You specify the succeeding data carrier which the backup should continue to be imported from.
The reply to this DBM command displays information about the import of the backup. Pay particular attention to the message number displayed in the Returncode field.
However, you get the reply only once the backup has been imported completely, or if the backup was interrupted. This command may therefore take a long time to execute.
If you have executed the DBM command and the restore process was then interrupted again (message number -8020), specify the next succeeding data carrier with recover_replace.
You repeat this procedure until the data from all the data carriers belonging to the backup has been imported.
You have the server authorization Backup.
You have executed the DBM command for recovering the database instance (see: recover_start). The operation was interrupted because the data stored on the data carrier was imported completely. You are still in the same database session.
recover_replace <medium_name> [ExternalBackupID <ext_backup_ID>] [<loc> [<nnn>]]
Option |
Description |
---|---|
<medium_name> |
Backup template or complete file or device name of the data carrier via which the next data carrier can be accessed When restoring a backup made using a backup template for several data carriers at the same time, you must enter the name of the group of parallel data carriers here. |
ExternalBackupID <external_backup_ID> |
Only for restoring a backup that was created with a backup tool: Name under which the backup is known to the backup tool. |
<loc> |
Name of the device/the file in which the backup to be recovered is stored. Operating system functions must be able to address the device/file using <loc>. |
<nnn> |
Only for log backup to be imported and only for data carriers of the FILE type: Version number of the log backup on the data carrier to be imported |
OK
Returncode <value>
...
Value |
Description |
---|---|
Date |
Date |
Time |
Start time for backup |
Server |
Name of the database computer |
Database |
Name of the database |
Kernel Version |
Version of the database kernel |
Pages Transferred |
Number of pages transferred |
Pages Left |
Number of pages still to be transferred |
Volumes |
Number of data carriers used |
Medianame |
Name of the backup template |
Location |
File or device name |
Errortext |
Error message text See also: Messages documentation |
Label |
Backup ID |
Is Consistent |
Only for data backup: Backup is internally consistent |
First LOG Page |
For data backup: first page of log backup to be read For log backup: first page saved in log |
Last LOG Page |
For log backup only: last page saved in log |
DB Stamp 1 Date DB Stamp 1 Time |
Time stamp for first page of log backup |
DB Stamp 2 Date DB Stamp 2 Time |
Time stamp for last page of log backup |
Page Count |
Total number of pages backed up |
Devices Used |
Number of backup devices used |
Database ID |
Database ID used to identify data and log backups which belong together |
In the event of errors, see Reply Format.
Database Manager CLI Tutorial, Restoring the Database Instance
Database Administration, Restoring Databases