Recovery Using SQL Server Database Mirroring: Moving CommCell Operations to the Production CommServe Host
In a mirrored setup, when the production CommServe is unusable or inaccessible, the standby CommServe serves as a production CommServe for a few days or weeks. After you rebuild the original production CommServe, you can switch the CommCell operations back to the production CommServe host.
High-Level Process Flow
The process flow for moving CommCell operations back to the production CommServe host involves the following tasks in the order listed:
- Make sure there are no SnapProtect Services running on the production CommServe host. See Stopping a Service.
- If the SQL services on the production CommServe host are down due to a disaster, and the mirroring between production and standby CommServe databases is broken, then re-establish the mirroring relationship using SQL Management Studio software. Consult Microsoft manual for instructions on resuming database mirroring.
- Initiate a manual failover to production CommServe host using the following SQL query. Consult Microsoft manual for instructions on executing SQL queries.
ALTER DATABASE CommServ SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS
- Update the CommServe database with the host name of the production CommServe host.
For instructions on changing the CommServe host name, see Restoring CommCell Operations on the CommServe Host.
- Start the CommCell services on the production CommServe host. See Starting a Service.
- Open the CommCell console and verify that all the components, such clients, MediaAgents, Libraries, policies on the production CommServe are available.
- Update the CommServe name for all clients and MediaAgents. See Updating the CommServe Name for Clients and MediaAgents.
- Perform a few backup and restore operations for any client to ensure that the production CommServe database is ready to perform all the CommCell operations.
If there are inconsistencies between the DDB and the CommServe database during a backup or auxiliary copy operation, the DDBs are put in maintenance mode and an appropriate event message is displayed in the Event Viewer window. In such cases, run DDB Resynchronization to bring the DDBs online and revert it to a reusable state from the maintenance mode. See Resynchronizing the Deduplication Database.