Chapter 11. Administering SQL Remote for AdaptiveSer ver
Anywhere
Transaction log and backup management
Theimpor tance of good
backuppractices Replicationdepends on access to operations in the transaction log, and
accessto old transaction logs is sometimes required. Thissection describes
howto set up backup procedures at the consolidated and remote databases to
ensureproper access to old transaction logs.
Itis crucial to have good backup practices at SQL Remote consolidated
databasesites. Alost transaction log could easily mean having to re-extract
remoteusers. Atthe consolidated database site, a transaction log mirror is
recommended.
Forinformation on transaction log mirrors and other backup procedure
information,see “Backup and Data Recovery” [ASA Database Administration
Guide,page 373].
Ensuring access to old
transactions Alltransaction logs must be guaranteed available until they are no longer
neededby the replication system.
Inmany setups, users of remote databases may receive updates from the
officeserver every day or so. If some messages get lost or deleted, and have
tobe resent by the message-tracking system, it is possible that changesmade
severaldays ago will be required. Ifa remote user takes a vacation, and
messageshave been lost in the meantime, changes weeks old may be
required. If the transaction log is backed up daily,the log with the changes
willno longer be running on the server.
Becausethe transaction log continually grows in size, space can become a
concern. Youcan use an event handler on transaction log size to rename the
logwhen it reaches a given size. Thenyou can use the
DELETE_OLD_LOGSoption to clean up log files that are no longer needed.
Formore information about controlling transaction log size, see the
“BACKUPstatement” [ASA SQL Reference, page 307].

Setting the transaction log directory

Whenthe Message Agent needs to scan transaction logs other than the
currentlog, it looks through all the transaction log files kept in a designated
transactionlog directory. Asetting on the Message Agent command line
tellsthe Message Agent which directory this is.
Example Forexample, the following command line tells the Message Agent to look in
thedirectory

e:\archive

tofind old transaction logs. Thecommand must be
enteredall on one line.
dbremote -c "eng=server_name;uid=DBA;pwd=SQL" e:\archive
249