Implementing CA ARCserve Backup › Installing and Upgrading CA ARCserve Backup in a Cluster-aware Environment › Deployment Considerations

Deployment Considerations

Before you begin to deploy CA ARCserve Backup into a cluster environment, you need to be aware of the following considerations:

• Supported operating systems--For information about supported operating systems, see the CA ARCserve Backup Readme file.
• Required Cluster Resource Considerations--As with other cluster-aware applications, the CA ARCserve Backup HA server needs to bind itself with some cluster resources, including a shared disk and a virtual name/IP address. Clusters resources can be grouped together to allow you to install CA ARCserve Backup into an existing group and bind it with the existing cluster resources already established for that group, or to create a dedicated group for CA ARCserve Backup deployment.
• Special Installation/Configuration Considerations--To deploy CA ARCserve Backup into all cluster nodes, you need install the same CA ARCserve Backup components on all nodes, and each of these components must be configured in the same way. The CA ARCserve Backup system accounts must be the same for all CA ARCserve Backup servers installed on each of the cluster nodes.

  Note: The setup program for cluster machines does not support remote installation of the CA ARCserve Backup base product or the CA ARCserve Backup agents. This remote install limitation for the CA ARCserve Backup agents (for example, the Agent for Microsoft SQL Server and the Agent for Microsoft Exchange Server) only applies if you use a virtual host. Remote installation of CA ARCserve Backup agents using the physical hosts of clusters is supported.

• Failover Trigger Mechanism Considerations--CA ARCserve Backup has its own cluster resource Dynamic Link Library functions (DLL) and scripts to extend the cluster service capabilities to monitor and detect CA ARCserve Backup failures. The network name and IP address of a virtual server allows CA ARCserve Backup to appear as a single system and take advantage of the capabilities of cluster management tools.
• Upgrade Considerations--To ensure that all CA ARCserve Backup services start properly, you must execute the cstop and cstart scripts after you complete the upgrade process and before you open the CA ARCserve Backup Manager Console. You must perform this task when you upgrade from CA ARCserve Backup r12 (includes the GA release and all of the latest service packs), CA ARCserve Backup r12.5 (includes the GA release and all of the latest service packs), and CA ARCserve Backup r15 (includes the GA release and all of the latest service packs) to this release.

  The cstop and cstart batch files are stored in the CA ARCserve Backup installation directory on the CA ARCserve Backup server.

  Note: For more information about using cstop and cstart, see the Administration Guide.