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 Server Appliance backup over SCP stuck between 40 - 60% (70877)

Last Updated: 11/10/2021Categories: TroubleshootingTotal Views: 19562Language:
English

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Symptoms

VCSA backup using SCP gets stuck between 40 - 60% and fails

Restoring the VCSA from such a backup fails with the error:

Metadata and system validation failed
Backup PNID is not resolved on the network please configure the network DNS service accordingly

When executing the command below you receive output that is not an FQDN or IP:

/usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost;

Purpose

This article provides steps to resolve the backup issue when using SCP when the PNID of the vCenter Server Appliance is a short-name.

Cause

The backup process relies on the use of an FQDN or IP for the PNID. When a short-name is set for the PNID it is unable to resolve this correctly and the backup process fails.

Resolution

This is expected behavior as a result of deploying the VCSA using a short-name as the PNID.

For VCSA versions prior to 6.7 U3 it is not possible to change the PNID after deployment. For more info, see Cannot change the vCenter Server or Platform Service Controller 6.x hostname on versions prior to vCenter Server 6.7 Update 3.

Workaround

To work around this issue, follow the steps below:

Connect to the console of the VCSA using SSH.

Take a backup of the files we will be editing using the command below:

cp /etc/resolv.conf /storage/core/resolv.conf.backup; cp /usr/lib/applmgmt/backup_restore/py/vmware/appliance/backup_restore/util/Net.py /storage/core/Net.py.backup;

Add search domain.com to end of the /etc/resolv.conf file using the command below where domain.com your own domain:

echo 'search domain.com' >> /etc/resolv.conf;

In the file /usr/lib/applmgmt/backup_restore/py/vmware/appliance/backup_restore/util/Net.py change the following line from:

ipV4Cmd = ['/usr/bin/dig', '+noedns', '+short', pnid, 'a']

to

ipV4Cmd = ['/usr/bin/dig', '+noedns', '+short','+search', pnid, 'a']

Note:

Ensure that only the +search parameter is added.
Net.py is read-only so need to save with :wq!

Restart the VAMI service using the command below:

service-control --stop applmgmt;service-control --start applmgmt;

Retry the VCSA backup via SCP.

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
•
HCX 統合のための NSX 要件 (71398)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

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

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant