Migrating a Physical Machine or Virtual Machine to an everRun 7.x System

1. Download the P2V client ISO file from the Downloads page at http://www.stratus.com/go/support/everrun.

   1. On the Downloads page, click everRun (if it is not already displayed) and then select the appropriate version.
   2. Scroll down to Drivers and Tools and then continue scrolling to everRun P2V Client for Virtual or Physical Machine Migration.
   3. Select the P2V Client (virt-p2v) file.

   If you want to verify the integrity of the ISO image, also download the associated fciv (Windows) or md5sum (Linux) checksum file and execute similar commands to those described in Obtaining everRun Software.

2. Burn the P2V client ISO file to a CD-ROM that you will use to boot the physical machine.
   
3. Insert the P2V client CD into the CD/DVD drive of the source PM.
4. Shut down the PM in preparation to boot the P2V client.

1. Download the P2V client ISO file from the Drivers and Tools section of the Downloads page at http://www.stratus.com/go/support/everrun. Ensure that you download the version of the P2V client that matches the version of the everRun system to which you are migrating the VM.

   If you want to verify the integrity of the ISO image, also download the associated fciv (Windows) or md5sum (Linux) checksum file and execute similar commands to those described in Obtaining everRun Software.

2. Insert or connect the P2V client ISO file to the source VM and set the virtual CD drive as the boot device in the associated hypervisor.
3. Shut down the VM in preparation to boot the P2V client.

1. Power on the source PM or VM to boot the P2V client. After a minute or so, the virt-p2v window is displayed.

2. If prompted, configure the network settings to use for the migration process; otherwise, skip to step 3. To configure the network settings:

   1. Select an active network device, if more than one is present.

   2. To specify static network settings, optionally clear the Automatic configuration check box and enter your IP Address, Gateway, and DNS Servers settings.

      Otherwise, keep the default settings to use DHCP.

   3. Click Use these network settings.
3. Enter the connection settings for the conversion server (the everRun system). Enter the Hostname or IP address of the system and the Password for the root account. (You must use the root account of the everRun host operating system, as described in Accessing the Host Operating System.)
4. Click Connect. The Target properties page is displayed.
5. Select EverRun-FT as the Destination Profile. (For information about these levels of protection, see Creating a New Virtual Machine and Modes of Operation.)
6. Enter the Name for the target VM that will be displayed in the everRun Availability Console. (The name must be different from any existing VMs on the everRun system.)
7. The Number of CPUs and Memory(MB) values are automatically detected and completed, but optionally modify them if you want the VM on the everRun system to have more CPUs or memory than the source PM or VM.

8. Select which Fixed Storage devices to include in the migration by activating the check box next to each device.

   You must select at least one volume, including the boot volume. (Because the P2V client is a Linux-based utility, all devices are listed by Linux device names, where sda or vda represents the boot volume.)

9. The P2V client automatically manages Removable Media and Network Interfaces for the migration. Only one CD/DVD drive and one network interface is transferred to the new VM on the everRun system, regardless of your selections. You cannot change the CD/DVD configuration in the new VM, but you can provision additional network interfaces to the VM as needed after the migration.
10. When you are ready to migrate the PM or VM to the everRun system, click Convert. (If you need to cancel the migration for any reason, see Troubleshooting below.)
11. When the migration is complete, the P2V client displays a success message. If applicable, you can eject the CD or virtual CD and click Power Off to shut down the source PM or VM.

1. Open the Virtual Machines page (see The Virtual Machines Page) in the everRun Availability Console.

2. Select the new VM in the top pane and click Config to open the Reprovision Virtual Machine wizard, as described in Reprovisioning Virtual Machine Resources. Use the wizard to configure the desired vCPUs, memory, storage, and network settings for the VM:

   • If your source PM or VM had more than one network interface, configure the additional network interfaces that were not included in the migration process.
   • If you will continue running the source PM or VM, ensure that the MAC address for each network interface in the new VM is different from the source PM or VM.

   Click Finish on the last wizard page to implement the changes.

3. Click Start to boot the new VM.
4. Click Console to open the console of the VM and log on to the guest operating system. (For information about using the console, see Opening a Virtual Machine Console Session.)

5. For Windows-based VMs only, install the required VirtIO drivers (already installed on Linux-based systems).

   Note: You must install two or more drivers, each of which requires the system to restart. When prompted, you can wait until the last driver is installed to restart the guest operating system.

   In most cases, Windows either prompts you to install the drivers or automatically installs the drivers. After restarting the system to apply the new drivers, verify that the drivers are present or install them if necessary, as follows:

   1. Open Device Manager in the guest operating system.

   2. Expand Network adapters and verify that the Red Hat VirtIO Ethernet Adapter is present. There may be more than one adapter present depending on the number of network interfaces in your VM.

      If the Red Hat VirtIO Ethernet Adapter is not present, expand Other devices and right-click the unknown Ethernet Controller device. Select Update Driver Software and follow the wizard to automatically search for and install the Red Hat VirtIO Ethernet Adapter driver. Repeat the driver update for each additional Ethernet Controller device.

   3. Expand Storage controllers and verify that the Red Hat VirtIO SCSI controller is present. There may be more than one controller present depending on the number of volumes in your VM.

      If the Red Hat VirtIO SCSI controller is not present, right-click the unknown SCSI controller device. Select Update Driver Software and follow the wizard to automatically search for and install the Red Hat VirtIO SCSI controller driver. Repeat the driver update for each additional SCSI controller device.

   4. If applicable, restart the guest operating system to load the updated drivers.
   Note: On the Virtual Machines page and Volumes page of the everRun Availability Console, the State column may not accurately reflect the state of the VM or volume until the VirtIO drivers are properly installed.

6. Disable any guest operating system services that are unnecessary for operation on the everRun system:

   • If you migrated from a PM source, disable any services that interact directly with hardware. Examples include:
     • Dell OpenManage (OMSA)
     • HP Insight Manager
     • Diskeeper
   • If you migrated from a VM source, disable any services associated with other hypervisors. Examples include:
     • VMware Tools
     • Hyper-V Tools
     • Citrix Tools for Virtual Machines

   After disabling these services, restart the guest operating system to implement your changes.

7. If necessary, update the network configuration settings in the guest operating system and restart it to enable the settings.
8. Verify that you have configured your guest operating system with the additional Windows- or Linux-based system settings described in:
• Configuring Windows-based Virtual Machines
• Configuring Linux-based Virtual Machines

After you verify that the new VM is functioning properly, the migration process is complete; however, the everRun system may continue to synchronize data between PMs to enable High Availability (HA) or Fault Tolerant (FT) operation.

If necessary, use the following information to resolve problems with the migration process.

To cancel the migration process

Power down the source PM or VM running the P2V client.

To clean up after a canceled or failed migration

Open the everRun Availability Console and remove any migrated volumes associated with the source PM or VM. If you want to restart the migration process, reboot the P2V client on the source PM or VM.

To recover from a failed migration

If the migration process fails, an error message is displayed in the P2V client on the source PM or VM. Another message may be displayed on the everRun system. Use these messages to determine the problem.

If the migration continues to fail, and the option is available, enable server-side debugging. After the migration, generate a diagnostic file to send to your authorized Stratus service representative, as described in Creating a Diagnostic File. The diagnostic file includes any server-side debugging messages from the migration process.

To recover when the new VM's console hangs on the everRun system

For Ubuntu-based VMs, the VM console hangs in everRun Availability Console if you do not properly set the gfxmode parameter before the migration process (as described in Notes). If the VM console hangs, keep restarting the VM until the console opens properly in everRun Availability Console and then modify the gfxmode parameter to prevent subsequent issues.

For additional VM console troubleshooting, see Opening a Virtual Machine Console Session.

To recover missing data volumes in the VM on the everRun system

If your data volumes do not appear in the VM on the everRun system after the import, you may need to manually restore the volumes, as follows:

• Shut down the VM, run the Reprovision Virtual Machine wizard, and verify that you have included the volumes on the Volumes page.
• For Windows-based VMs, use Disk Management to bring data volumes online.
• For Linux-based VMs, edit the /etc/fstab file to reflect the new device names for the storage devices, from Avance (/dev/xvda through /dev/xvdh) to everRun (/dev/vda through /dev/vdh). Device names also may have shifted, for example, if volumes were not included in the import.

To recover missing network devices in the VM on the everRun system

If your network devices do not appear in the VM on the everRun system after the import , you may need to manually restore them, as follows:

• Shut down the VM, run the Reprovision Virtual Machine wizard, and verify that you have included the networks on the Networks page.
• For Linux-based VMs, reconfigure the network startup script to reflect the new device names for the network interfaces.