Migrating a Windows Server 2003 VM to an everRun 7.x System

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.

   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.

2. If you want to verify the integrity of the ISO image, also download the associated fciv checksum file, and then download the Microsoft File Checksum Integrity Verifier (FCIV) executable file from the Microsoft Support Website. Save both files to the directory that contains the downloaded ISO file.

   Open a command prompt. From the directory containing the ISO, executable, and verification files, type a command similar to the following to verify the ISO image:

   fciv -v -xml virt-p2v-n.n.n-n.nnnnnnnn.n.el6.centos.xml

   If the command succeeds (that is, it returns the message All files verified successfully), go to the next step. If the command fails, repeat the download.

3. In the Avance Management Console, use the P2V client ISO file to create a VCD that you will boot in the Windows Server 2003 VM to transfer it to the everRunsystem.
4. On the Virtual Machines page, select the Windows Server 2003 VM and click Shutdown.
5. When the Windows Server 2003 VM is stopped, click Boot from CD.
6. In the Boot from a CD dialog box, select the P2V client VCD and click Boot.

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.
2. Burn the P2V client ISO file to a physical CD that you will boot in the Windows Server 2003 VM to transfer it to the everRun 7.2 or later system.
3. Perform steps 1 through 9 in the To migrate VMs from the everRun MX node to the everRun 7.x node section of Converting an everRun MX System to an everRun 7.x System to shut down the Windows Server 2003 VM and boot it from the P2V client CD.

1. In the virt-p2v window, fill in the destination everRun system's host name (or host IP address) and password. Click Test connection and Next.

2. In the next virt-p2v window, click Start conversion.

   You can monitor the progress of the migration in the virt-p2v window and on the Volumes page of the destination everRun system's everRun Availability Console as volumes associated with the new VM begin to appear.

3. When the migration is complete, the virt-p2v window displays a success message. Click Power Off to shut down the source VM.
4. In the destination everRun system's everRun Availability Console, click Virtual Machines.
5. Select the newly created VM and click Start.
6. Log on to the Windows Server 2003 guest operating system.
7. A service control manager warning about a driver failing during system startup appears. Click OK.
8. In the Found New Hardware wizard, select No, not this time and click Next.
9. Select Install the software automatically. Click Next.
10. A warning about the RedHat VirtIO Ethernet Adapter not passing Windows Logo testing appears. Click Continue Anyway.
11. When the Found New Hardware wizard completes, click Finish.
12. A warning about the RedHat VirtIO SCSI Adapter not passing Windows Logo testing appears. Click Continue Anyway.
13. The Found New Hardware wizard displays a Cannot Install this Hardware message. Select Don't prompt me again to install this software and click Finish.
14. At the prompt to restart the computer, click Yes.
15. A service control manager warning about a driver failing during system startup appears again. Click OK.
16. If necessary, update the network configuration settings in the guest operating system and restart it to enable the settings.

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.