|
If your database is not involved in replication, and if you have limited disk space on your online computer, you can delete the contents of the online transaction log (truncate the log) when you make a backup. In this case, you need to use every backup copy made since the last full backup during recovery from media failure on the database file.
For more information about when to use this type of backup, see A backup scheme for databases not involved in replication.
Start Sybase Central. Connect to the database as the DBA.
Right-click the database and choose Create Backup Images from the popup menu.
The Create Backup Images wizard appears.
Click Next on the introductory page of the wizard.
Select the database that you want to back up.
On the next page, enter the name of a directory to hold the backup copies, and choose whether to perform a complete backup (all database files) or an incremental backup (transaction log file only).
On the next page, select the option Truncate the Transaction Log.
Click Finish to start the backup.
Use the BACKUP statement with the following clauses:
BACKUP DATABASE DIRECTORY backup-directory [ TRANSACTION LOG ONLY ] TRANSACTION LOG TRUNCATE;
Include the TRANSACTION LOG ONLY clause only if you are making an incremental backup.
The backup copies of the transaction log and database file are placed in backup-directory. If you enter a path, it is relative to the working directory of the database server, not your client application.
From the command prompt, enter the following command:
dbbackup -c "connection-string" -x [ -t ] backup-directory
Include the -t option only if you are making an incremental backup.
The backup copies of the transaction log and database file are placed in backup-directory. If you enter a path, it is relative to the directory from which you run the command.
Before the online transaction log can be erased, all outstanding transactions must terminate. If there are outstanding transactions, your backup cannot complete. See Backup internals.
You can determine which connection has an outstanding transaction using the sa_conn_info system procedure. If necessary, you can disconnect the user with a DROP CONNECTION statement. See Determining which connection has an outstanding transaction.