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

Configuring MSCS for high availability (67076)

Last Updated: 2/20/2019Categories: Best PracticesTotal Views: 2267Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

The article details steps around setting up a Microsoft Cluster Service (MSCS) as an availability solution for vCenter Server.

MSCS as an availability solution for vCenter Server is provided only for management nodes of vCenter Server (M node). For infrastructure nodes, customers must deploy multiple N nodes for high availability. You cannot have M and N nodes on the same VM for MSCS protection.

Solution

To setup a Microsoft Cluster Service (MSCS) as an availability solution for vCenter Server:

Power on the VM.

Format the two RDM disks, assign them drive letters, and convert them to MBR.

Using Windows > Server Manager > Features, install .net.

Install vCenter Server on one of the RDM disks and set the start option to manual.

Power off the VM.

Detach the RDM disks.

Detaching the RDM disks is not a permanent deletion. Do not select Delete from disk and do not delete the vmdk files.

Clone the VM. Do not select the Customize the operating system option.

Do not use the default or custom sysprep file, so that the clone has the same SID.

Attach the shared RDMs to both VMs and power them on.

Change the host name and IP address on the first VM (VM1).

Note the original IP address and host name that were used at the time of the installation of vCenter Server on VM1. This information is used to assign a cluster role IP.

Install failover clustering on both nodes.

To create an MSCS cluster on VM1, include both nodes in the cluster. Also select the validation option for the new cluster.

To start configuring roles, select Generic Service and click Next.

Select VMware Service Lifecycle Manager from the listed services and click Next.

Enter the host name and IP used for the VM1. Then assign the RDM to the role.

In the Replicate Registry Settings wizard, add the registry key SYSTEM\CurrentControlSet\Services\VMwareDirectoryService and click Next.

Using Add Resource, add the VMware AFD and VMware vCenter Configuration services to the role by 'Add Resource' action.

Add Cluster Disk and Cluster Role IP resource as dependencies for 'VMware vCenter Configuration Service'.

Stop and restart the role.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)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:

Related Versions:

Take Our Survey

Support Assistant