Deployment Guide › Clustered CMS Deployments › Upgrade a Clustered CMS From 12.0 to 12.5

Previous Topic: Test the Cluster

Next Topic: Apply Hotfixes and Service Packs

Upgrade a Clustered CMS From 12.0 to 12.5

To upgrade a clustered CA DLP 12.0 to 12.5

  1. Transfer control of the clustered CMS to the primary node.
  2. Select ‘Do not restart’ on the policies tab of the CA DLP Infrastructure resource.
  3. Open a command prompt on the primary node. Run the CA DLP 12.5 server install and specify the CMS Cluster Network Name in the WGNINTERNALMACHINENAME property: 
    msiexec /i c:\DLP_AdminInstall\server.msi WGNINTERNALMACHINENAME=V-CMS

    The InstallShield Wizard opens.

  4. Follow the InstallShield Wizard and restart if a restart is requested.

    The server is installed.

  5. Right-click the V-CMS node, click Move this service or application to another node, and click MACHINE2.
  6. Open a command prompt on the secondary node. Run the CA DLP 12.5 server install and specify the CMS Cluster Network Name in the WGNINTERNALMACHINENAME property: 
    msiexec /i c:\DLP_AdminInstall\server.msi WGNINTERNALMACHINENAME=V-CMS

    The InstallShield Wizard opens.

  7. Follow the InstallShield Wizard and restart if a restart is requested.

    The server is installed.

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

To test the upgraded cluster

  1. Verify the controlling node has brought all resources online and that the CA DLP 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.