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

vCenter services not starting automatically after a restore from an image based backup. (78042)

Last Updated: 12/3/2021Categories: TroubleshootingTotal Views: 36194Language:
Chinese (Simplified)JapaneseEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

vCenter / PSC not fully starting after restoring VM from backup.

Backup method was an Image Based Backup.

Backups using the VAMI file based backup are not impacted.

vmon service is masked - thereby not allowing all services managed by vmon to start.

Unmasking vmon allows services to start successfully.

On reboot vmon becomes masked again.

On a manual start of the services, it fails as below,
==================================================
#service-control --start --all
Operation not cancellable. Please wait for it to finish...
Performing start operation on service lwsmd...
Service lwsmd startup type is not automatic. Skip
Performing start operation on service vmafdd...
Service vmafdd startup type is not automatic. Skip
Performing start operation on service vmdird...
Service vmdird startup type is not automatic. Skip
Performing start operation on service vmcad...
Service vmcad startup type is not automatic. Skip
Performing start operation on service vmware-sts-idmd...
Service vmware-sts-idmd startup type is not automatic. Skip
Performing start operation on service vmware-stsd...
Service vmware-stsd startup type is not automatic. Skip
Performing start operation on service vmdnsd...
Service vmdnsd startup type is not automatic. Skip
Performing start operation on profile: ALL...
Service vmware-vmon startup type is not automatic. Skip
Service-control failed. Error: Failed to start services in profile ALL. RC=11, stderr=Connect error. ErrCode: 111

Here is how you check if vmon is masked
=======================================
# systemctl list-unit-files | grep vmware-vmon.service
vmware-vmon.service          masked

To unmask the service
=======================================
#systemctl unmask vmware-vmon.service

Note- this will allow you to start the service - but the issue will reoccur on reboot.

Resolution

Run reconciliation operations below after you restore the vCenter appliance from an image based backup.

Navigate to the vCenter Server Management Interface, https://vCenter_FQDN_or_IP:5480 , and click "Set up vCenter Server Appliance" button.

Input the root password and click [LOG IN].

Click [NEXT].

Input SSO user name and password, then click [FINISH].

Reconciliation starts. Wait 15 - 30 minutes to finish.

Reconciliation completes and you will be able to access vSphere Client.

Related Information

"Failed to execute operation: Unit file is masked" when we try to start the service on VCSA 6.5
File-Based Backup and Restore of vCenter Server Appliance
VMware vCenter Server Appliance 6.7 File-Based Backup & Restore (VIDEO)
vCenter Server Appliance 6.7 File-Based Backup and Restore Walkthroughs (VMWARE BLOG)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant