Converting an everRun MX System to an everRun 7.x System

1. Plan for converting your everRun MX system by reviewing the information:

   • Planning to Migrate from an everRun MX System

     Describes some items to consider when migrating or converting from an everRun MX system to an everRun 7.x system.

   • Software Installation

     Summarizes the steps for installing the everRun 7.x software.

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

     Describes how to use the P2V client to migrate a VM from one system to another. Also describes some steps you may need to complete in your guest operating systems before migrating the VMs to ensure that the VMs will function properly on the everRun 7.x system.

2. Back up your everRun MX system and VMs.

3. Download the everRun 7.x 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 select the appropriate version.
   2. Scroll down to Product Downloads, and under Install, click the link to the appropriate ISO image (everRun_install-7.x.x.x-xxx.iso).
   3. Save the ISO image

4. Download the P2V client ISO file from the same Downloads page.

   1. On the Downloads page, click everRun (if it is not already displayed) and then select the appropriate version.
   2. Scroll down to the Drivers and Tools bar and then continue scrolling to everRun P2V Client for Virtual or Physical Machine Migration.
   3. Select the P2V Client (virt-p2v) file.
   4. Save the file.
5. Burn the everRun 7.x ISO file to a physical DVD that you will use to install the everRun 7.x software on each PM in your system.
6. Burn the P2V client ISO file to a physical CD that you will boot in each everRun MX VM to transfer the VMs to the everRun 7.x system.

7. Contact your network administrator to request at least one static IP address to use as the system-wide IP address for your converted everRun 7.x system. Request an additional static IP address for each of the two nodes if you do not have a DHCP server to automatically assign these addresses or if you prefer to use only static addresses.

   Note: You must maintain unique system IP addresses for the everRun MX system and the everRun 7.x system while both systems are online; however, if you want to re-use the original everRun MX system IP address for the everRun 7.x system, you can change the network settings of the everRun 7.x system after the conversion is complete.

Starting with both nodes running the everRun MX software, do the following:

1. Log on to the everRun Availability Center with the hostname or IP address of your everRun MX master node at:

   http://everRunMX-address:8080
2. On left-hand navigation panel, click the Hosts tab.
3. Right-click the master server and select Shutdown.

4. Allow the server to evacuate the VMs and properly shut down. You can watch its progress on the everRun Log tab.

   When the server is shut down, a message describes that you have lost connection to the everRun Availability Center. This is expected.

5. Open Citrix XenCenter and connect to remaining server of the everRun MX system, which is now the master server.
6. Make sure the VMs are still running on the remaining server before continuing.

Starting one node shut down and the second node running the everRun MX software, do the following:

1. Insert the everRun 7.x DVD into the physical DVD drive of the offline node and boot the node to start the installation program.

2. Follow the instructions in Installing Software on the First PM to install the everRun 7.x software on the first node. Power on the node, update the necessary settings in the firmware (BIOS) setup utility, and boot the node from the everRun 7.x DVD to run the installation program.

   When configuring the management network, select a DHCP-assigned address for now and record the IP address as described in Recording the Management IP Address. (You can optionally specify a static IP address for each node later, after converting the second node.)

   Caution: Do not convert the remaining node of the everRun MX system at this point; otherwise, all everRun MX data and VMs will be lost.
3. When you finish installing the everRun 7.x software on the first node, verify that you can connect to the everRun Availability Console at the IP address of the newly-installed node.

4. Log on to the everRun Availability Console of the newly-installed node as described in Logging on to the everRun Availability Console for the First Time.

   When prompted for the initial configuration settings, type the static IP address you obtained from your network administrator as the System IP address. Also, if you want to fully enable the features of your everRun 7.x system for testing, upload and activate your product license on the LICENSE INFORMATION page.

   Notes:  

   • When specifying the System IP address, type the system-wide IP address of the everRun system, and not the node0 or node1 address.
   • If you want to verify that your VMs work on the first node before you install the everRun 7.x software on the remaining node, activate your product license now. You can use the P2V client to migrate your VMs to the everRun 7.x system without a product license, but you cannot start and test your VMs on the everRun 7.x system unless you activate a valid license.

With the first node running the everRun 7.x software and the second node running the everRun MX software, do the following:

1. If applicable, prepare your VMs for migration as described in Migrating a Physical Machine or Virtual Machine to an everRun 7.x System. (If you need to migrate a Windows Server 2003 VM, see the specific steps in Migrating a Windows Server 2003 VM to an everRun 7.x System.)

   In some cases, you need to perform steps in the guest operating system before migrating a VM to ensure that the VM will function properly on the everRun 7.x system.

2. Log on to the everRun Availability Center on the remaining node of the everRun MX system at:

   http://everRunMX-system:8080
3. In the left-hand navigation panel, click Virtual Machines.
4. Right-click a VM that you want to migrate and click Unprotect.
5. When the VM is unprotected and automatically shut down, go back to XenCenter.
6. In the left-hand navigation panel of XenCenter, locate and expand the entry for the everRun MX system. Click the VM, and click Start.
7. After the VM starts, click the Console tab and click Click here to create a DVD Drive. Shut down the VM to save the change.

8. Insert the P2V client CD into the DVD drive of the remaining everRun MX node.

9. In the Console tab, next to DVD drive n, select the physical P2V client CD in the drop down menu. Click Start to begin booting the VM from the P2V client CD.
10. Migrate the VM by following the steps in Migrating a Physical Machine or Virtual Machine to an everRun 7.x System.

11. After the migration completes, power off the VM and close the VM console window.

12. In the everRun Availability Console connected to the everRun 7.x node, verify that the VM appears on the Virtual Machines page.

13. Start the migrated VM and verify that it is functioning properly. Follow the instructions in Migrating a Physical Machine or Virtual Machine to an everRun 7.x System to complete any migration steps in the VM. For example, you may need to install drivers or disable certain services.

    Caution: The original VM on the everRun MX system must remain shut down when you use the VM on the everRun 7.x system; otherwise, the VMs will have network and software licensing conflicts.
    Note: You can start a VM on the everRun 7.x system only if you have activated your product license. Upload and activate your license as described in Managing the everRun Product License.

14. If necessary, configure and manage your VM as described in Managing Virtual Machines. For guest-specific settings, see:

    • Configuring Windows-based Virtual Machines
    • Configuring Linux-based Virtual Machines
15. Follow steps 1-14 to migrate additional VMs.
16. Verify that all of your VMs are functioning properly, and that you have recorded any additional settings that you need from the remaining everRun MX server, which you will overwrite in the next procedure.

1. Shut down the remaining node of the everRun MX system.

2. Follow the instructions in Installing Software on the Second PM to install the everRun 7.x software on the remaining node. Power on the node, update the necessary settings in the firmware (BIOS) setup utility, and boot the node from the everRun 7.x DVD to run the installation program.

   When configuring the management network, select a DHCP-assigned address for now. (You can specify a static IP address after the software installation.)

3. When the installation finishes, connect to the everRun Availability Console at the system IP address of the everRun 7.x system.

4. Verify that both PMs reach the running state and that the PMs finish synchronizing. The initial synchronization may take minutes or hours depending on your configuration, including the amount of storage and the number of VMs.

5. Optionally, update the network settings for the everRun 7.x system:

   • If you want to reuse the static IP address of the everRun MX system as the system IP address of the everRun 7.x system, open the Preferences page and click IP Configuration. On the System IP tab, enter the static IP settings that were used by the everRun MX system and click Save.
   • If you want to specify a static IP address for each node, click each Noden IP tab, enter the new settings, and click Save.

   If necessary, the everRun Availability Console reloads to reflect the new addresses.

6. Configure the everRun 7.x settings summarized in Post-Installation Tasks.

If necessary, use the following information to resolve problems with the export or import process.

To resolve network connectivity problems with the everRun 7.x system

If you have trouble connecting to the everRun Availability Console after installing the first node, you may have used the same IP address for node0 and for the system IP address of the everRun 7.x system To correct the problem, reinstall the everRun 7.x software on node0 and ensure that the IP addresses you type for node0 and the system IP address are unique.