[PDF] Parallels Server 5 Bare Metal

Managing Virtual Machines and Containers
1 Once you start the migration, Parallels Server Bare Metal checks whether the destination server
meets all migration requirements and the virtual machine or Container can be migrated to this
server.
2 All virtual memory and disks of the virtual machine or Container are migrated to the destination
server.
3 The virtual machine or Container on the source server is suspended.
4 The changed memory pages and virtual disk blocks, if any, are migrated to the destination
server.
5 The virtual machine or Container is resumed on the destination server.
The virtual machine or Container continues running during steps 1 and 2 and is not available to the
end user during steps 3-5. But since the amount of memory pages and virtual disk blocks changed
during step 2 is small, the service outage time for the end user is almost imperceptible.
Migrating virtual machines and Containers
Depending on whether you are migrating a virtual machine or Container, the command-line options
you pass to the pmigrate slightly differ. For example, you can migrate Container 101 from the
local server to the destination server destserver.com by executing the following command on
the local server:
# pmigrate c 101 c --online destserver.com
Enter password:
Connection to destination server (192.168.1.57) is successfully established
...
Successfully completed
At the same time, to migrate the MyVM virtual machine to the same destination server
destserver.com, you can run this command on the local server:
# pmigrate v MyVM v destserver.com
Migrate the VM MyVM to test.com
...
The VM has been successfully migrated.
As you can see, to migrate a virtual machine, you skip the --online option and use the v option
to specify that you are migrating a virtual machine.
Notes:
1. For more information on options you can use with the pmigrate utility, see the Parallels Server 5 Bare
Metal Command-Line Reference Guide.
2. After migration, the moved virtual machine may not be accessible over the network for several minutes
due to latencies in the network equipment reconfiguration (for example, when switches need to update
their dynamic VLAN membership tables).
61