Loading...

Recovering the CommServe Database

You can recover your CommServe database from a disaster recovery backup to the same or a different CommServe host using the CommServe Recovery Assistant tool. The tool is primarily used in the following scenarios:

  • Rebuild your CommServe host from a disaster
  • Upgrade or move the CommServe database to a new hardware
  • Migrate the CommServe database from either a clustered environment to a non-cluster environment, or from a non-clustered environment to a clustered environment.

Note: If you are using the tool to stage the CommServe database for troubleshooting purposes, see Staging the CommServe Database.

Before You Begin

Review the following tasks:

  • Review CommServe Recovery Process Flow.
  • Run a full backup of the CommServe databases on the destination CommServe host to ensure that no current activity is lost. For instructions on performing a Disaster Recovery Backup for a CommServe database, go to Performing a Disaster Recovery Backup.
  • Stop services on the original production CommServe host. See, Stopping a Service.
  • If you are restoring to a different or a new CommServe host, obtain a new IP address change license from your software account manager or support.
  • Make sure that the destination CommServe host is at the same service pack level as the DR backup or higher.
  • Make sure that you have the latest version of the disaster recovery backup (SET_XXX folder) on the destination CommServe host.
    • If you have the disaster recovery backup files in the network location, copy the files to the local disk on the CommServe host.
    • If you have the disaster recovery backup files on a disk or tape media, see Retrieving Disaster Recovery Backup from Media.
  • If the IP address of the destination CommServe host is different from the original CommServe host, contact your SnapProtect Account Manager or Support for a new license..

Procedure

  1. On the CommServe computer, go to the <software installation path>\Base folder.
  2. Double-click CSRecoveryAssistant.exe.
  3. In the CommServe Recovery Assistant dialog box, click Recovery, and then click Next.
  4. If you have already restored the CommServe database on this computer, select the Database already restored on this computer check box and click Next.
  5. In the Enter the path to the database dump folder box, enter or browse the name of the Disaster Recovery folder where the dump files are located, and then click Next.

    Make sure that the dump files are available on the local disk of the CommServe host.

  6. In the Enter the path to extract the database files box, type the destination path where you want to restore the CommServe database files and then click Next.

    Alternatively, click Browse and select the restore path.

    By default, all the database files are restored to the CommServe database path located on the destination CommServe host.

  7. In the Summary screen, review the selections, and then click Start Recovery.

    The tool now performs the following operations on the CommServe system:

    • Stop services on your CommServe computer
    • Restore the database to the specified restore path
    • Verifies and upgrades the database if required

      The tool can upgrade the database from a previous version or service pack.

    • Synchronize the CommServe system and the restored database
    • Run post operations on the CommServe computer
  8. When all the operations are complete, click Next.

    The host name and client name of the destination CommServe host and the restored database are displayed. If the names are different, the tool updates the CommServe host with the client name of the restored database and host name of the destination CommServe host.

  9. If the IP address of the destination CommServe host is different from the original production CommServe host, select the Provide a license file check box and enter the path to a new IP address change license file in the text box provided and click Next.

    Note: If you do not have a new license, contact your SnapProtect Account Manager or Support for a new license.

    It is optional to provide a license file if the tool detects no change in the CommServe IP address in the existing license file.

  10. If you are migrating the database from a non-clustered to a clustered environment, complete the following steps:
    1. Select the Convert to cluster check box.
    2. In the Physical Node text boxes type the names of the physical CommServe nodes as they appear in the Microsoft Failover Cluster Manager.

      Do not copy and paste the physical node name from the registry, or add the characters "_node" to the node name. The characters "_node" are automatically added to the physical node name during the database restore operation.

    3. Send the update status to the CommServe database by configuring the bSendUpdateStatusToCS additional setting.

      On the CommServe computer, add the bSendUpdateStatusToCS additional setting with value1. For instructions on adding the additional setting from the CommCell Console, see Add or Modify an Additional Setting.

      Refer to the following table for applicable values:

      Property Value
      Name bSendUpdateStatusToCS
      Category UpdateFlags
      Type Integer
      Value Select one of the following values:
      • 1 - to send the update status information to the CommServe database during client service restarts
      • 0 - to disable the update status sync
  11. If you are migrating the database from a clustered to a non-clustered environment, select the Convert to non-cluster check box and click Next.
  12. A completion message is displayed. Click Finish.

Result

After the DR restore, you will notice a considerable increase in the job ID for new jobs. This increase is added to avoid conflicts with job IDs referenced in the deduplication databases (DDBs) when the DDBs are resynchronized.

What to Do Next

When finished, start all services on the destination CommServe host. See, Starting a Service.

Complete the steps described in CommServe Recovery Process Flow.