If you have an existing everRun MX system, 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.
Whether you reuse the existing everRun MX hardware or migrate to new hardware, the platform must meet the minimum system requirements for everRun 7.x systems, as described in Physical Machine System Requirements.
Multi-node XenServer pools are supported by everRun MX, but only two-node configurations are supported for everRun 7.x systems.
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.
Verify that the Windows guest operating system running in each of the everRun MX virtual machines is supported by the everRun 7.x software. See Compatible Guest Operating Systems.
Also, verify that each Windows 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).
Prepare the platform network and the networking environment to conform to the everRun 7.x requirements. See General Network Requirements and Configurations.
The XenServer management network becomes the everRun 7.x business network. As in everRun MX, the management console (everRun Availability Console) is accessed over this network.
Bonded network interfaces are recommend for the XenServer management network, but they are not supported for the everRun 7.x management network.
In everRun MX, each node in the XenServer pool has an IPv4 address associated with it. The same is true for an everRun 7.x system, but a system IP address is also required, and it must be a static address (not DHCP). This system IP address provides access to the everRun Availability Console; it is failed-over between everRun 7.x nodes as necessary by the everRun 7.x software.
The A-Link networks that were in use in everRun MX will continue to be the A-Link networks on the everRun 7.x system. In everRun MX, the A-Links could have networking interfaces in each node that were not on the same subnet, but this is not possible on an everRun 7.x system. For each of the two possible A-Links, the network interfaces associated with them in each node must exist in the same local network, because IPv6 link local addresses are used to identify them.
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).
The everRun private network must be identified. Only one everRun 7.x 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 7.x nodes.
On the everRun 7.x system, 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.
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 as a business network.
everRun MX supported redundant-path storage
For physical storage requirements, see Storage Requirements.
Prior to everRun MX 6.2, the quorum servers could be available only over the A-Links. As of everRun MX 6.2, the quorum servers could be available over any network in the XenServer pool. On everRun 7.x systems, the quorum servers must be available over the business network, which is configured with an IPv4 address and required for quorum.
The Preferred Quorum Server should be configured as the first Quorum Server and the Alternate Quorum Server should be configured as the second Quorum Server in the everRun Availability Console.
After the nodes in the everRun 7.x system are configured, you can install and configure the everRun 7.x software, as described in Software Installation.
Using either the P2V client migration process or the OVF import process, migrate the VMs to the everRun 7.x system. For an overview of each process, see Creating and Migrating Virtual Machines.
|
Product Support and Downloads
|
About Stratus
|
|
Product Documentation (PDF Format)
|
About Help
|