CommServe Hardware Refresh: Post Migration Operations

The following operations are recommended on the new CommServe computer after the hardware refresh.

Configure Cluster Environment

If you moved the CommServe database from a cluster to a cluster environment, you need to perform additional steps to configure the database in the new environment.

Note: If you moved the CommServe from a cluster environment to a non-cluster environment or from a non-cluster environment to a cluster environment, then no additional action is needed. The CommServe Recovery Assistant tool automatically detects the change in the cluster environment and performs the cluster migration as part of the recovery process.

Cluster to Cluster Configuration

Use the CommServe Recovery Assistant tool to configure the database when it is moved from a cluster to a cluster environment.

Step 1: Apply the Options to Migrate the CommServe Database from a Clustered Environment to a Non-Clustered Environment

  1. On the active node (where the CommServe software is installed), go to the Software_Installation_Path/Base folder.
  2. Double-click CSRecoveryAssistant.exe and follow the steps provided in Recovering the CommServe Database.

Step 2: Apply the Options to Migrate the CommServe Database from a Non-Clustered Environment to a Clustered Environment

  1. On the Cluster/Non-Cluster CommServe DB Migration tab, select the Cluster/Non-Cluster CommServe DB Migration check box.
  2. Under Migration Options, click Setup CommServe DB to Cluster.
  3. Under CommServe Physical Nodes, type the name 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.

  4. Click OK.

Step 3: Configure an Additional Setting to Send Update Status to the CommServe

  1. Log on to the CommCell Console.
  2. In the CommCell Browser, right click the <CommServe> computer, and then click Properties.
  3. Click the Additional Settings tab, and then click Add.
  4. In the Add Additional Settings on Windows Client dialog box, do the following:
    1. In the Name box, type bSendUpdateStatusToCS.
    2. In the Category box, type registry.
    3. From the Type list, select INTEGER.
    4. In the Value box, type 1.
    5. Click OK.
  5. Click OK to close the CommCell Properties dialog box.
  6. Restart the CommCell services using the Process Manager. For instructions, see Restarting a Service.

Resynchronize Deduplication Databases (DDB)

After hardware refresh, if there are inconsistencies between the DDB and the CommServe database during a backup or auxiliary copy operation, the DDBs are put in maintenance mode and an appropriate event message is displayed in the Event Viewer window. In such cases, run DDB Resynchronization to bring the DDBs online and revert it to a reusable state from maintenance mode.

For more information, see Resynchronizing the Deduplication Database.

Tune the SQL Server Memory Usage

If you pre-installed the SQL Server on the new hardware before the CommServe software was installed, we recommend you to verify the SQL memory usage for the SnapProtect components. The maximum memory used by the SQL Server should be 50% of the physical memory available in the new computer.

  1. On the CommServe computer, open the Microsoft SQL Server Management Studio.
  2. Right-click the Server_Instance, and then click Properties.
  3. From the Server Properties dialog box, on the left pane, select the Memory page.
  4. In the Maximum server memory (in MB) box, specify 50% of the physical memory available in the computer.
  5. Click OK.

Verify Port Numbers Used for Reports

If the IIS port number for reports has been changed, you must update the default URL for reports in the CommCell Console. For instructions, see Setting the Default Report URL.

Verify SnapProtect Network Components (If CommServe Name Changed)

If the new CommServe computer has a different name and IP address than the old computer, reconfigure each data interface pair (DIP) that exists between the CommServe computer and other clients. See Data Interface Pairs - Advanced for information on adding, editing or deleting DIPs.