CommServe Recovery Using Disaster Recovery Backup

In the event of a disaster, when the production CommServe host becomes unusable or inaccessible, use the Disaster Recovery tool to restore the most recent disaster recovery backup of the production CommServe database to a new CommServe host and resume the CommCell operations.

During recovery, you must have the latest full Disaster Recovery (DR) backup and the latest differential DR backup to build the standby CommServe host. Once restored, the database reflects the state of the production CommCell group when the DR backup was performed. Based on the frequency of the DR backup, you may lose some data such as information about backup operations, entity creation or configuration changes, when you move the CommCell operations to the standby CommServe host.

After recovering the CommServe database, the clients are updated to use the standby CommServe host. In large CommCell environments, renaming the CommServe name on all the clients is a time consuming task. In such cases, you can avoid renaming the CommServe name by using a dedicated proxy for disaster recovery. The proxy is used to route requests and responses between the CommServe and the proxy-enabled clients. For instructions on configuring a proxy for disaster recovery, see Using SnapProtect Proxy for Disaster Recovery.

Note: In a CommCell group with File Archiver agents, if the archived file was stubbed or deleted before the last backup was included in the DR backup, then recalls that use the stub may fail after the DR restore. However, for OnePass agents, stubbing is delayed by default to ensure that the last backup is included in the DR backup.

To recover your CommServe database by using DR backups, complete the following tasks in the order listed:

  1.  Stop services on the production CommServe host.
  2. Install the CommServe software on a new host.

    All the latest software updates that were installed on the production CommServe host must be installed on the new CommServe host.

  3. Restore the CommServe databases from the DR backup to the new CommServe host. For instructions, see Restoring CommCell Operations on the CommServe Host.
  4. Start CommCell services on the standby CommServe host. For instructions, see Starting a Service.
  5. Resynchronize the Deduplication Databases (DDB).

    After restoring the CommServe database, any DDBs that are inconsistent with the CommServe database are put into maintenance mode automatically. Therefore, you must synchronize the inconsistent DDBs to a reusable state. For information on synchronizing the DDB, see Resynchronize the Deduplication Database.

    Important: If the restore was performed using a DR backup older than five days, you must seal existing Deduplication databases after restoring the CommServe database. For more information, see CommServe Disaster Recovery Tool - Post Recovery Options.

  6. Update the CommServe Name for all Clients and MediaAgents.
  7. Schedule disaster recovery backups on the new CommServe host.