User's Manual

Log names are not
important
The Message Agent opens all the files in the transaction log directory to
determine which files are logs, so the actual names of the log files are not
important.
This section describes how you can set up a backup procedure to ensure that
such a directory is kept in proper shape.
Backup utility options
The Adaptive Server Anywhere backup utility has several options,
accessible through Sybase Central wizard selections or through dbbackup
options, that control its behavior.
This section describes two approaches to using the backup utility in
SQL Remote consolidated database backups. Backups must ensure that a set
of transaction logs suitable for use by the Message Agent is always available.
Using the live directory as the transaction log directory
It is recommended that you use the option to rename and restart the
transaction log when backing up the consolidated database and remote
database transaction logs. For the dbbackup utility, this is the -r option.
The figure below illustrates a database named consol.db , with a transaction
log named consol.log in the same directory. For the sake of simplicity, we
consider the log to be in the same directory as the database, although this
would not be generally safe practice in a production environment. The
directory is named c:\live .
971201AA.log
consol.db
971201AB.log
consol.log
A backup command line The following command line backs up the database using the rename and
restart option:
dbbackup -r -c "uid=DBA;pwd=SQL" c:\archive
The connection string options would be different for each database.
Effects of the backup If you back up the transaction log to a directory c:\archive using the rename
and restart option, the Backup utility carries out the following tasks:
250