vCenter Server Heartbeat (vCSHB) is a great mechanism for protecting vCenter Server and related or supporting services, such as its Microsoft SQL database or Horizon View Composer. However, with any solution of this magnitude, there will be points in the design to which careful consideration needs to be applied.
VMware, like many other large corporations, announces new products at their large conferences. So far at Partner Exchange, I've seen VMware announce new competencies for its partners, new products to run the cloud, new certifications for technology professionals, and new email collaboration suites. The questions that come to mind are how all of these will impact the consumer, why it matters to the IT manager and how it will affect normal business user. In an effort to sum up the changes and the impacts, I will break each of these down along with why you should care.
So the last couple of days have been fairly interesting here at VMworld. As expected, the much anticipated announcement of vCloud Director (formerly Project Redwood or the vCloud Service Director) was made at this morning's general session. From the sessions that we've attended, a couple of things are very clear:
In Part 1 of Exchange 2010 on vSphere 4, Best Practices, we looked into the sizing requirements relative to our Client Access, Hub Transport, and Mailbox server roles. For this entry, we'll take a look at our vSphere 4 environment and apply VMware and Microsoft support Best Practices to our ESX cluster. Keep in mind that these configurations have been tailored in order to apply to all use cases inside of a VMware environment so whether your goal is to support 50 users on a single Exchange 2010 Virtual Machine, or 50,000 users across several ESX clusters, the same measures should be applied to your VMs and host servers.
Imagine if you would, a world where virtualization is the defining trend in x86 computing. Where new advances in hardware capacity and hypervisor scalability see 20+ VM-to-physical server environments everywhere. Where the days of having to co-mingle your Microsoft application services on a single machine have been washed away by the ability to spin up new low cost systems at whim. Where you can afford to follow best practices and keep things like Domain Controllers and DHCP services on separate machines. Oh wait, we're already at Shangri-La's doorstep!