Access your Pro+ Content below.
To P2V or Not to P2V? The rules of the road for virtual migration
This article is part of the Virtual Data Center issue of December 2008, Vol. 6
In the move from physical to virtual infrastructure, organizations face numerous challenges: getting appropriate decisional support, planning and implementing the right hardware components, even choosing the right hypervisor. But one of the most complicated processes that organizations encounter is determining how to move current physical workloads into virtual machines (VMs). Virtualization providers often tout their physical-to-virtual (P2V) migration tools as the cure-all for this complex process. But when your IT infrastructure is at the core of business operations, you want to ensure that your approach provides the best results. After all, when you put all your eggs in one basket, the basket better be as tough and resilient as you can make it. So what does a physical-to-virtual migration entail, and why can it be problematic? In simple terms, the virtual hardware presented by a virtual machine is always different from the physical hardware on the original server. A conversion process is thus required to accommodate these ...
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
Given the low risk, companies often embark on virtualization projects by virtualizing a test and development environment. But even virtualized lab environments can pose problems.
Physical-to-virtual migration is sometimes touted as a turnkey event. But without understanding your server environment, P2V tasks are hardly seamless.
Columns in this issue
This issue demystifies some of the magic behind virtualization.