Recovering Your CommServe Database

The CommServe disaster recovery process involves three important operations:

  • Recovering the CommServe database

    The most recent changes in the production CommServe database must be available on a new or standby CommServe host.

  • Accessing the backup data

    If the new or standby CommServe host is set up at a remote recovery site, it may not have access to all the MediaAgents and storage resources available at the production site. In such cases, create additional copies of the backup data that are accessible from the standby CommServe host.

  • Installing latest updates on the standby CommServe host

    All the latest software updates installed on the production CommServe host must also be available on the new or standby CommServe host.

Component Checklist for Disaster Recovery

Recovering CommCell operations on new hosts can range from ad-hoc procurement of new computers when needed to designating existing computers specifically for disaster recovery use, preinstalling CommCell components, and staging copies of protected media for immediate access. The scale of your CommCell environment, network connections, and recovery time objectives dictate the CommCell components required to meet your recovery objectives.

Required Common Components

Common components needed for recovery from a CommCell disaster are:

  1. Compatible hardware (provided as needed or in the standby configuration)
  2. Installation software (cached or downloadable from the website)
  3. Latest service packs and hot fixes (cached or downloadable from the website)
  4. CommServe databases (exported, backed up, or mirrored)
  5. TCP/IP network connectivity (provided as needed or existing) CommCell license (existing dual or new license for alternate IP address)

The speed at which these components can be provided determines the time it takes to recover from a CommCell disaster.

Of the required components, the most critical and irreproducible component is the CommServe database. The CommServe database includes the primary CommCell configuration.

Protected Databases

In addition to the CommServe database, you must also protect the following databases if they are configured in the CommCell group.

  • DM2 (Web Server)

    To perform web console operations.

  • Cvcloud (Private Metrics Reporting Server database)

    To enable metrics reporting based on data collected from your CommCell computers by using the standby CommServe host.

  • WFEngine (Workflow Engine)

    To perform workflow operations.

As an administrator, review their CommCell recovery requirements and take necessary actions to protect and ensure that the CommServe database is available to the standby CommServe host.

CommCell Recovery Priority and Dependency

Depending upon the extent of the disaster, some or all of the following components may require re-installation or restoring. The order in which you recover these components is important. To restore the CommCell functionality, apply the following CommCell recovery priority/dependency.

  1. CommServe host (required hardware/software)
  2. CommServe database (metadata)
  3. MediaAgent host (required hardware/software)
  4. Library to access protected storage media
  5. Protected storage media (i.e. media that contains or can contain protected data )
  6. Client host (required hardware/software)

If your recovery objective is to restore functionality of a client host or production service, the critical component is the media containing the protected data. Creating multiple offsite copies and using vaulted storage locations are prudent steps to ensure availability of client data for recovery.

Disaster Recovery and Deduplicated Data

If deduplication is enabled for any storage policy, when you restore the CommServe functionality on another host, the CommServe database may become out-of-sync with the deduplication database (DDB). As a result, products with Service Pack 7 or later must resynchronize their DDB databases after restoring the CommServe database.

For more information, see Resynchronizing the Deduplication Database.