Lognames are not
important The Message Agent opens all the files in the transaction log directory to
determinewhich files are logs, so the actual names of the log files are not
important.
Thissection describes how you can set up a backup procedure to ensure that
sucha directory is kept in proper shape.
Backup utility options
TheAdaptive Server Anywhere backup utility has several options,
accessiblethrough Sybase Central wizard selections or through
dbbackup
options,that control its behavior.
Thissection describes two approaches to using the backup utility in
SQLRemote consolidated database backups. Backupsmust ensure that a set
oftransaction logs suitable for use by the Message Agent is always available.
Using the live directory as the transaction log directory
Itis recommended that you use the option to rename and restart the
transactionlog when backing up the consolidated database and remote
databasetransaction logs. Forthe
dbbackup
utility,this is the -r option.
Thefigure below illustrates a database named

consol.db

,with a transaction
lognamed
consol.log
inthe same directory. For the sake of simplicity, we
considerthe log to be in the same directory as the database, although this
wouldnot be generally safe practice in a production environment. The
directoryis named

c:\live

.
971201AA.log
consol.db
971201AB.log
consol.log
Abackup command line Thefollowing command line backs up the database using the rename and
restartoption:
dbbackup -r -c "uid=DBA;pwd=SQL" c:\archive
Theconnection string options would be different for each database.
Effectsof the backup Ifyou back up the transaction log to a directory

c:\archive

usingthe rename
andrestart option, the Backup utility carries out the following tasks:
250