ProblemVeritas (TM) Cluster Server 5.1 for Windows Application Note: Disaster Recovery for VMware VirtualCenter 2.5 templates
Deploying VMware VirtualCenter (VC) 2.5 with Storage Foundation 5.1 for Windows High Availability (HA)
SFW HA 5.1 provides clustering support for the following VirtualCenter 2.5 components, which are configured as two separate high availability solutions:
* VirtualCenter Server and Virtual Infrastructure Web Access Server
You set up these VirtualCenter components as a Veritas Cluster Server (VCS) service group for high-availability and (optionally) disaster recovery. Download the self extracting file (VCS_APP_VC_313422.EXE) attached below to a temporary folder and extract these 2 files:
VirtualCenterGrp.tf - VCS template file that has been customized for VirtualCenter 2.5
vcswin_appnote_VC.pdf - Application Note with instructions for configuring VirtualCenter for HA and DR in a VCS cluster
Follow the instructions found in the attached PDF Application Note for VC.
* VirtualCenter database
SFW HA 5.1 provides clustering support for SQL Server 2000 or 2005, with Veritas Volume Replicator (VVR) used for replication of the database to a secondary (disaster recovery) site. Instructions for configuring SQL Server 2000 or 2005 with SFW HA are provided with the SFW HA product.
Configuring a VC 2.5 service group for Storage Foundation 5.1 for Windows HA
You create a VirtualCenter service group using the VCS Java Console along with the VCS template that has been customized for VirtualCenter (VirtualCenterGrp.tf).
Note: The following steps describe how to configure the VirtualCenter service group. For the full set of tasks required to configure VirtualCenter 2.5 in a VCS cluster, see the Application Note for VC (the downloaded PDF).
To configure a VirtualCenter service group
Ensure that you have a unique IP address to assign as the virtual IP address of VirtualCenter when configuring the service group.
1 Ensure that the VirtualCenterGrp.tf template is installed on all cluster nodes in the following directory:
2 Stop the following VMware services and ensure that their startup properties are set to manual:
- VMware Infrastructure Web Access
- VMware License Server
- VMware VirtualCenter Server
These services are restarted automatically by Veritas Cluster Server when you bring the service group online.
3 Start the Cluster Manager Java Console and log on to the cluster.
4 Open the Cluster Explorer window (click anywhere in the active Cluster Monitor panel) and click Tools > Configuration Wizard.
5 On the Configuration Wizard Welcome panel, click Next.
6 Fill in the following information:
- Specify a name for the service group.
- Select the systems for the service group. Click the target systems in the Available Systems box, then click the right arrow to move the systems to Systems for Service Group.
- Leave the service group type as the default, Failover.
- Click Next.
7 Click Next again.
8 The Templates box lists the templates available on the system to which Cluster Manager is connected. The resource dependency graph of the templates, the number of resources, and the resource types are also displayed. In the Templates list, select VirtualCenterGrp. Click Next.
9 Click Next to create the service group.
10 After the service group is successfully created, click Next to edit attributes using the wizard.
11 The wizard lists the resources and their attributes. You must modify some of the attributes. To modify an attribute, do the following:
- Click the resource.
- Click the attribute to be modified.
- Click the Edit icon at the end of the table row.
- In the Edit Attribute dialog box, enter the attribute values.
- Click OK.
The following table shows the resources and corresponding attributes that you must modify:
12 Click Finish.
13 Right-click on the newly created service group and select Enable Resources.
14 Bring the service group online.
If you get a message saying "Group has not been fully probed on system" or if some of the resources are in an UNKNOWN state or display a "?", you must restart the cluster as follows. Run the following commands from the command prompt, in the sequence shown:
hastop -all -force
These commands will restart the cluster without taking any applications offline.