Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Decommissioning an ESXi host from a Workload Domain in SDDC Manager fails at the Restore Hosts subtask. (56629)

Last Updated: 12/1/2018Categories: TroubleshootingTotal Views: 2659Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While decommissioning an ESXi host in SDDC, the subtask 'Restore Hosts' fails with an error similar to the following:

"Restoring image to host 192.168.x.x"

You see messages similar to the following in the /home/vrack/vrm/logs/evodsddc.log file on the SDDC Manager Controller VM:

2018-05-18 09:06:46.887 [pool-23-thread-1] ERROR [com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine] [CA0UJB] Exception in task: Restore Hosts for Workflow viDecomm
issioning-43df6de0-4a2d-11e8-83c1-1fc3d27d992b-1526021811622
com.vmware.vrack.vrm.core.error.InternalServerErrorException: /backup/hostbackup/R1N4/statebackupinitial not available on 192.168.x.x
at com.vmware.vrack.vrm.iaas.tools.service.EsxiBootbankBackupServiceImpl.downloadToLocalFolder(EsxiBootbankBackupServiceImpl.java:198)
at com.vmware.vrack.vrm.iaas.tools.service.EsxiBootbankBackupServiceImpl.downloadToLocalFolderFromLcm(EsxiBootbankBackupServiceImpl.java:179)
at com.vmware.vrack.vrm.iaas.tools.service.EsxiBootbankBackupServiceImpl.restoreEsxiFolder(EsxiBootbankBackupServiceImpl.java:74)
at com.vmware.vrack.vrm.workflow.tasks.removal.hostrestore.RestoreHostsFromImageTask.doForHost(RestoreHostsFromImageTask.java:79)
at com.vmware.vrack.vrm.workflow.tasks.removal.AbstractMultiHostTask.run(AbstractMultiHostTask.java:63)
at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine.executeTask(SimpleWorkflowEngine.java:550)
at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine.runSingleTask(SimpleWorkflowEngine.java:501)
at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine.access$1000(SimpleWorkflowEngine.java:47)
at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine$2.run(SimpleWorkflowEngine.java:311)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment

On the SDDC Manager Utility VM, the hostbackup directory for the affected host may be empty..

Resolution

This is a known issue affecting VMware Cloud Foundation 2.2. There is currently no resolution.

Workaround

To workaround this, you must copy the equivalent backup files from the host directly on to the SDDC Utility VM.

Log in to the SDDC Manager Utility VM as the root user.

Change directory to the affected host backup:

cd /backup/hostbackup

Create a host directory for the affected host:

mkdir R1N6/

Note: Change R1N6 to match the affected ESXi node name.

Change directory to the newly created host directory:

cd R1N6/

List the contents of the directory:

ls

Note: You will see output similar to the following:

bootbankbackup

Create the two default statebackup directories:

mkdir statebackupinitial
mkdir statebackuplatest

Change directory to statebackupinitial:

cd statebackupinitial/

Copy the files from the statebackupninitial directory on the affected ESXi host to the SDDC Utility VM:

scp [email-masked]:/store/statebackupinitial/* .

Notes:

Replace 192.168.100.100 with the IP address of the affected ESXi host.

You will see output similar to the following:

The authenticity of host '192.168.100.110 (192.168.100.110)' can't be established.
RSA key fingerprint is SHA256:tiKDtVkK1eQWY8ZKB1WHKowPqy6L1A3H1fIN9KHUTPo.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.100.110' (RSA) to the list of known hosts.
Password:
configBundle-rack-1-n6.vcf.vsphere.local.tgz 100% 22KB 16.0MB/s 00:00

Follow the same process as step 7, this time with the statebackuplatest directory:

scp [email-masked]:/store/statebackuplatest/* .
statebackuplatest/cd ../

Notes:

Replace 192.168.100.100 with the IP address of the affected ESXi host.

You will see output similar to the following:

Password:
configBundle-rack-1-n6.vcf.vsphere.local.tgz 100% 50KB 24.5MB/s 00:00

Change to the hostbackup directory:

cd ..

Change the permissions on the files:

chown -R backupuser:users *

Restart the Decommission Host workflow in SDDC Manager.

Related Information

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 2.x

Take Our Survey

Support Assistant