Unable to protect 2 clusters with the same cluster name. Both the clusters are joined to different domains.
After protecting the first cluster, attempting to protect the second cluster results in this error "Unable to protect 192.168.1.2(dummy IP) because it already exists".
Attempts to change the display name of first cluster before protecting the second cluster will not resolve this issue.
Rapid Recovery will generate the agent ID of cluster based on the cluster name.
As both clusters having the cluster name, the same agent ID will be generated.
During protection of the second cluster, as the agent ID being generated, the Rapid Recovery core will discover that another agent/cluster with the same agent ID already present and will fail the protection process.
1. Protect the first cluster.
2. Change the display name of the first cluster.
3. Perform the following registry change to change the Agent ID of the first cluster.
Identify which is the agent id at HKLM\Software\AppRecovery\Core\Agents\"Cluster Agent ID". The "DisplayName" value would have shown the correct Agent ID for the cluster.
The "Cluster Agent ID" key will be in this example format 47257bd3-0000-0000-0000-000000000000.
Please perform a small change on the "Cluster Agent ID" . For example, 47257bd3-0000-0000-0000-000000000000 -> 47257bd4-0000-0000-0000-000000000000.
4. Perform the following registry change to change the "ParentClusterAgentId' value for all the nodes of the first cluster.
Identify which is the agent id at HKLM\Software\AppRecovery\Core\Agents\"Node Agent ID". The "DisplayName" value would have shown the correct Agent ID for the cluster.
For the "ParentClusterAgentId' value of all the nodes, please perform the same change of ID as step 3.
5. Restart the core service. Verify that the first cluster is still online and working fine.
6. Proceed to protect the second cluster.
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
This is a Rapid Recovery defect. The defect will be fixed in a later release of Rapid Recovery.