## recover_replace

### Use

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.

See also:

Database Administration Tutorial, Restoring the Database Instance

Concepts of the Database System, Restoring the Database Instance

### Prerequisites

● 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.

### Syntax

recover_replace <medium_name> [ExternalBackupID <ext_backup_ID>] [<loc> [<nnn>]]

Options

Option | Description
<medium_name> | Data carrier from which the backup is to be imported When restoring a backup that was created using a backup template for multiple data carriers in parallel, you need to specify the name of the group of parallel data carriers here.
ExternalBackupID <external_backup_ID> | Only for recovering 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 backups to be imported and only for data carriers of the type FILE: version number of the log backup on the data carrier that is to be imported

### Reply

OK

Returncode <value>

Date [<value>]

Time [<value>]

Server [<value>]

Database [<value>]

Kernel Version [<value>]

Pages Transferred [<value>]

Pages Left [<value>]

Volume Count [<value>]

Mediumname [<value>]

Location [<value>]

Errortext [<value>]

Label [<value>]

Is Consistent [<value>]

First LOG Page [<value>]

Last LOG Page [<value>]

DB Stamp 1 Date [<value>]

DB Stamp 1 Time [<value>]

DB Stamp 2 Date [<value>]

DB Stamp 2 Time [<value>]

Page Count [<value>]

Devices Used [<value>]

Database ID [<value>]

Max Used Data Page [<value>]

Values for the Reply Fields

Value | Description
Date | Date
Time | Time
Server | Name of the database computer
Database | Name of the database instance
Kernel Version | Version of database software
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: Documentation, Messages
Label | Backup ID
Is Consistent | For data backup only: backup is internally consistent
First LOG Page | For data backup: first page of log backup to be imported 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 that belong together
Max Used Data Page | Highest page number assigned (indication of minimum database size when backup is imported)

In the event of errors, see Reply Format.