Considerations about testing disaster recovery in an end-to-end environment
During a disaster recovery, the USS BINDIR (either HFS or ZFS) is also to be restored. If you are testing a disaster recovery while the production environment is still running, the IP addresses contained in the Symphony™ file could cause the fault-tolerant agents to be inadvertently shut down. To prevent this problem, the WRKDIR must not be restored at the disaster recovery site or the Symphony™ file must be deleted before starting the end-to-end server at the disaster recovery site.
Therefore, if you are testing a disaster recovery, perform either
of the following:
- Do not restore the WRKDIR at the disaster recovery site. Instead, run the EQQPCS05 job to create an empty WRKDIR, then start the end-to-end server and run a SYMPHONY RENEW.
- After restoring the production WRKDIR and before starting
the controller and end-to-end server, delete or rename
the
Symphonyandtranslator.chkfiles from WRKDIR. Start the controller and end-to-end server, then run a SYMPHONY RENEW.