backup_start

Use

You back up the data area or the log area of the database instance.

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. For this reason, the response to this DBM command can take a long time. You can display the ongoing status of the backup operation with the DBM command backup_state.

If it is clear from the message number that the backup operation has only been interrupted, you must continue within the same database session with a succeeding command (backup_replace, backup_ignore), or terminate it (backup_cancel).

See also:

Database Administration Tutorial, Backup

Concepts of the Database Systems, Backing Up Data, Backing Up Log Entries

Prerequisites

?     You have the server authorization Backup.

?     You have opened a database session (see: db_connect).

?     If you want to perform an interactive log backup, you must have performed a data backup for the relevant database instance at least once previously.

Syntax

backup_start <medium_name> [<backup_type>] [AUTOIGNORE]

Options

Option

Description

<medium_name>

Name of the backup template

When backing up on a group of parallel data carriers, you need to specify the name of the group here.

<backup_type>

Type of backup

You only need to specify an entry here if you did not specify the backup type when you defined the backup template to be used (media definitions in earlier versions). Possible values are:
DATA: complete data backup
PAGES: incremental data backup
LOG: interactive log backup
Otherwise the system uses the value for the backup type specified during the media definition.

AUTOIGNORE

 

Backup is continued automatically without the data carrier last reported as full (see: 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 database instance

Kernel Version

Version of 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

Reply in the Event of an Error

If an error occurs while you are using a third-party backup tool, you will receive a reply in the following format:

ERR

<errcode>, <err_description>

[<extended_description>]

Values for the Reply Fields

Value

Description

<errcode>

Error Message Number

See: Messages

<err_description>

Description of the error

<extended_description>

Cause of error

The following errors may occur:

Error Message Number

Error message text

Explanation

-24927

ERR_TOOLCHK: the external backup tool was not found

The backup tool could not be found or has been installed incorrectly.

-24926

ERR_MEDIUMCHK: the medium cannot be used with this external backup tool

The backup template specified cannot be used with this backup tool.

-24925

ERR_PREPARE: prepare of the backup operation failed

The preparations required to use the backup tool could not be completed correctly.

-24924

ERR_DBREQ: cannot start database kernel request

The database instance was unable to start the backup.

-24923

ERR_TOOLREQ: cannot start external backup tool correctly

The backup tool could not be started correctly.

-24922

ERR_OPCHK: cannot check state of backup operation

Unable to check the status of database instance or backup tool.

-24921

ERR_POSTOP: cannot finish backup operation correctly

Although the backup was successful, the post-processing steps required could not be performed.

-24920

ERR_BACKUPOP: backup operation was unsuccessful

The backup failed due to a problem with the database or the backup tool.

-24919

ERR_CLEANUP: cannot clean up correctly after backup operation

Although the backup was successful, the system resources used during the check could not be released again.