You are here: everRun User's Guide > Managing Virtual Machines > Creating and Migrating Virtual Machines > Planning to Migrate from an Avance Unit

Planning to Migrate from an Avance Unit

If you have an existing Avance unit, this topic describes some items to consider when migrating to an everRun 7.x system.

For all systems, see Creating and Migrating Virtual Machines for information about migrating your virtual machines (VMs) to the everRun 7.x system.

Note: For best results, contact your authorized Stratus service representative for assistance in evaluating and performing upgrades from an Avance unit.

Platform Requirements

Whether you reuse the existing Avance hardware or migrate to new hardware, the platform must meet the minimum system requirements for everRun systems, as described in Physical Machine System Requirements.

Planned Outage

The considerations in this help topic assume that an outage can be tolerated throughout the migration process. If you have minimum downtime requirements, contact your authorized Stratus service representative for assistance.

Guest Operating System Support

Verify that the Windows or Linux guest operating system running in each of the Avance VMs is supported by the everRun software. See Compatible Guest Operating Systems.

Also, verify that each guest operating system is supported by the migration process (as described in Migrating a Physical Machine or Virtual Machine to an everRun 7.x System) or the import process (as described in Importing an OVF File from an everRun MX System).

Network Preparation

Prepare the platform network and the networking environment to conform to the everRun system requirements. See General Network Requirements and Configurations.

Management Network Access

The same network that was used to access the Avance Management Console will be used for the everRun Availability Console.

In Avance, the nodes were available on the management network for management only through the IPv4 system address, which could be failed-over to either node in the system. The everRun software uses the same system address, but it also requires separate IPv4 addresses for each node in the same subnet as the system IP address.

Availability Link Networks

Avance had no Availability Links; therefore, these networks must be added to the hardware configuration.

Two 10-Gb networks are recommended for the A-Links.

It is not required that the A-Link connections be point-to-point (that is, they can be on a switched network).

Private Network

The same network used as the private network on the Avance unit can be used for the private network on the everRun system.

Only one everRun system can be installed and operational on the private network at any one time, so it is recommended that the private network be a point-to-point connection between the two everRun nodes.

It is typical to share one of the A-Links for the private network when at least one of the A-Link networks is connected point-to-point.

A 10-Gb network is recommended for the private network.

Business Networks

All networks that are not the private network or an A-Link network can also be business networks (that is, networks available for use by the VMs). The management network can be used simultaneously with the business network.

Storage Considerations

Avance unit storage can be used as-is in the everRun system; however, there can be only one storage group. For physical storage requirements, see Storage Requirements.

Installing everRun

After the nodes in the everRun system are configured, you can install and configure the everRun software, as described in Software Installation.

Migrating Virtual Machines

Using either the P2V client migration process or the OVF import process, migrate the VMs to the everRun system. For an overview of each process, see Creating and Migrating Virtual Machines.

of