DH2i’s DxConsole can reduce license cost and complexity and enhance availability in Microsoft SQL Server implementations—on-premises, virtualized, and non-virtualized—and allow you to fail over to the cloud.
Amazon’s recent outages remind us that deploying in the cloud doesn’t automatically guarantee high availability. Where you deploy, and how you deploy turns out to really matter.
There used to be a FedEx commercial that had a saying “when it just has to be there overnight”. What if we did a play on words and changed the saying to work with Fault-Tolerance and or High Availability. The saying would be something like “when it just has to remain running overnight”.
With the release of vSphere 4.1 there have been some great enhancements that have been added with this release. In one of my earlier post I took a look at the vSphere 4.1 release of ESXi. This post I am going to take a look at vSphere 4.1 availability options and enhancements. So what has changed with this release? A maximum of 320 virtual machines per cluster has been firmly set. In vSphere 4.0 there were different VM/Host limitations for DRS as well as different rules for VMware HA. VMware has also raised the number of virtual machines that can be run in a single cluster from 1280 in 4.0 to 3000 in the vSphere 4.1 release. How do these improvements affect your upgrade planning?
This technique operates completely transparent to the vSphere environment, as only a single LUN is presented to the two hosts. So a single vMotion and a “logical” storage vMotion (actually hyper-speed synchronous dual write) are combined into a single vMotion which only takes a few minutes or seconds to execute.