CommServe Recovery Process Flow

In the event of a disaster, when the production CommServe host becomes unusable or inaccessible, use the CommServe Recovery Assistant 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 clients, stubbing is delayed by default to ensure that the last backup is included in the DR backup.

To recover your CommServe database 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.

    Make sure the computer name of the new host is same as that of the old CommServe host. For information on how to change the computer host name of a Windows Server, see Microsoft documentation.

    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 Recovering the CommServe Database.

    See Recovering the CommServe Database Using the Command Line Interface to use the tool from the command line.

    If an export copy of the Disaster Recovery (DR) backup metadata does not exist, you must first retrieve the metadata from the backup. See Retrieving Disaster Recovery (DR) Backups from Media for more information.

  4. Start CommCell services on the standby CommServe host. For instructions, see Starting a Service.
  5. Using DNS, configure the host name of the old CommServe computer to point to the IP address of the new computer.

    If you do not use DNS, contact customer support for assistance.

    Important: Verify that all client computers point to the host name of the old CommServe computer, and not to the IP address. For instructions on changing the CommServe name on clients, see Changing the Client Computer Name.

  6. 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.

  7. If you have a Silo Archive job running, commit the SILO job. See Committing Silo Backup Jobs for more information.
  8. Schedule disaster recovery backups on the new CommServe host.