You use this DBM command to continue a backup without the last medium that was reported full.
This is relevant for backups to parallel backup media. When a backup medium is full and further data still has to be transferred, the system prompts you to provide a succeeding medium. Otherwise, the backup process is stopped.
You can use the backup_ignore command to continue backups that have been stopped without providing a new backup medium. In this case, the remaining data to be transferred is saved to the other media in the group of parallel backup media.
You have the DBM operator authorization Backup.
You have started backing up the database instance. The backup process was interrupted because the backup medium was reported full.
backup_ignore
The reply to this command contains the information about the backup supplied by the kernel.
This information is only output when the backup has been completed or interrupted. This command may, therefore, take a long time to execute.
OK<NL>
Returncode
<value><NL>
Date
[<value>]<NL>
Time
[<value>]<NL>
Server
[<value>]<NL>
Database
[<value>]<NL>
Kernel Version
[<value>]<NL>
Pages Transferred
[<value>]<NL>
Pages Left
[<value>]<NL>
Volume Count
[<value>]<NL>
Medianame [<value>]<NL>
Location
[<value>]<NL>
Errortext
[<value>]<NL>
Label
[<value>]<NL>
Is Consistent
[<value>]<NL>
First LOG Page
[<value>]<NL>
Last LOG Page
[<value>]<NL>
DB Stamp 1 Date
[<value>]<NL>
DB Stamp 1 Time
[<value>]<NL>
DB Stamp 2 Date
[<value>]<NL>
DB Stamp 2 Time
[<value>]<NL>
Page Count
[<value>]<NL>
Devices Used
[<value>]<NL>
In particular, analyze the Returncode reply field, which contains a numeric value supplied by the kernel.
See also: Messages
If it is clear from the message number that the backup was just interrupted, the session must be continued with the continuation command: (backup_replace, backup_ignore), or terminated with backup_cancel.
In the event of errors, see Reply Format.