backup_ignore

Use

A backup performed using a backup template for a group of parallel data carriers was interrupted because the system has sent a message saying a data carrier in the group is full. As other data still needs to be backed up, the system requests you to replace this data carrier.

You use the DBM commandbackup_ignore to continue the backup operation without replacing this data carrier. In this case, the remaining data to be backed up is only saved to the other data carriers in the group.

After the system has executed this DBM command, information about the backup is output. The information is only given when the backup operation is finished or is interrupted again. For this reason, the response to this DBM command can take a long time.

Pay special attention to the Returncode reply field, which contains a numeric value for a message.

See also: Messages

If it is clear from the message number that the backup operation has been interrupted again, you have to continue the session with a succeeding command (backup_replace, backup_ignore), or terminate with backup_cancel.

See also:

Concepts of the Database System, Backing Up Data

Prerequisites

?     You have the server authorization Backup.

?     You have started backing up the database instance on a group of parallel data carriers. The backup operation was interrupted because one of the data carriers in the group was reported as full. You are still in the same database session.

Syntax

backup_ignore

Reply

OK

Returncode              <value>

Date                    [<value>]

Time                    [<value>]

Server                  [<value>]

Database                [<value>]

Kernel Version          [<value>]

Pages Transferred       [<value>]

Pages Left              [<value>]

Volume Count            [<value>]

Medianame               [<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>]

Values for the Reply Fields

Field

Description

Date

Date

Time

Start time for backup

Server

Name of the database computer

Database

Name of the database instance

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

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

In the event of errors, see Reply Format.