DeepSee and Disaster Recovery
This appendix describes the recommended procedure for write-protecting copied source data on an async mirror member using DeepSee. It discusses the following topics:
This section describes the necessary initial configuration tasks.
Set up the async mirror as a disaster recovery (DR) async with all source data databases and the newly-mapped database for ^OBJ.DSTIME. This will perform more validation of the system and push any issues with the ISCAgent and so on to configuration time instead of recovery time. Note that this mode does not allow for a read-write database.
Once configured, switch the DR to a read-only async member.
On a read-only async, each specific database has aReadOnlyflag that can be cleared, allowing writes. Do this for the database containing ^OBJ.DSTIME.
The source data is now write-protected and the cubes can be synchronized properly.
This section describes the steps to take during disaster recovery.
Remove the database containing ^OBJ.DSTIME from the mirror configuration. Note that the database is still available.
Switch the async member back to a DR member.
Promote the member to primary.
The ^OBJ.DSTIME buffer needs to be treated as out-of-date on any other systems that may now be relying on this one, as there will be no attempt to synchronize that data with other async members. The database containing ^OBJ.DSTIME needs to be added back into the mirror set as part of the recovery procedure.