CommServe Recovery Using SQL Server Database Mirroring
Caution: SQL database mirroring is deprecated by Microsoft and may not be available in future versions of Microsoft SQL Server. Therefore, we recommend that you build the CommServe Disaster Recovery Using CommServe LiveSync For High Availability Disaster Recovery.
In this method of disaster recovery, Microsoft SQL Server's database mirroring feature is used to keep the databases of the production CommServe host and the standby CommServe host in a near synchronized state. Committed SQL transactions on the production CommServe host are immediately applied to the standby CommServe host. The standby CommServe host can be activated by automatic or manual failover, or by breaking the mirror relationship and bringing the standby CommServe host databases online.
Microsoft SQL Server database mirroring has several options and configurations which depend on your recovery objectives and hosting environment. Consult Microsoft documentation to configure the mirroring mode you want to use.
In addition to the CommServe database, you can also replicate the following databases using the SQL Server database mirroring method.
- HistoryDB (History Database)
- DM2 (Web Server)
- WFEngine (Workflow Engine)
- CVCloud (Private Metrics Reporting Server database)
- Build the standby CommServe host. See Building the Standby CommServe Host.
- Test restore operations on the standby CommServe host. See Testing the Standby CommServe Host.
- Move the CommCell operations to the standby CommServe host in the event of a disaster. See Moving CommCell Operations to the Standby CommServe Host.
- Once the production CommServe host is operational, move back the CommCell operations to the production CommServe host. See Resuming CommCell Operations on the Production CommServe Host.
Last modified: 2/6/2020 8:36:26 PM