This should be recoverable, but it can be difficult to troubleshoot this way. Have you investigated the BAD_POWER_STATE error? From your first screenshot above, it looks like the VM is suspended, not stopped. Have you tried starting it with xe vm-resume?

@TechGrips I'm simply trying to provide assistance. It easy to misinterpret a forum post, so let's just chalk it up to a miscommunication.

@TechGrips said in How to do Simple Backup to Local USB Drive?:

I've done that, many times actually, as I mentioned in my original post.

Hmmm... I must have missed that in my quick review of your OP. Checked again, still don't see where you mentioned trying to create a local BR.

Create a local backup remote under Settings > Remotes. Then use it as the target for your backup jobs.

The memory usage being reported may be incorrect due to the way Node uses memory. I see kswapd0 with high CPU usage in your screenshot, so that is a clear indicator that swapping is occurring. Give the VM 16GB again and the issue should resolve itself.

Yes, the default timeout for XAPI tasks is 24 hours. This can be modified as explained in the documentation -- https://docs.xcp-ng.org/management/manage-locally/api/#24h-task-timeout

Your backup won't be affected if the VM is rebooted while the backup is running.

@kagbasi-ngc Try changing ({name}) to {{name}} in your user filter

Isn't this the same issue caused by the Node upgrade? https://github.com/nodejs/node/issues/54359

notr1ch created this issue in nodejs/node

closed Happy eyeballs implementation times out prematurely #54359

@kagbasi-wgsdac You can monitor the XO logs by issuing the command journalctl -u xo-server -f -n 50 and then retrying the export from within XO.

You could also check the logs on the XCP host -- https://docs.xcp-ng.org/troubleshooting/log-files/

@kagbasi-ngc Maybe this? https://docs.xcp-ng.org/releases/release-8-3/#nested-virtualization-though-not-on-purpose

@kagbasi-wgsdac AFAIK, it should be browser agnostic. Do you get any errors? Have you checked the browser console for any useful output?

You could try exporting the VM from the XCP-ng host's CLI using xe vm-export.

@kagbasi-wgsdac Can you explain your use case? Does the download work if you click the Download VM link or the OK button?

As mentioned in the following image, the URL is only valid for a short period of time --

Whenever I click the link or the OK button, the download automatically starts via the browser.

You should start by checking the logs. https://docs.xcp-ng.org/troubleshooting/log-files/

Hi,

Can you explain the steps you are taking to perform the export?

Dan

A few things you could do --

• Share the full error message (see entry in Setting > Logs)
• Switch to the "latest" release channel to see if issue also occurs there
• Review our Vmware migration checklist -- https://help.vates.tech/kb/en-us/37/133

HTH, Dan

Have you checked to see if there is a backup network configured on the pool (bottom of the pool's Advanced tab in XO)?

@jebrown For now, there is a limit of 7 network interface on a VM on XCP-ng/Xen Orchestra.

How many network interfaces are defined on this VM?