You will want to implement a recovery strategy both for your replication control server, and for any databases that are replication sources. The replication control server is the database location of the applicable subscription definitions and Apply program control tables. The sections that follow describe the implications if the replication control server is on the satellite. If the replication control server or the replication source is not on the satellite, refer to the documentation for the DB2 database product that serves either as a replication control server or replication source for the recommendations and procedures for implementing a recovery strategy.
If the replication control server is on the satellite, either the database that contains the user data contains the subscription definitions and the Apply program control tables, or you use a different database to contain the replication-related information.
For refresh, version, and point-in-time forward recovery, you must cold start the Capture program to refresh the replicated data on the satellite. The only situation in which you do not have to cold start the Capture program occurs when you roll forward to the end of the logs. In this situation, the database is completely restored. For information on cold starting the Capture program, refer to the description of how to start the Capture program in the Windows and OS/2 environments in the Replication Guide and Reference.
| Note: | If you roll forward to a point in time, it may not be possible to restore all the data that is unique to the satellite: log records that were written past the specified point in time may contain unique data. |
The database that provides the replication control server function does not have to be a database on the satellite. Instead, the database can be on the DB2 control server, or on any other DB2 server. Your recovery strategy for this database should be forward recovery to the end of the logs. This method is the only way to restore all the replication-related data that indicates whether a satellite has replicated or not, and what data each satellite has replicated.
Neither forward recovery to a point in time, nor version recovery are recommended for the replication control server. With either method, you cannot re-create all the data that indicates whether a satellite has replicated, or what data it replicated. If you have to restore the database with point-in-time or version recovery, you should cold start the Capture program on all the satellites that use that replication control server to ensure that their data is up-to-date.
[ Top of Page ]