Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vMotion over Distance support with EMC VPLEX Metro (1021215)

Last Updated: 7/13/2020Categories: InformationalTotal Views: 33279Language:
JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Purpose

This article provides information about the support of vMotion over Distance operations over VPLEX Metro using Distributed Virtual Volume. It also specifies the VMware ESXi/ESX host and VPLEX configuration details and expected behavior under different operational scenarios.

Resolution

About EMC VPLEX

EMC VPLEX is a new federation solution that can be stretched across two geographically dispersed data centers separated by synchronous distances. Starting with VPLEX Geosynchrony 5.2 and ESXi 5.5 round-trip-time for a non-uniform host access configuration is supported up to 10 milliseconds. For detailed supported configuration please refer to the latest VPLEX EMC Simple Support Matrix (ESSM) on support.emc.com. It provides simultaneous access to storage devices at 2 sites through creation of VPLEX Distributed Virtual Volume.

For more information about Distributed Virtual Volume, see Additional Information in this article.

Provided all vMotion over Distance requirements are met, with Distributed Virtual volume configured on VPLEX, a distant vMotion operation can be done from Data center 1 and Data center 2. You can vMotion over Distance a virtual machine from one data center to another to avoid disasters, migrate workloads to save power, or load balance workloads.

Notes:

See Requirements in this article for more information about the requirements for vMotion over Distance.

See Best practice documents in this article for more information about Distributed Virtual Volume on VPLEX.

This graphic demonstrates vMotion over Distance over VPLEX Distributed volume:

Requirements

To perform a vMotion over Distance operation successfully over synchronous distance, these requirements must be met:

An IP network with a minimum bandwidth of 622 Mbps is required.

The maximum latency between the two VMware vSphere servers cannot exceed 5 milliseconds (ms). Round-trip-time for a non-uniform host access configuration is now supported up to 10 milliseconds for VPLEX Geosynchrony 5.2 and ESXi 5.5 with NMP and PowerPath. For detailed supported configuration please refer to latest VPLEX EMC Simple Support Matrix (ESSM) on support.emc.com.

The source and destination ESXi/ESX servers must have a private network on the same IP subnet and broadcast domain.

The IP subnet on which the virtual machine resides must be accessible from both the source and destination ESXi/ESX servers. This requirement is very important because a virtual machine retains its IP address when it moves to the destination ESXi/ESX server to help ensure that its communication with the outside world (for example, with TCP clients) continues smoothly after the move.

The data storage location including the boot device used by the virtual machine must be active and accessible by both the source and destination ESXi/ESX servers at all times.

Access from vCenter Server and vSphere Client to both the ESXi/ESX servers must be available to accomplish the migration.

Note: See Best practice documents in this article for additional requirements for VPLEX Distributed Virtual Volume.

Supported use cases for vMotion over Distance with VPLEX Metro

This table shows the supported cases with VPLEX configuration:

Case

Support

Simultaneous access to a shared Distributed Virtual Volume from two separate ESXi/ESX clusters

Supported

vMotion between a host in ESXi/ESX cluster 1 / data center 1 to a host in ESXi/ESX cluster 2 / data center 2 leveraging the shared Distributed Virtual Volume

Supported

Tested Scenarios

When performing the vMotion over Distance over VPLEX Metro using Distributed Virtual Volume, these failure scenarios are tested and supported.

Note: Boot from SAN configuration using Distributed Virtual Volume is not supported.

On creation of a VPLEX distributed volume, a winner VPLEX cluster must be assigned. In the event of VPLEX inter-cluster communication failure, the winner VPLEX cluster continues to service I/Os destined to the VPLEX distributed volume. The loser VPLEX cluster does not service I/Os received on the distributed volume.

The VPLEX behavior and impact on ESXi/ESX servers are documented based on the fact that the VPLEX cluster at the source data center (Data center 1) is set as the winner for the VPLEX Distributed Virtual volume.

Scenario

VPLEX Behavior

Impact on ESXi/ESX hosts

Loss of ESXi/ESX server at source

No impact

Virtual machines that were running on the local ESXi/ESX server can be registered and restarted on the destination ESXi/ESX server.

Loss of ESXi/ESX server at destination

No impact

Virtual machines that were running on the remote ESXi/ESX server can be registered and restarted on the source ESXi/ESX server.

VPLEX cluster failure at source

I/O can be resumed on the VPLEX cluster at destination

Virtual machines fail on ESXi/ESX servers at both source and destination. They can be restarted on the destination ESXi/ESX server.

VPLEX cluster failure at destination

VPLEX continues to process I/O at the source. When the VPLEX cluster at destination data center is back online, any changes written during the outage are replicated to the destination's Distributed volume mirror leg.

No impact to source ESXi/ESX server. Virtual machines on destination ESXi/ESX server fail. They can be restarted on the source ESXi/ESX server.

Total Data center 1 failure (Total site failure)

I/O can be resumed on the VPLEX cluster at destination data center

Virtual machines fail at destination ESXi/ESX server. Virtual machines at source and destination ESXi/ESX servers can be restarted on the destination ESXi/ESX server.

Total Data center 2 failure (Total site failure)

VPLEX continues to process I/O at the source data center. When the VPLEX cluster at destination data center is back online, any changes written during the outage are replicated to the destination's Distributed volume mirror leg.

vMotion fails with no interruption to source ESXi/ESX. Virtual machines at destination ESXi/ESX server can be restarted on the source ESXi/ESX server with manual intervention.

No impact on source ESXi/ESX server.

Inter-site network failure (Network Partition)

VPLEX winner cluster at Data center 1 continues to function

Destination ESXi/ESX server is not able to perform I/O to VPLEX Distributed volumes. Manual intervention required to resume I/O at destination data center.

No impact on source ESXi/ESX server.

VPLEX inter-cluster communication link failure
(Network Partition)

VPLEX winner cluster at Data center 1 continues to function

Destination ESXi/ESX server is not able to perform I/O to VPLEX Distributed Virtual Volumes. Manual intervention is required to resume I/O at destination.

VPLEX director failure

No impact. I/O continues on the remaining directors.

No impact. Under some conditions, a director failure may cause a vMotion that is already in progress to halt. However, the virtual machine continues to run at source and the vMotion can be re-initiated and completed as expected.

VPLEX management server failure

No impact

No impact

Redundant front-end path failure

No impact

No impact

Redundant back-end path failure

No impact

No impact

Back-end array failure on Data center 1

No impact. VPLEX automatically starts rebuild when the failed Back-end array is back. The rebuild may affect the host I/O response. The rebuild parameters can be adjusted to minimize the rebuild effect on host I/O response time. Contact EMC for more details.

ESXi/ESX may observe slower I/O responses over Distributed Virtual Volume due to rebuilds. The rebuild parameters can be adjusted to minimize the rebuild effect on host I/O response time. Contact EMC for more details.

Back-end array failure on Data center 2

No impact. VPLEX automatically starts rebuild once the failed Back-end array is back. The rebuild may affect the host I/O response. The rebuild parameters can be adjusted to minimize the rebuild effect on host I/O response time. Contact EMC for more details.

ESXi/ESX may observe slower I/O responses over Distributed Virtual Volume due to rebuilds. The rebuild parameters can be adjusted to minimize the rebuild effect on host I/O response time. Contact EMC for more details.

Best practice documents

EMC best practice documents for vMotion over Distance using VPLEX:

USING VMWARE VSPHERE WITH EMC VPLEX - Best Practices Planning

vMotion over Distance with EMC VPLEX Metro - Best Practices

Note: The preceding links were correct as of February 13, 2015. If you find a link is broken, provide a feedback and a VMware employee will update the link.

Related Information

This table defines terms used in this article:

Term

Definition

Distributed Virtual Volume

A VPLEX virtual volume with complete, synchronized, copies of data (mirrors), exposed through 2 geographically separated VPLEX clusters. Distributed Virtual Volumes can be simultaneously accessed by servers at distant data centers thus allowing vMotion over Distance.

Winner Cluster

On creation of a VPLEX Distributed Virtual Volume, a winner VPLEX cluster must be assigned. In the event of VPLEX inter-cluster communication failure, the winner VPLEX cluster continues to service I/O destined to the VPLEX Distributed Virtual Volume. The loser VPLEX cluster does not service I/O received on the Distributed Virtual Volume. This VPLEX behavior addresses split-brain issues and data corruption in case of VPLEX inter-cluster network partition.

For more information, see Use of EMC VPLEX Metro to Enable Virtualized Workload Mobility.

Note: The preceding link was correct as of February 13, 2015. If you find the link is broken, provide a feedback and a VMware employee will update the link.

vSphere Storage DRS or vSphere Storage I/O Control support in a vSphere Metro Storage Cluster environment
EMC VPLEX Metro による長距離 vMotion のサポート

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant