ABORT BACKUP

Aborts an online backup operation.

SYNTAX

DESCRIPTION

The ABORT BACKUP command cancels an online backup. You may want to cancel a backup if errors occur during the backup operation or if you want to perform the backup at another time. Only users with SYSADM or DBA security privileges can execute the ABORT BACKUP command.

Backup mode indicates whether DBMaker will perform online incremental backups, and what data will be backed up during an incremental backup. There are three backup modes: NONBACKUP, BACKUP-DATA, and BACKUP-DATA-AND-BLOB. You can set the backup mode in three ways: using the DB_BMODE keyword in the dmconfig.ini configuration file, using the SQL SET command at the dmSQL command prompt, or using the Server Manager utility provided with DBMaker.

NONBACKUP mode provides no protection for any data that was inserted or updated since the last full backup. In this mode, DBMaker cannot perform online incremental backups. A database can use the journal to fully recover from a program failure, but a disk failure may result in loss of data. Journal blocks not in use by an active transaction can be reused immediately after a checkpoint, but once they are overwritten, you can only restore the database to the point in time of the last full backup.

BACKUP-DATA mode provides protection for data (excluding BLOB data) that was inserted or updated since the last full backup. In this mode, DBMaker can perform an online incremental backup, but only non-BLOB data will be stored in the backup files. A database can use the journal to fully recover from a program failure, and can partially recover from a disk failure. Although you can use the last backup to restore the database to the point in time of the media failure; any changes to BLOB data will be lost. Journal blocks not in use by an active transaction can only be reused after a checkpoint has taken place and the journal file has been backed up.

BACKUP-DATA-AND-BLOB mode provides protection for all data (including BLOB data) that was inserted or updated since the last full backup. In this mode, DBMaker can perform an online incremental backup, and all data will be stored in the backup files. A database can use the journal to fully recover from a program failure, and can fully recover from a disk failure. You can use the last backup to completely restore the database to the point in time of the media failure, including all BLOB data. Journal blocks not in use by an active transaction can only be reused after a checkpoint has taken place and the journal file has been backed up.

Issuing the ABORT BACKUP command does not change the backup mode of the database. The database will remain in the same backup mode it was in before the backup started.

EXAMPLE

The following example aborts a backup operation:

RELATED COMMANDS

• BEGIN BACKUP
• END BACKUP

< Contents | ADD TO GROUP >