Check the output of dmesg -T|grep -Eiv 'guest|capacity|promiscuous' on the host. It's likely that there was a network disconnect at some point and you have a stuck mount. You could also check to see if df -h hangs when you execute it on the host.

@msupport Thanks for the detailed report. Please answer these questions to help us to better understand the source of the issue:

• What OS were the affected VMs running?
• Which guest tools were installed?
• Were the affected VDIs in VHD or QCOW2 format?

Hi,

I found your original request. I will make sure someone from the Sales team responds ASAP.

Regards,
Dan

Hi!

Which documentation did you follow?

Did you verify the md5sum of the downloaded XVA file?

The XCP-ng logs may provide further insight into the error: https://docs.xcp-ng.org/troubleshooting/log-files/

Regards,
Dan

@acebmxer Pretty sure that coming from Veeam. Did you try the option to Restore with different settings?

Actually, isn't XAPI 24.19.2 what is shipped with the original XCP-ng 8.3 release? If so, then you could just do this --

• Reinstall XCP-ng on the new host
• Restore the pool metadata
• Patch the host

This is the safest method to allow the metadata restore --

• Reinstall XCP-ng on the new host
• Patch it to bring it to the correct XAPI level (use https://help.vates.tech/kb/en-us/14/103 as a reference)
• Restore the pool metadata
• Patch the host again to install any remaining updates

See https://xcp-ng.org/forum/post/101039 for a prior example of this. Your case involves a different XAPI version, so a custom list of required packages would be required for it to work.

Thanks for the reports and the detailed analysis. I'll make sure that the XOA team is notified.

Does it fail every time or is it an intermittent issue?

@pedro_udifar Please update to the latest code base and then let us know if you still encounter this issue.

@pedro_udifar What is your current commit for the XO VM? Can you share the full error log as an attachment?

@rvreugde I believe this is already being reviewed internally.

@acebmxer Do you have VMs that aren't configured for HA? Does it work if you temporarily disable HA?

@pkgw Thanks for the feedback. The good news is that there is already an effort under way rework and enhance the RPU process. Let me ping @Team-XAPI-Network and @Team-XO-Backend in case they want to request additional information from you.

It's possible that you hit this known issue.

If you haven't rebooted after patching, then that could be a contributing factor.

Have you tried restarting the toolstack?

To investigate further, you can review the host's log files https://docs.xcp-ng.org/troubleshooting/log-files/

IIUC, the Smart Reboot option found on the host's Advanced tab does what you are asking.

@skipthompson81 said:

this CONFLICT is not OK!

You will need to provide more details about this specific backup job. It's possible that the backup succeeded, but then the subsequent Health Check failed or timed out. Have you tried downloading and examining the full log from the failed backup?

I'm not positive, but this may be available RSN in xo-lite.