Here’s a great resource to keep in mind as you’re planning your vSphere 4.0 deployment: “Reference Implementation: Clustering vCenter Server 4.0 Using Microsoft Cluster Services”. The tech note provides detailed steps for setting up a fresh installation of vCenter Server 4.0 in a MSCS environment, as well as upgrading an existing vCenter cluster setup on MSCS to vCenter Server 4.0. While this particular document shows the setup of a reference implementation using VMs for the cluster nodes, other variations would certainly also be valid.
For those of you who are already familiar with the procedure used to set up vCenter Server 2.5 with MSCS, I wanted to highlight how the procedure has changed with vCenter Server 4.0. With the release of vCenter Server 4.0, one of the main differences is that vCenter Server roles are now stored in Microsoft Active Directory Application Mode (ADAM) instances. During the MSCS setup process, you can simply use ADAM replication to replicate the roles from node 1 to node 2.
Of course, using MSCS is just one of many ways to protect your vCenter management platform. If you’re looking for something that’s easier to install and configure, vCenter Server Heartbeat has no hardware configuration dependencies and automatically detects standard VMware vCenter Server components upon installation for instant monitoring and protection. If you’re going to VMworld, be sure to add the 2-hour instructor-led “Lab 6 VMware vCenter Server Heartbeat” and “VM2674 VMware vCenter Server Heartbeat Best Practices” to your schedule. The breakout session will highlight a number of customer examples focused on VMware vCenter Server Heartbeat deployments, and give you insight into how you can protect other important solutions like Site Recovery Manager or View.
- From Catherine Fan in VMware Product Management.