Administering Satellites Guide and Reference

Recovering Satellites in the Production Environment

Because the model office is the template for the production satellites, the recovery strategy that you decide on for the model office also applies to the production satellites. Recovering the Model Office describes the considerations for using refresh, version, or forward recovery on the model office. The considerations for using these recovery strategies with production satellites are as follows:

Refresh recovery

With refresh recovery, you do not use database backups to recover the database on the production satellite. Instead, you use the install image that was generated from the model office to re-install the entire satellite, then use the Set Execution Starting Point window to specify that the satellite re-execute all of its group batches from the first batch step of each batch.

Version recovery

If you are using version recovery, you can back up the database on a periodic basis. In this situation, you will want to schedule how frequently the database is backed up. For example, you may want to take a backup image of the database on a weekly, or even a monthly basis. Or you may want the database to be backed up more frequently. One important factor to consider is the volume of transactions that are applied to the database. If the database is frequently updated, you may want to back up the database more frequently. With version recovery, the backup schedule will determine how much you can protect against the loss of data.

Forward recovery

If you are using forward recovery, you will want to schedule how frequently the database is backed up. The more frequent the backup, the fewer the logs that will have to be applied during the roll-forward phase when the database is recovered. For example, if updates to the database are infrequent, you may want to take a backup image of the database on a weekly, or even a monthly basis. Because few log records will be written, it will not require much time to fully recover the database. If, however, the database is updated frequently, you may want to back up the database more frequently to reduce the number of logs, and the amount of time that will be required to fully restore the database.

[ Top of Page ]