In Part 1
of this series, I delved into the installation of the
. In this, Part 2, I deal with data migration from a standalone system (the system being migrated into the virtual environment) to a newly created DomU (a new virtual machine which is going to replace the stand-alone system).
When it comes to data migration, it can be said that just like any other system admin’s tasks, only your imagination can pose limitations on how you may approach the assignment. This essentially means that your creativity in tackling this task depends on the following:
- Your understanding of the system being migrated and the environment around it.
- The tools that you have on hand.
Depending on the understanding I have, I pondered for a while on how to approach the task. Then, I concluded that I could either migrate the whole stand-alone system (migrate the whole system) as it is; or simply migrate fundamental roles’ related data (migrate only necessary services’ related data).
Several years ago I was hired as a Linux System Administrator to consolidate several network services into a Xen virtual environment. Even though Xen was already the incorporated virtual machine manager (VMM) distributed with Redhat Enterprise Linux 5 (rhel5), I could not find any quick guide to help me tackle the task. To this day, there are very few clear how-tos when it comes to virtualization using Xen. Therefore, I am writing this quick guide hoping that it’s going to be a valuable reference for anyone who opts to use Xen rather than any other VMM out there.
In case you are not familiar with Xen, it was a fruit of a research project conducted at the University of Cambridge back in the early 2000s. The first version came out in 2003. In 2007 Citrix Systems bought its source code and later the same year made the source public through Xen Project.
When one has decided to consolidate servers or services into a Xen’s virtual environment, one is faced with a couple of choices to make: 1) Select Virtual Machine Type; and 2) Select Migration Method.