This Content Component encountered an error

PRO+ Premium Content/Virtual Data Center

Thank you for joining!
Access your Pro+ Content below.
February 2011, Vol. 31

Considerations for V2V and V2P workload migrations

This tip is the second in a two-part series on virtual migrations. Read  part one about management tips for planning P2V migrations. Once a virtualization layer is in place, pre-existing workloads must make the transition from physical servers to virtual servers. Virtual workloads may also need to make a transition from one virtualization platform to another as platforms are upgraded or swapped out over time. And although the assumption might be that virtual machines (VMs) never go back, there are cases when a workload may make the transition back to a physical server. This tip takes a closer look at the considerations and caveats in virtual-to-virtual (V2V) and virtual-to-physical (V2P) workload transitions, as well as important factors to note for disaster recovery. From virtual to virtual Although migrating workloads from physical to virtual is quite common, the move from virtual to virtual is a bit more complicated. There are generally only three situations that require V2V migration: the current virtualization platform is ...

Access this PRO+ Content for Free!

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

Features in this issue