This section provides information about the configurations and log on account requirements of each supported application and database server and for each replication solution.
Note: The configurations and requirements of a File Server are described in Installing the CA ARCserve RHA Engine.
This section contains the following topics:
Supported Application and Database Servers
File Server Replication and High Availability
Microsoft Exchange Server Replication and High Availability
Microsoft SQL Server Replication and High Availability
Oracle Server High Availability
Microsoft Hyper-V Server Replication and High Availability
Microsoft SharePoint Server Replication and High Availability
vCenter Server Replication and High Availability
Microsoft Dynamics CRM Replication and High Availability
Configure BlackBerry for CA ARCserve RHA
Control Service High Availability
The Replication and High Availability solutions are custom-tailored for the following application and database servers, for both 32-bit and 64-bit Windows:
CA ARCserve RHA can also transfer full systems to virtual machines. For an up-to-date list of supported platforms and applications, see the CA ARCserve RHA Supported Configurations document at the CA Support website.
Important! For all supported servers, you must statically assign all IP addresses (DHCP-assigned IP addresses on the Master or Replica server are not supported).
This section describes the requirements for running CA ARCserve RHA for File Server.
To implement High Availability procedures for File Server, you need to have the following configurations:
Note: For a complete list of supported operating systems and applications, see the CA ARCserve RHA Release Notes.
The CA ARCserve HA service log on account must satisfy all of the following account conditions:
For servers in a workgroup, set the CA ARCserve RHA Engine service account to Local System (unless you have added any custom scripts that require higher level permissions). Servers in a workgroup can use Redirect DNS only with DNS servers that allow non-secure updates. You can use Move IP, Switch Computer Name, and custom redirection scripts normally.
This section describes the CA ARCserve RHA configuration requirements for Microsoft Exchange Server.
This section describes the requirements for running CA ARCserve RHA for Exchange Server.
To implement Replication for Exchange Server, you need to have the following configurations:
Note: For a complete list of supported operating systems and applications, see the CA ARCserve RHA Release Notes.
Note: Exchange Server 2010 does not permit you to create two databases with the same name on Master and Replica servers, even if the database is dismounted. Use a name for the Replica database that is less than 64 characters long and follows this convention:
<ReplicaName>=<MasterName>_xxxx
Where xxx = random number.
The CA ARCserve RHA Engine service log on account must meet all of the following conditions:
Note: If your company's security policy requires even more granular permissions than described, contact CA technical support to receive detailed instructions on permissions required.
With CA ARCserve RHA, working with clusters is nearly identical to working with stand-alone servers. Simply enter the "Exchange Virtual Server Name" as the Master or Replica server name where appropriate.
On Exchange 2007, CA ARCserve RHA supports LCR deployments. No additional configurations are required.
Note: On Exchange 2007, CCR deployments are not supported.
This section describes the requirements for running CA ARCserve HA for Exchange Server.
To implement Replication for Exchange Server, you need to have the following configurations:
Note: For a complete list of supported operating systems and applications, see the CA ARCserve RHA Release Notes.
Note: Exchange Server 2010 does not permit you to create two databases with the same name on Master and Replica servers, even if the database is dismounted. Use a name for the Replica database that is less than 64 characters long and follows this convention:
<ReplicaName>=<MasterName>_xxxx
Where xxx = random number.
The CA ARCserve HA Engine service log on account must meet all of the following conditions:
Note: If your company's security policy requires more granular permissions than described, contact CA ARCserve RHA technical support to receive detailed instructions on the permissions required.
With CA ARCserve HA, working with clusters is nearly identical to working with stand-alone servers. Simply enter the "Exchange Virtual Server Name" as the Master or Replica server name where appropriate.
On Exchange 2007, CA ARCserve HA supports LCR deployments. No additional configurations are required.
Note: On Exchange 2007, CCR deployments are not supported.
This section describes the CA ARCserve RHA requirements for Microsoft SQL Server.
This section describes the requirements for running CA ARCserve RHA for SQL Server.
To implement Replication for SQL Server, you need to have the following configurations:
Note: For a complete list of supported operating systems and applications, see the CA ARCserve RHA Release Notes.
To use the Replication solution with the Assured Recovery option for SQL Server, you need to have the following configurations:
Also, you must stop the SQL Server service on a Replica host when replication is active.
Note: If the SQL Master Database is not replicated, you can detach the replicated databases on the Replica server without stopping the Engine service.
The CA ARCserve RHA Engine service log on account must meet all of the following conditions:
This section describes the requirements for running CA ARCserve HA for SQL Server.
To implement High Availability procedures for SQL Server, you need to have the following configurations:
Note: For a complete list of supported operating systems and applications, see the CA ARCserve RHA Release Notes.
The CA ARCserve HA Engine service log on account must satisfy all of the following conditions:
Note: If your company's security policy requires more granular permissions than described, contact technical support to receive detailed instructions. For servers in a workgroup, leave the log on user as Local System.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |