Requirements of Supported Applications and Databases › Microsoft SharePoint Server Replication and High Availability › High Availability for SharePoint Server › Prepare the Replica for Standalone Deployment › Manually Prepare the Replica for Standalone Deploymnet

Manually Prepare the Replica for Standalone Deploymnet

Before you manually prepare the Replica for standalone deployment, collect the following information and read all steps before proceeding:

• The names of the SharePoint Server configuration database and central administration database on the Master server
• The display names, ports, headers, alternate access mapping and content database names for all web applications created on the Master server
• (For SharePoint Server 2007 standalone deployment) The Shared Services Provider name on the Master

You should also view the following Microsoft TechNet documents:

• Psconfig command-line reference (SharePoint Server 2010) (cc263093)
• Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Office SharePoint Server) (for SharePoint Server 2007)
• STSADM.exe command line reference

Important! CA ARCserve RHA changes the setting of a Microsoft loopback check to ensure successful high availability scenarios on SharePoint standalone deployments. For more information, see the following Microsoft support information:

• http://support.microsoft.com/kb/887993
• http://support.microsoft.com/kb/926642

To manually prepare the Replica for standalone deployment

1. Gather the information listed.
2. Read the Microsoft TechNet documents.

   Note: The value of the following parameters should be identical to the ones on the Master: sp_cfgDB, CenAdmContDB, CentralAdminPort.

3. Open a command line session and enter the following commands.

   psconfig.exe -cmd configdb -create -server hostname\inst -database sp_cfgDB -admincontentdatabase CenAdmContDB
   psconfig.exe -cmd installfeatures
   psconfig.exe -cmd secureresources
   psconfig.exe -cmd services -install
   psconfig.exe -cmd services -provision (Valid only for SP2010)
   psconfig.exe -cmd adminvs -provision -port centralAdminPort
   

4. Create the web applications on the Replica via the Central Administrative site or STSADM tool so all display names, headers, alternate access mapping, content database names and ports are identical to those on the Master. Use the Master hostname with the port as the load balance URL when creating web applications on the Replica. You do not need to create site collections because sub-sites and site collections are stored in the Content Database, which is replicated in CA ARCserve RHA scenarios.
5. Start the services and create Share Services Provider (SharePoint Server 2007) or create the service applications on the Replica so that they are identical to those on the Master using the Central Administrative site.

   Important! Do not use the SharePoint products configuration wizard to configure the Replica before you run an HA scenario.

vCenter Server Replication and High Availability

vCenter Server Replication

This section describes the requirements for running CA ARCserve RHA for vCenter Server.

vCenter Replication Configuration

To implement Replication for vCenter Server, you need to have the following configurations:

• An instance of vCenter Server installed on the Master.
• Two servers running supported Windows Server with the same level of service packs and hot fixes installed.

  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 vCenter Server, you need to have the following configurations:

• The same version of vCenter Server installed on both Master and Replica servers.
• The vCenter Server installed with the same login credentials on Master and Replica servers.

vCenter Replication Log On Account

The CA ARCserve RHA Engine service log on account must meet all of the following conditions:

• For stand-alone servers (i.e., non-clustered), use the default of Local System.
• For cluster nodes, use a service account that is a Local Administrator on all cluster nodes.

High Availability for vCenter Server

This section describes the requirements for running CA ARCserve HA for vCenter Server.

vCenter Server HA Configuration

To implement High Availability procedures for vCenter Server, you need to have the following configurations:

• Two servers running supported Windows Server with the same level of service packs and hot fixes installed.

  Note: For a complete list of supported operating systems and applications, see the CA ARCserve RHA Release Notes.

• Both servers should have the same vCenter version, service packs and hot fixes installed.
• (In the Active Directory environment) Both Master and Replica servers should reside in the same Active Directory forest and be members of the same domain or trusted domains.
• Statically assign all IP addresses (DHCP-assigned IP addresses on the Master or Replica server are not supported).
• No participating server can be a domain controller or DNS server.
• If Database Server is installed locally or remotely to Master, configure Replica to connect to same Database Server.
• If License Server is installed locally to Master, install another instance of the License Server on the Replica and configure the Replica to connect to it.
• If License Server is installed remotely to Master, configure the Replica to connect to this instance.

vCenter HA Log On Account

The CA ARCserve HA Engine service log on account must satisfy all of the following account conditions:

• It is a member of the Domain Admins group. If the Domain Admins group is not a member of the built-in domain local group Administrators you must use an account that is.
• It is a member of the local machine Administrators Group. If the Domain Admins group is not a member, add the account manually.
• For servers in a work group, use the Local System account.

Microsoft Dynamics CRM Replication and High Availability

CA ARCserve RHA Configuration for Dynamics CRM

Microsoft Dynamics CRM is comprised of various server roles that have been combined into two server role groups:

• Application Server Role Group—This group contains the CRM core services, web front end, and help.
• Platform Server Role Group—This group contains the asynchronous processing service, discovery service, and reporting service.

Both server role groups use the SQL reporting service, which can be installed on a separate computer. You can install server role groups on the same computer, or on separate computers.

CA ARCserve RHA for Dynamics CRM can be configured in two ways:

UNIX/Linux Configuration

On AIX servers, the hostname is always set to be FQDN. When retrieving FQDN, only DNS is supported. NIS or NIS+ naming service are not supported.

If DNS redirection is used, set the lookup order to order bind, hosts in /etc/host.conf.

A bind package is required for DNS redirection:

For Oracle on UNIX/Linux systems, only the File System storage option for database instance datafiles is supported.

Full System High Availability

Full System HA can be configured as follows:

Master server

This server can be any Windows server supported by the Engine. The Master can be a physical or virtual server.

Replica server

The following virtualized environments are supported as the Replica server in Full System scenarios:

• Microsoft Hyper-V
• Citrix XenServer (Xen)
• ESX
• vCenter Server
• Amazon EC2

Note: For Hyper-V 1.0, ensure all patches are installed, particularly KB950050. Go to the Microsoft website for more information. Do not use the default installation path when creating Hyper-V virtual machines. CA ARCserve RHA cannot access the default virtual machine installation path during auto-discovery. Create a new folder such as C:\VM on Master and Replica. During Full System HA scenario creation, specify this folder on the Volume Setting screen.