Premium Content

Access "Considerations for V2V and V2P workload migrations"

Stephen J. Bigelow, Senior Technology Editor Published: 15 Oct 2012

This article is part of the null issue of null

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 upgraded or patched to a ... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy