Background documentationrecover_ignore Locate this document in the navigation structure

 

While restoring a backup created using a backup template for multiple parallel data carriers, the data was imported in full from one of the data carriers involved. The system prompts you to specify a succeeding data carrier. If you do not do this, but instead execute the DBM command recover_ignore, the system then works only with the remaining space on the parallel data carriers.

Example

You would use this DBM command in the following situation, for example:

You want to import a backup that was created using three tape drives in parallel and consists of a total of 5 tapes. You start importing the data using three tape drives so that tapes 1-3 are imported in parallel. After a while, the data on the tape in tape drive 1 has been completely imported. The import from drives 2 and 3 is ongoing. The system prompts you to place the next tape in tape drive 1. If you now enter recover_ignore, the import continues only with tape drives 2 and 3.

As soon as the next tape drive (e.g. tape drive 3) prompts you to insert another data carrier, use recover_replace to specify a succeeding data carrier and import tape 4.

When you are asked to do so by tape drive 2, also use recover_replace to specify a succeeding data carrier and import tape 5.

Thereafter all 5 backup tapes will have been imported.

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.

Prerequisites

  • You have the server authorization Backup.

  • You have started recovering a database instance by importing data from several media simultaneously (see recover_start) and are still in the same database session. The operation was interrupted because the system is requesting a succeeding data carrier for one of the parallel data carriers. You do not want to specify another succeeding data carrier here and only want the remaining data carriers to continue importing.

Structure

recover_ignore

Result

OK

Returncode <value>

...

Values for the Reply Fields

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.