Staging the CommServe Database Using Disaster Recovery Tool

Use the CommServe Disaster Recovery Tool to stage your production CommServe database on another CommServe host for troubleshooting purposes. This process is used by administrators strictly for troubleshooting the CommServe database.

Note: If you are using the tool for disaster recovery purposes, see Restoring CommCell Operations on the CommServe Host.

About This Task

During test or staging mode, you can restore the CommServe database and other CommServe hosted databases included in the DR backup.

After recovery, the tool automatically performs the following post staging operations on the CommServe database, so that the database is not reachable to any clients or MediaAgents in the CommCell group:

  • Remove mail server from the database
  • Reset all passwords
  • Reset admin password
  • Disable alerts
  • Disable schedules
  • Disable clients
  • Disable MediaAgent
  • Update Windows Version for CommServe
  • Disable All Activity
  • Suspend Running Jobs
  • Revoke all client certificates
  • Disable all client hostnames
  • Reset all network passwords

For more information on post staging operations, see Post Staging Operations.

Before You Begin

  • Use SnapProtect Process Manager to stop all services on the CommServe host. See Stopping a Service
  • Ensure that the correct version of the disaster recovery backup files (SET_XXX folder), that you want to restore, is available on the CommServe. You can find the disaster recovery backup Job ID and the time when the backup job completed in the version.txt file in the SET_XXX folder. Note that Disaster Recovery Backup files (.dmp) are portable between CommServe computers running Microsoft Windows Server 32-bit and x64 edition operating systems.
    • 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.

Procedure

  1. On the CommServe computer, navigate to the installation_directory\Base folder.
  2. Double-click CommserveDisasterRecoveryGUI.exe.
  3. In the CommserveDisasterRecoveryGUI dialog box , from the Select reason for DB restore drop-down box, select Test/Staging.
  4. On the Restore Database tab , click the Restore DB check box.
  5. If you need to provide different SQL Server account credentials, under Destination SQL Server Info, click Log in as:.
  6. If you need to restore only the CommServe database from multiple databases in the disaster recovery backup, click Restore Single Database.
  7. In the Restore File box, enter or browse the name of the Disaster Recovery export folder (SET_XXX folder) where the dump files are located.

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

    By default, all the metadata files in the SET_XXX folder are restored in the same path as located on the production CommServe host.

  8. If you need to migrate the CommServe database to a clustered or non-clustered environment, complete the following steps:
    1. Click the Cluster/Non-Cluster CommServe DB Migration tab and select the Cluster/Non-Cluster CommServe DB Migration check box.
    2. Do one of the following:
      GOAL ACTION
      Migrate from clustered to a non-clustered environment Select Setup CommServe DB to Non-Cluster.
      Migrate from a non-clustered environment to a clustered environment
      • Select Setup CommServe DB to Cluster.
      • Under CommServe Physical Nodes, 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.

      Migrate from a clustered environment to a clustered environment
      • Select Setup CommServe DB to Non-Cluster.

        Leave the Disaster Recovery tool open and wait for the operation to complete.

      • Select Setup CommServe DB to Cluster.
      • Under CommServe Physical Nodes, 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.

      • Configure the bSendUpdateStatusToCS additional setting to send the update status to the CommServe database.
  9. Click OK to start the restore operation.

What to Do Next

When finished, use the Process Manager to start all services on the CommServe host.