CA ARCserve RHA Components and Deployment › CA ARCserve RHA Deployment

CA ARCserve RHA Deployment

The deployment of CA ARCserve RHA components depends on the size of your IT enterprise network and your replication and HA needs. However, there are certain guidelines that you should follow when designing your Replication and High Availability environment and deploying the different components on a Windows platform. The following section provides information regarding an efficient deployment of CA ARCserve RHA components.

The following illustration shows a typical deployment of CA ARCserve RHA components:

• CA ARCserve RHA Control Service

  The Control Service must be able to connect to all Master and Switchover Replica servers. It is not mandatory that the Control Service have a direct connection to each non-Switchover Replica server in the scenarios.

  We recommend installing the Control Service on a separate server. If you are working with High Availability scenarios, do not install the Control Service on either the Master or the Replica hosts.

  You can install the Control Service on your local workstation. However, you should be aware that if this workstation is disabled or offline, you will not be able to monitor or manage your scenarios.

• CA ARCserve RHA Engine

  The Engine must be installed on each Master and Replica server that participates in the defined scenarios.

• CA ARCserve RHA Management Center

  This component can be opened from any workstation that has a browser and network connectivity to the Control Service.

• CA ARCserve RHA PowerShell

  This component can be opened from any workstation that has Windows PowerShell and network connectivity to the Control Service.