archive_stage

Use

To increase your data security, you make one or several copies of the backup files of log backups using backup tools. The system then checks whether the copying was successful. You can use the options to control whether the copied files should be compared with the original files for security reasons, and whether the original files should be deleted after the copying.

Log backups that are created using the automatic log backup function can only be written to files. For archiving, you can use operating system commands to copy the backup files onto other data carriers.

The DBM command archive_stage, on the other hand, enables you to transfer the content of the backup files into pipes, so that they can be read and archived using the backup tools of other providers. The data read from the pipes can then be archived using backup tools, either a single time, or for security reasons, multiple times. These backup tools can also be from different providers. The process also ensures that all the copies of the backup files created in this way are identical, even if the active automatic log backup has meanwhile written more new backup files.

If you want to archive the same backup files multiple times on different data carriers, you call the Database Manager CLI in session mode. You 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. You then execute the DBM command archive_stage_repeat, entering an additional data carrier (2). Thus the same group of backup files is copied again.

The archived backup 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 backup files.

See also:

Concepts of the Database System, Archiving Backup Files

Prerequisites

?     You have the server authorization Backup.

?     You have backed up the log area in files.

?     The backup template for the data carrier is defined for backup type LOG (see: medium_put).

Syntax

archive_stage <ext_backup_medium> <log_medium> [NOVERIFY] [KEEP] [FNL <list>]

Options

Option

Description

<ext_backup_medium>

Name of the backup template

<log_medium>

Name of the backup template with which the log backup was created

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.

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 files are archived but are not deleted afterwards.

If you do not specify this option, then the original files are deleted after they have been successfully archived on the data carrier (system default).

FNL

File Number List: Keyword of the list of files to be archived

Only specify this keyword and the file number list if backup 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 backup 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 the backup files that exist at the start of the archiving process, that were created using the specified backup template, and that are also in the backup history.

Reply

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 backup files

Bytes Processed

Processed bytes

Deleted Stage Files

Deleted backup files

Remaining Stage Files

Remaining backup files

<number>

Number

Example

Call the Database Manager CLI in session mode, log on as operator OLEG with password MONDAY, connect to the database instance DEMODB, create a single archive of the original backup files 1 and 3-10 (created using the backup template DemoAutoLog; now you want to back them up again for archiving purposes using the backup template EXTDATACARRIER_1; you do not want to delete the original backup files):

>dbmcli -u OLEG,MONDAY -d DEMODB

dbmcli on DEMODB>archive_stage EXTDATACARRIER_1 DemoAutoLog NOVERIFY KEEP FNL 1,3-10

OK
Processed Stage Files   9
Bytes Processed         12845056
Deleted Stage Files     0
Remaining Stage Files   2