Storage Foundation and High Availability Solutions 7.4.1 HA and DR Solutions Guide for Microsoft SharePoint 2010 - Windows
- Introducing Storage Foundation and High Availability Solutions for SharePoint 2010
- About high availability support for SharePoint Server
- Introducing the VCS agent for SharePoint Server 2010
- Configuration workflows for SharePoint Server 2010
- Reviewing the HA configuration
- Notes and recommendations for cluster and application configuration
- Configuring the cluster using the Cluster Configuration Wizard
- Using the Solutions Configuration Center
- Installing and configuring SharePoint Server 2010 for high availability
- Configuring disaster recovery for SharePoint Server 2010
- Introducing the VCS agent for SharePoint Search Service Application
- About the VCS agent for SharePoint Search service application
- Configuring the SharePoint Search Service Application service group
- Verifying the application service group
- Administering the SharePoint Search Service Application service group
- Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
Requirements
Veritas provides the following DNS update script files in the %VCS_HOME%\bin\SQLServer
directory:
The files consist of the following:
dnsupdate-online.pl
dnsupdate-offline.pl
dnsupdate-monitor.pl
dnsupdate-settings.txt
The scripts log to the engine log. The name of the first log file is engine_A.txt
.
Note:
The scripts require the Dnscmd.exe
command-line tool, which is installed as part of the DNS server tools on Windows Server systems.
Customize the settings file for your environment. You need two copies of the settings file, one for the primary site settings and another for the secondary site settings.
See Customizing the DNS update settings for the web servers.
Place the script files and the appropriately customized settings file for the site at a location where they are available from the cluster nodes. Since you specify the file names and locations as part of the service group process resource, you can choose the file names and locations. To avoid editing the service group again on the secondary site, you must use the same names and locations on both sites.
Warning:
Do not place the settings file on a replicated volume. Otherwise, the settings file of the active site overwrites settings file of the passive site during replication.