Misplaced Pages

Physical-to-Virtual

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Physical-to-Virtual" – news · newspapers · books · scholar · JSTOR (September 2014) (Learn how and when to remove this message)

In computing. Physical-to-Virtual ("P2V" or "p-to-v") involves the process of decoupling and migrating a physical server's operating system (OS), applications, and data from that physical server to a virtual-machine guest hosted on a virtualized platform.

Methods of P2V migration

Manual P2V

User manually creates a virtual machine in a virtual host environment and copies all the files from OS, applications and data from the source machine.

Semi-automated P2V

Performing a P2V migration using a tool that assists the user in moving the servers from physical state to virtual machine.

Fully automated P2V

Performing a P2V migration using a tool that migrates the server over the network without any assistance from the user.

See also

External links

References

  1. Muller, Al; Wilson, Seburn (2005). "Chapter 6: Physical-to-Virtual Migrations". Configuring VMware ESX Server 2.5. Syngress. p. 139. ISBN 9780080488578. Retrieved 2013-07-24. The concept of this p-to-v process, or any p-to-v process, is really quite simple: you are making a copy of your hard drive and piping it eventually into a virtual server.


Stub icon

This computing article is a stub. You can help Misplaced Pages by expanding it.

Categories:
Physical-to-Virtual Add topic