This set of backup options is typically used for databases involved in replication. In addition to making backup copies of the database file and transaction log, the transaction log at backup time is renamed to an offline log, and a new transaction log is started with the same name as the log in use at backup time.
For more information about when to use this set of backup options, see A backup scheme for databases involved in replication.
To make a backup, renaming the transaction log (Sybase Central)
Connect to the database as a user with DBA authority.
Right-click the database and choose Create Backup Images.
In the Which Database Do You Want To Back Up list, select the database and click Next.
In the Save The Backup Images In The Following Directory field, type the name of a directory to save the backup copies.
Select an option in the Which Files Do You Want To Back Up list and click Next.
In the What Do You Want To Do With The Transaction Log list, click Rename The Transaction Log.
To make a backup, renaming the transaction log (SQL)
Use the BACKUP statement with the following clauses:
BACKUP DATABASE DIRECTORY backup-directory [ TRANSACTION LOG ONLY ] TRANSACTION LOG RENAME;
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.
To make a backup, renaming the transaction log (Command line)
Run the following command (it must be typed on one line):
dbbackup -c "connection-string" -r [ -t ] backup-directory
Include the -t option 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 renamed, all outstanding transactions must complete. If there are outstanding transactions, your backup will not 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.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|