Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.0 (Français) » SQL Remote » Managing SQL Remote systems

 

Backing up SQL Remote systems

SQL Remote replication depends on access to operations in the transaction log, and access to old transaction logs. Any backup strategy that you implement must incorporate the maintenance of the transaction logs for SQL Remote.

The SQL Remote Message Agent (dbremote) must have access to the current and old transaction logs until they are no longer needed.

A consolidated database no longer needs its transaction logs when all remote databases have received and have confirmed that the messages contained in the transaction logs have been successfully applied.

A remote database no longer needs its transaction logs when the consolidated database has received and confirmed that it has successfully applied the messages contained in the transaction logs.

 Backing up remote databases
 Backing up consolidated databases
 The Backup utility (dbbackup) and the SQL Remote Message Agent (dbremote) -x option

Maintaining transaction logs for remote databases
Protecting the consolidated database from media failures
Back up the consolidated database