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
Prerequisites
Before getting started with Just In Time Availability, ensure that the following prerequisites are met:
The Just In Time (JIT) solution feature cannot co-exist with VMware HA, VMware FT, and VMware DRS. This pre-requisite is applicable for
only.VIOM 7.2 version must be installed and configured using fully qualified domain name (FQDN) or IP.
Make sure that you have the admin privileges for vCenter.
VMware Tools must be installed and running on the guest virtual machine.
VIOM Control Host add-on must be installed on VIOM server or machine.
The virtual machines must be added in VIOM. The virtual machines, vSphere ESX servers, and VIOM must have the same Network Time Protocol (NTP) server configured.
Make sure to specify VIOM Central Server FQDN or IP in the SNMP Settings of the vCenter Server.
vCenter Server and VIOM must be configured using the same FQDN or IP address. Make sure that if FQDN is used to configure vCenter in VIOM Server that is used during the configuration.
If raw disk mapping (RDM) disks are added to the virtual machine, then make sure that the virtual machine is in the physical compatibility mode. Veritas AppProtect does not support the virtual compatibility mode for RDM disks.
For Microsoft Windows operating system, make sure that you have the Microsoft Windows product license key. The key is required to run the Sysprep utility, which enables customization of the Windows operating system for a clone operation.
For RHEL7 and SUSE12 operating system, install the deployPkg plug-in file on the virtual machine.
For more information on installing the plug-in, see
Make sure that the InfoScale Availability service group is configured with one of the storage agents such as Mount, DiskGroup, LVMVolumeGroup, VMNSDg (for Windows), or DiskRes (for Windows), for the data disks. This configuration enables Veritas AppProtect to discover data disks for the applications. Also, ensure that the service group is online to determine data disk mapping.
Virtual machines which have snapshots associated with them are not supported.
Virtual machines with SCSI Bus Sharing are not supported.
Make sure that the SNMP Traps are configured for the following from vCenter server to VIOM:
Registered virtual machine
Reconfigured virtual machine
Virtual machine which is getting cloned
Make sure that the boot disk of VM's (vmdk) does not have spaces.
For HA console add on upgrade from VIOM 7.1 to VIOM 7.2, refer Veritas InfoScale Operations Manager 7.2 Add-ons User's Guide for more details.
Make sure to set the vSphere DRS Automation Level to manual, if you want to configure Restart VM on target ESX or Restore VM on target ESX policies for your plan.
Ensure to update or edit the plan, when a virtual machine is migrated or if there are any modifications made to the settings of the virtual machines which are configured for that plan.
Ensure to increase the tolerance limit of DiskRes resource to two, if you want to create a plan for unplanned recovery with Restore VM on target ESX as the unplanned recovery policy.
Note:
This prerequisite is applicable for Windows operating system.