Views:

Summary

If IP addresses on Windows cluster nodes are changed, the Cmagents for the cluster on these nodes fail to start. To resolve this issue, use the procedure to check that the current IP addresses for all nodes are in the registry entries.

 

Symptoms

After IP addresses on Windows cluster nodes are changed, the Cmagents for the cluster on these nodes fails to start.

 

Resolution

On Windows cluster nodes, the Cmagent for the cluster is associated with the IP address in SSCMAPI:

-hn<IP address>

SSCMAPI is a registry value stored under registry key HKLM\Software\Syncsort\BackupExpress\<ClusterName>\0. The Windows cluster service, as configured in cluster group Backup Express\Backup Express Cmagent, replicates this registry key.

If you change the IP addresses on cluster nodes and later attempt to run the Cmagent service, the service does not start because the IP addresses in SSCMAPI revert to the old IP addresses. This happens even if you previously changed all occurrences of the IP addresses in the Windows Cluster Administrator and updated the registry value SSCMAPI with the new IP addresses.

To resolve this issue:

  1. In the Windows Cluster Administrator, select:
    Groups > Backup Express > Backup Express Cmagent > Properties > Registry Replication.
    Keep a copy of the Root Registry Key, then delete it.


     
  2. Stop all Cmagent services on all cluster nodes.
     
  3. Check all the registry entries under HKLM\software\Syncsort for all cluster nodes and ensure that all of the IP addresses are new.
     
  4. Start Cmagent services on each node (two per node).
     
  5. In the Windows Cluster Administrator, bring the Cmagent online.
     
  6. To confirm that the Cmagent is running, perform a failover for the Backup Express group.
     
  7. Re-enter the Root Registry Key from step 1 into Registry Replication.