Making a server-side backup with the BACKUP DATABASE statement

 Make an image backup (SQL)

The following backup leaves the transaction log untouched. For information about other transaction log management options when making a backup, see BACKUP statement.

  1. Connect to the database as a user with REMOTE DBA or BACKUP authority.

  2. Execute the following statement to make an image backup:

    BACKUP DATABASE
    DIRECTORY directory-name;

    The BACKUP statement makes an entry in the text file backup.syb. For information about the location of the backup.syb file, see SALOGDIR environment variable.

    For information about recovering from an image backup, see Restoring from an image backup.

 Make an archive backup to tape (SQL)

The following backup leaves the transaction log untouched. For information about other transaction log management options when making a backup, see BACKUP statement.

  1. Connect to the database as a user with REMOTE DBA or BACKUP authority.

  2. Execute the following BACKUP statement to make an archive backup to tape:

    BACKUP DATABASE
    TO archive-root
    [ ATTENDED { ON | OFF } ]
    [ WITH COMMENT comment-string ];

    If you set the ATTENDED option to OFF, the backup fails if it runs out of tape or disk space. If ATTENDED is set to ON, you are prompted to take an action when there is no more space on the backup archive device.

    The BACKUP statement makes an entry in the text file backup.syb. For information about the location of the backup.syb file, see SALOGDIR environment variable.

    For information about recovering from an archive backup, see Restoring from an archive backup.

 See also
 Examples