For disaster recovery purposes, you might want to set up
a tracker site. To set up a tracker site, you create a mirror image
of your primary Db2 subsystem,
and then ensure that the tracker site is synchronized with the primary
site.
Procedure
To set up the tracker site:
- Create a mirror image of your primary Db2 subsystem
or data sharing group.
This process is described in steps
1 through 4 of the normal disaster recovery procedure, which includes
creating catalogs and restoring Db2 libraries.
- Modify the subsystem parameters as follows:
- Set the TRKRSITE subsystem parameter to YES.
- Optionally, set the SITETYP parameter to RECOVERYSITE if the full
image copies that this site is to receive are created as remote site
copies.
- Use the access method services DEFINE CLUSTER command
to allocate data sets for all user-managed table spaces that you plan
to send over from the primary site.
- Optional: Allocate data sets for user-managed
indexes that you want to rebuild during recovery cycles.
The
main reason that you rebuild indexes during recovery cycles is for
running efficient queries on the tracker site. If you do not require
indexes, you do not need to rebuild them for recovery cycles. For
nonpartitioning indexes on very large tables, you can include indexes
for LOGONLY recovery during the recovery cycle, which can reduce the
amount of time that it takes to bring up the disaster site. Be sure
that you define data sets with the proper prefix (either I or J) for
both indexes and table spaces.
- Send full image copies of all Db2 data at the primary site to
the tracker site. Optionally, you can use the BACKUP SYSTEM utility
with the DATA ONLY option and send copies of the database copy pool
to the tracker site.
If you send copies that the
BACKUP SYSTEM utility creates, this step completes the tracker site
setup procedure.
- If you did not use the BACKUP SYSTEM
utility in the prior, tailor installation job DSNTIJIN to create Db2 catalog data sets.