Access your Pro+ Content below.
Considerations for V2V and V2P workload migrations
This article is part of the Virtual Data Center issue of February 2011, Vol. 31
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 email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
Although there are few situations in which V2V or V2P migrations are necessary, administrators needing to make these moves must be prepared to handle unique challenges.
With physical security, you don't have to consider breaches of virtual machines, utilities or virtual disk files. But virtualization creates new security risks and vulnerabilities.
Keep your servers up to snuff by ensuring that resources have been optimally allocated. Understanding resource supply and demand is the key to a strong capacity management process.