Building a Standby CommServe Host for Disaster Recovery

You can reduce the downtime to recover your CommServe database by assigning a dedicated computer host with preconfigured software as an alternate or standby CommServe host. As CommServe functionality is critical to CommCell operations, you can assign a computer as the standby CommServe host, install the CommServe software, and replicate the production (active) CommServe databases to the standby host periodically.

For this method, the Microsoft SQL Server Agent is used to back up the database and transaction logs from the production CommServe host and restore in standby mode to the standby CommServe host. The database is restored when you first set up the standby CommServe host and transaction logs are restored every time you perform the transaction log backup on the production CommServe host. This method is often referred to as log shipping.

You can build the standby CommServe host using one of the following configurations:

Basic Configuration

In the event of a disaster, use this configuration if you plan to fail over the CommServe functionality manually and redirect selected clients to the standby CommServe host. This configuration type requires minimum resources and a reduced recovery time. Moreover, you can also check disaster readiness easily without bringing down the CommCell services on the production CommServe host.

For more information, see Basic Configuration.

Advanced Configuration

Use advanced configuration, if you want to automatically monitor the availability of the active CommServe host and send alert notifications or take failover decisions accordingly. With advanced configuration, the recovery down time is minimal. However, you will require additional resources and configuration.

For more information, see Advanced Configuration.

Optional Configuration:

You can also use the Microsoft SQL Server database mirroring feature 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.

For more information on mirroring the CommServe hosted databases, see Recovery Using SQL Server Database Mirroring.

Related Topics

Standby CommServe Host Requirements