Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Migrating a vSAN Stretch cluster to a redeployed vCenter as vCenter couldn't be recovered / Correcting a stretch cluster not displaying correctly in vCenter after migration (77163)

Last Updated: 7/30/2023Categories: TroubleshootingTotal Views: 2982Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The vCenter was failed and had to be redeployed.

The vSAN stretch cluster wasn't turned off prior to migration.

The cluster is fully formed / data objects are healthy / the unicastagent list is complete, etc., via CLI.

The Fault Domains are correct, however, no witness/stretched cluster is configured via vCenter.

An alarm is active for “vSphere and vSAN Cluster Members Match” in relation to the witness.

One cannot select the current witness via Cluster -> Configure -> vSAN -> Fault Domains -> Stretched Cluster -> Configure (Current witness not available via wizard)

Purpose

To provide steps to bring vCenter and ESXi in sync for vSAN Stretch Cluster Status

Cause

The vSAN stretched cluster has moved to a new vCenter without first turning off stretch cluster.

The vCenter failed and had to be redeployed.

Impact / Risks

vCenter and ESXi out of sync regarding vSAN Stretch cluster status

Resolution

1) Run the following on the current Witness - Witness will leave the cluster, however, unicastagent list does not update and objects remain healthy:

# esxcli vsan cluster leave

2) Configure stretched cluster in vCenter -> Witness should now be available for selection

3) This task appears to fail, however, vCenter now views the cluster as stretched with the original witness – health checks succeed, etc.

Related Information

Additional steps for moving a stretched cluster include:

Copy all VDS settings to new cluster

Enable vSAN on new cluster

Disable stretched cluster

Move each host

Move witness

Re-enable stretched cluster

Moving a vSAN cluster from one vCenter Server to another (2151610)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
ドメイン コントローラで SMBv3 が有効になっている場合に、vCenter Server アプライアンスに対してドメイン参加操作を行うと、次のエラーが発生して失敗する：ERROR_ACCESS_DENIED (77295)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
运行状况服务错误地报告 UI 中的虚拟对象下的对象不可访问 (80995)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant