Treat your virtualization project like a data center move
Why is it that migrating to virtual infrastructure (VI) is most often considered to be the responsibility of the server administrators? Anyone who has already done it can tell you it involves much more than servers and hardware. Even for small companies, virtualizing servers potentially (and usually) involves networking, storage, security, and infrastructure services changes. In fact, it is often as involved and complex as moving your physical servers from one data center to another.
So why is there a perception that implementing VI is only a server team responsibility? Obviously, one reason is because on the surface it’s about installing and consolidating operating systems on server hardware. Another reason is because VMware, the source for all the interest in migrating to VI to date, has done such a great job marketing their products as just server installs.


First, what is a fail over scenario? The first thing that comes to mind is a problem. One or more of your ESX hosts unexpectedly crashed. This is considered unplanned downtime. Another fail over scenario to consider is planned downtime such as rebooting after applying ESX patches. For both of these types of scenarios you want to make sure your VMs stay online.