Platform Deployment Guide › Clustered CMS Deployments › Upgrade a Clustered CMS

Upgrade a Clustered CMS

To upgrade a clustered CA DataMinder

1. Transfer control of the clustered CMS to node 1.
2. Select ‘Do not restart’ on the policies tab of the CA DataMinder Infrastructure resource.
3. (Only required if you are upgrading from 14.0 or earlier) On the primary node, migrate the existing product registry key to the new CA DataMinder registry key.

   To migrate the registry key, you must run the migreg.exe utility from a command line on the primary node. For details, see the 'Pre-Upgrade Tasks' chapter in the Upgrade Guide.

   Note: CA Technologies is renaming its security portfolio to follow the Minder product family. In particular, CA DLP has been renamed to CA DataMinder in the current release. In parallel with this product name change, the registry key used by CA DataMinder components has also been renamed.

4. Open a command prompt on the primary node.

   Run the CA DataMinder server installation wizard and specify the CMS Cluster Network Name in the WGNINTERNALMACHINENAME property. For example:

   msiexec /i c:\DLP_AdminInstall\server.msi WGNINTERNALMACHINENAME=V-CMS
   

   The installation wizard opens.

5. Step through the wizard screens. Restart the server if requested.

   The CMS on the primary node is upgraded.

6. Right-click the V-CMS node, select Move this service or application to another node, and click MACHINE2.
7. (Only required if you are upgrading from 14.0 or earlier) On node 2, migrate the existing product registry key to the new CA DataMinder registry key.

   See step 3 for details.

8. Open a command prompt on node 2.

   Run the CA DataMinder server installation wizard and specify the CMS Cluster Network Name in the WGNINTERNALMACHINENAME property. For example:

   msiexec /i c:\DLP_AdminInstall\server.msi WGNINTERNALMACHINENAME=V-CMS
   

   The InstallShield Wizard opens.

9. Step through the wizard screens. Restart the server if requested.

   The node 2 CMS is upgraded.

10. Open the advanced policies tab of the CA DataMinder Infrastructure resource and set the policies for the infrastructure resource in line with your failover strategy.

To test the upgraded clustered CMS

1. Verify the controlling node has brought all resources online and that the CA DataMinder infrastructure has started correctly.
2. Connect a remote Admin Console to the virtual CMS. Do some operations, fail the CMS over to the other node and see if the connection recovers from the remote Admin Console.
3. From a remote iConsole, verify that data can be retrieved successfully when either node has control.