You archive the log backup version files. To do this, you use a backup tool to copy the version files to an external backup medium.
The archived version files are assigned their own external backup IDs and are entered in the backup history.
After you execute the DBM command, the system displays information about the archived version files.
If you want to achive the same version files mulitiple times on different external backup media, call the Database Manager CLI in session mode. Next, you use the archive_stage command described here plus the KEEP option, and then the command for creating multiple archives of the version files of the log area (see: archive_stage_repeat).
See also:
Concepts of the Database System, Archiving Version Files
· You have the server authorization Backup.
· You have backed up the log area.
· The external backup medium is defined for backup type LOG (see: medium_put).
archive_stage <ext_backup_medium> <log_medium> [VERIFY | NOVERIFY] [REMOVE | KEEP] [FNL <list>]
Options
Option |
Description |
<ext_backup_medium> |
Name of the external backup medium |
<log_medium> |
Name of the backup medium that was used for the log backup |
VERIFY |
System default value The archived files are compared with the original files. |
NOVERIFY |
The system only performs the standard checks to determine whether the backup was successful. The system displays error messages where appropriate and the output of the backup tools. |
REMOVE |
System default value The original files are deleted after they have been successfully archived to the external backup medium. |
KEEP |
The original files are archived but are not deleted afterwards. |
FNL |
File Number List: Keyword of the list of files to be archived Only specify this keyword and the file number list if version files that you are sure were created are not in the backup history due to an error. This would be the case, for example, if the version files with the number 10 and 12 are in the backup history, but number 11 is missing. |
<list> |
File name or area or file names: You can leave out leading zeros. Separate multiple specifications using commas. If you do not specify a file list, the system copies all version files on the backup medium that are also in the backup history. |
OK
Processed Stage Files <number>
Bytes Processed <number>
Deleted Stage Files <number>
Remaining Stage Files <number>
Values for the Reply Fields
Value |
Description |
Processed Stage Files |
Processed version files |
Bytes Processed |
Processed bytes |
Deleted Stage Files |
Deleted version files |
Remaining Stage Files |
Remaining version files |
<number> |
Number |
Logging on to the Database Manager CLI as operator OLEG with the password MONDAY, connecting to the database instance DEMODB.
Creating a single archive of the original version files 1 and 3-10. They are stored on the DemoAutoLog backup medium and should be archived on the EXTMEDIUM_1 external backup medium, the version files should not be deleted afterwards:
dbmcli -u OLEG,MONDAY -d DEMODB
dbmcli on DEMODB>archive_stage EXTMEDIUM_1 DemoAutoLog NOVERIFY KEEP FNL 1,3-10
OK
Processed Stage Files 9
Bytes Processed
12845056
Deleted Stage Files
0
Remaining Stage Files
2