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 to/from a cluster environment, you may need to perform additional steps to configure the database in the new environment.

Select the procedure applicable to your environment.

  • Cluster to Cluster Configuration

    Use this procedure if you moved the CommServe database from a cluster environment to another cluster environment. No action is needed If the name of the physical nodes for the new CommServe computer are the same as the old computer.

  • Non-Cluster to Cluster Configuration

    Use this procedure if you moved the CommServe database from a non-cluster environment to a cluster environment.

  • Cluster to Non-Cluster Configuration

    If you moved the CommServe from a cluster environment to a non-cluster environment, then no additional action is needed.

Cluster to Cluster Configuration

Use the CommServe Disaster Recovery 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

Skip this step if you upgraded your CommServe database from version 8 to version 10.

  1. On the active node (where the CommServe software is installed), navigate to the <software installation path>\Base folder.
  2. Double-click CommserveDisasterRecoveryGUI.exe. The CommserveDisasterRecoveryGUI dialog box appears.
  3. Click the Cluster/Non-Cluster CommServe DB Migration tab, and then select the Cluster/Non-Cluster CommServe DB Migration check box.
  4. Under Migration Options, click Setup CommServe DB to Non-Cluster, and then click OK.

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

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

  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.

Non-Cluster to Cluster Configuration

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

  1. On the CommServe computer, navigate to the <software installation path>\Base folder.
  2. Double-click CommserveDisasterRecoveryGUI.exe.
  3. Click the Cluster/Non-Cluster CommServe DB Migration tab, and then select the Cluster/Non-Cluster CommServe DB Migration check box.
  4. Under Migration Options, click Setup CommServe DB to Cluster.
  5. 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.

  6. Click OK.

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, select the Memory page on the left pane.
  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.

  1. Verify the port number in IIS.
  2. In the CommCell Console, click the Configuration tab, and then click Email and Web Server.

    The E-Mail and Web Server Configuration dialog box appears.

  3. Click the Web Server tab.
  4. In the Report Default URL box, enter the new port number that is specified in IIS and the rest of the default URL.

    For example:

    http://commcell1:89/reports

  5. Click OK.

Verify SnapProtect Network Components (If CommServe Name Changed)

If the new CommServe computer has a different name and IP address than the old computer, then check the following network components:

  • Data Interface Pairs

    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.

  • Firewall Settings for Version 8 Clients

    Update the host name of the CommServe computer in the fwhosts, fwports and fwpeers files of each version 8 client computer. The firewall files are located in the <Software Installation Path>\Base folder of each client computer.

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.