Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » SQL Anywhere Server - Database Administration » Backup and Data Recovery » Designing backup procedures

Understanding parallel database backups Next Page

A backup scheme for when disk space is plentiful

If disk space is not a problem on your production computer (where the database server is running) then you do not need to worry about choosing special options to manage the transaction log file or the checkpoint log. In this case, you can use an image backup. The simplest image backup makes copies of the database file and transaction log, and leaves the transaction log in place. All backups leave the database file in place.

A full backup of this kind is illustrated in the figure below. In an incremental backup, only the transaction log is backed up.

In a full backup, the database file and log file are copied to the backup directory. The backup leaves the database file and log file in place.

For more information about full backups, see Making a backup, continuing to use the original transaction log.