archive_stage 
To increase your data security, make one or several copies of the backup files of log backups using backup tools or operating system commands. The system checks whether the copying was successful.
With the help of the command options you can control whether the copied files should be compared with the original files for security reasons, and whether the original files should be deleted after copying.
Log backups that are created using the automatic log backup function can only be written to files. To archive those log backups on other data carriers, you can use operating system commands. All other log backups can be archived using the archive_stage command.
For example, you can transfer the content of the backup files into pipes, so that they can be read and archived using one or more backup tools of other providers. The backup tools can archive the data read from the pipes either once, or for security reasons, multiple times. The backup tools used can even be combinations of tools from different providers.
The archiving process with the help of the archive_stage command allways ensures that the content of any number of copies is identical to their original log backup. This also applies if the active automatic log backup function is running and has meanwhile written new backup files.
Example
If you want to archive the same backup files multiple times on different data carriers, call Database Manager CLI in session mode. First use the archive_stage command described here plus the KEEP option, entering a data carrier (1) onto which you want to copy the backup files. Then execute the archive_stage_repeat command, entering an additional data carrier (2). This way the same group of backup files is copied again.
All copies of the backup files are assigned their own external backup IDs and are entered in the backup history.
After the system has executed the DBM command, information about the archived backup files is displayed.
Prerequisites
You have the server permission Backup.
The backup template for the data carrier is defined for backup type LOG (see medium_put).
Structure
archive_stage <archive_medium> <log_medium> [NOVERIFY] [KEEP] [FNL <list>]
Option |
Description |
|---|---|
<archive_medium> |
Name of the backup template to be used for archiving |
<log_medium> |
Name of the backup template with which the log backup has been created |
NOVERIFY |
The system only performs the standard checks to determine whether the copying was successful. The system displays error messages where appropriate, as well as the output of the backup tools. If you do not specify this option, then the system additionally compares the content of the archived files with the content of the original files (system default). |
KEEP |
The original log backup files are archived but are not deleted afterwards. If you do not specify this option, then the original log backup files are deleted after they have been successfully archived on the data carrier (system default). |
FNL |
File Number List: Keyword for the list of files to be archived Only specify this keyword and the list of file numbers if you are sure that particular log backup files were created but are not listed in the backup history due to an error. This would be the case, for example, if the log backup files with the number 10 and 12 are listed in the backup history, but number 11 is missing. |
<list> |
File name or range of file names: You can omit leading zeros. Separate multiple values using commas. If you do not specify a file list, the system copies all the log backup files that exist at the start of the archiving process, were created using the specified backup template, and are listed in the backup history. |
Result
OK
Processed Stage Files <number>
Bytes Processed <number>
Deleted Stage Files <number>
Remaining Stage Files <number>
Value |
Description |
|---|---|
Processed Stage Files |
Processed log backup files |
Bytes Processed |
Processed bytes |
Deleted Stage Files |
Deleted log backup files |
Remaining Stage Files |
Remaining log backup files |
<number> |
Number |
Example
Call Database Manager CLI in session mode, log on as the operator OLEG with the password MONDAY, connect to the database DEMODB:
>dbmcli -u OLEG,MONDAY -d DEMODB
dbmcli on DEMODB>
Create a single copy of the original backup files 1 and 3-10. They were backed up using the backup template DemoAutoLog and should now be backed up again for archiving purposes using the backup template ARCHDATACARRIER_1. The original backup files should not be deleted afterwards:
dbmcli on DEMODB>archive_stage ARCHDATACARRIER_1 DemoAutoLog NOVERIFY KEEP FNL 1,3-10
OK
Processed Stage Files 9
Bytes Processed 12845056
Deleted Stage Files 0
Remaining Stage Files 2
More Information
Database Administration, Archiving Backup Files