Install, Upgrade and Uninstall CA ARCserve RHA › Install CA ARCserve RHA for Microsoft Failover Cluster

Install CA ARCserve RHA for Microsoft Failover Cluster

On each node in your cluster environment, run the CA ARCserve RHA MSFC plug-in called CAARCserveRHAforMSFC.exe or CAARCserveRHAforMSFC64.exe (64-bit version) to launch the InstallShield wizard, which guides you through the process of installing the CA ARCserve RHA Disk Resource for Microsoft Failover Cluster and the CA ARCserve RHA Disk Cluster Manager MMC Snap-in.

Complete the wizard screens to install the CA ARCserve RHA for Microsoft Failover Cluster. You may choose Complete or Custom Setup.

• Complete -- installs all program components
• Custom -- installs the components you specify

Note: After installation, you should restart the CA ARCserve RHA Engine before you create a disk resource. Microsoft .NET Framework 3.5 is required. If the software does not detect it, you are prompted to install it and then retry installation.

During installation, the required processes are added to the Windows Firewall as exceptions. If you are using another firewall product or have manually configured one, you must remember to add the CA ARCserve RHA for Microsoft Failover Cluster processes as exceptions to ensure proper communication between MMC and the CA ARCserve RHA Engine.

Upgrade an Installation

Although CA ARCserve RHA is different from the previous version in many respects, there is no major difference between a new installation and an update to an existing one. The system automatically detects previous components, and the MSI wizard carries out all the required tasks to upgrade the application. Most of the components from a previous version can stay on your network, and you can import existing scenarios and reuse them through the CA ARCserve RHA Manager.

Important! Full System scenario must be re-run at least once after you upgrade to r16.0 SP2 from a previous release.

Note: The scenarios that were created in the previous version were saved by default in INSTALLDIR:\Program Files\CA/ARCserve RHA\ws_scenarios. For more information about the import process, see CA ARCserve RHA Administration Guide.

For a successful upgrade, the only component you need to remove is the previous CA ARCserve RHA Engine. Therefore, you need to uninstall CA ARCserve RHA from each Master and Replica server. You can either use the Setup.exe file to automate this procedure or you can do it manually before you start the new installation.

Note: If you are trying to install the Control Service on a machine that contains a GUI from a previous version, you will get the following message:

A previous version of CA ARCserve RHA has been detected. You don't need to remove it in order to install the new version.

Click OK, and continue the installation.

To remove a former Engine using the setup.exe file:

1. Double-click the Setup.exe installation file. The CA ARCserve RHA Installation wizard appears.
2. Click the Install option. The Install Components page appears.
3. Click the Install CA ARCserve RHA Engine option. Click the Install CA ARCserve RHA Engine option.

   The Choose Setup Language dialog appears.

4. Select from the drop-down list the Installation wizard language you prefer, and click OK.

   A progress bar appears.

5. Once the initial process is completed, the Welcome page appears.
6. Click Next. The system detects that an old Engine exists on your server, and the Information about previous version page appears.
7. To automatically remove the older Engine, click Next. A progress bar appears.
8. Once the removal process is completed, the License Agreement page appears.
9. Follow the wizard's instructions until the installation is complete, as described on Installing the CA ARCserve RHA Engine.

Note: All existing bookmarks and rewind points are lost after the upgrade.

Upgrade in Phases

This release of CA ARCserve RHA is backwards compatible with the previous version, so you can upgrade over time.

To run CA ARCserve RHA in a mixed environment, consider the following:

• Upgrade the Control Service first.
• If you are not planning to upgrade the Master and Replica servers at once, make sure you upgrade the Master before the Replica. Backward replication is not supported until both servers are upgraded.
• For HA scenarios, you must upgrade Master and Replica servers at once.
• You cannot create new File Server or application scenarios when the running an older version of the Engine, but may create new CD scenarios.

XONET Proxy Application

The XONET Proxy Application is a TCP/IP-based service that enables prior and current versions of CA ARCserve RHA Engines to exist on the same network port. Use it when you wish to gradually upgrade a large Content Distribution installation base. See the topic, Uninstall v4 and Proxy Applications, when you are ready to remove the previous version.

XONET configuration is automatically performed during the upgrade process. When you install the upgrade to another port, XONET monitors port 25000 and analyzes incoming connections. All v4 connections are routed to port 24000 (default) and all connections for the current version are routed to port 26000 (default).

For more information, see the topic, Installation Program Enhancements.

Note: XONET Proxy supports Windows platforms only.

InstallShield Package

The InstallShield package for CA ARCserve RHA has been enhanced with a new Preserve v4 option to support a phased upgrade plan. Enable this option to retain prior installations when installing the current CA ARCserve RHA version. The installation program modifies the existing port setting stored in the v4 ws_rep.cfg file to 24000 and installs a new ws_rep.cfg file with the port setting of 26000.

The remote installer also supports installations that preserve v4. During scenario verification, the remote installer discovers the versions of all CA ARCserve RHA products installed on the target machine. When v4 is discovered, the Installation Settings dialog contains an additional option, "Uninstall Engine of version 4 before upgrade." This option is enabled by default. If you wish to preserve v4, clear the checkbox to display additional fields. Your v4 scenarios are automatically imported and converted.

Important! If you install the XONET Proxy on a Microsoft Cluster, you must also install hot fix T5LT025 or the proxy will not work. To obtain the fix, contact Support to request it.

Version 4 port

This is the port number to which the v4 Engine will be moved. The default value, 24000, should not be changed.

Proxy port

This is the port number on which the XONET Proxy application listens. The default value, 25000, should not be changed.

Port number

This is the port number where the Engine for the current version listens. The default value, 26000, should not be changed.

The installation program also does the following:

• Migrates all v4 Delegated security users into Delegated Security groups corresponding to the current version
• Imports and converts scenarios created in prior version to current version
• Lets you uninstall v4 and proxy applications at will

Note: Proxy installation is automatically performed during upgrade; no separate executable exists.

Uninstall v4 and Proxy Applications

You can uninstall v4 and proxy applications manually, on a per-server basis.

To uninstall v4 and Proxy Application

1. Stop the XONET proxy service via Services applet.
2. Run the XONET proxy service with the -uninstall switch to remove the service.
3. Remove the XONET proxy application from the disk, if desired.
4. Uninstall v4 WANsync using the Add/Remove programs option in Windows Control Panel.
5. Edit the Port setting in the ws_rep.cfg file for the current version to 25000.
6. Restart the Engine via Services applet.

Troubleshooting XONET Proxy

Symptom:

I cannot access the Engine from the user interface (it is displayed as disconnected).

Solution:

Do the following:

1. Verify that the Engine service is up and running (go to the services applet and check the status of the Engine).
2. Verify that proxy service is up and running (go to the services applet and check the status of CAXOProxy service)
3. Verify that the Engine ports for both the v4 and current versions correlate with proxy service ports configuration. Default proxy ports configuration (go to services applet and double-click proxy service entry. Verify parameters in the Path to executable field).
   1. Main proxy port 25000.
   2. v4 proxy port 24000 (v4 Engine port should listen on this port; check v4 ws_rep.cfg).
   3. current version proxy port 26000 (Engine should listen on this port; check ws_rep.cfg).
4. Verify that scenarios for both v4 and the current version refer to the main proxy port (in Scenario, Engine options, the Engine port should be set to the main proxy port default value (25000).