|
|
|
Installing on clusters is much the same as a standard installation. To configure CA ARCserve HA on a cluster, enter the Virtual Server Network Name (or IP Address) resource (in the group you intend to protect) as the Master or Replica name. Do not use node names or IP addresses when configuring the scenario. Also, you must install the CA ARCserve RHA Engine to all cluster nodes (see Server Setup).
The only configuration that requires some preparation is the use of IP Move with a cluster. For more information about how you can use Move IP with clusters, please see Cluster Move IP.
CA ARCserve Replication has been enhanced so that the IIS metabase is fully protected. You no longer are required to first create websites on the Replica before running an IIS HA scenario. While HA scenarios are running, the metabase is periodically replicated.
Note: Metabase protection is supported only with IIS 6.0 and 7.0/7.5 in CA ARCserve Replication HA scenarios.
High availability scenarios can now monitor and restore IIS services in addition to sites using the Is-alive check. This enables CA ARCserve Replication to recognize that if one particular IIS service is down, the corresponding site is not necessarily down as well. The Is-alive check monitors a list of IIS services participating in an HA scenario, checking the status for each and restoring any service that is down. This ensures CA ARCserve Replication does not attempt to restart a site that is still running.
IIS auto-discovery in a Microsoft Cluster Server environment has also been enhanced so that all local sites, or sites containing a path not on the shared MSCS disk, are identified and automatically excluded from the scenario, so that you may run scenarios with default settings.
Note: RHA only protects the meta data of the application pools that are associated with selected websites, other application pools are not synchronized or replicated.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |