“Unable to write data to the transport connection: Broken pipe”
“Unable to restore the disk in HotAdd mode. Restoring disk using the Import functionality”
SCALING
We found over 200 CBT metadata VDI files throughout the XCP-ng pool, from dozens of different backup jobs. We don’t yet know how many of these have broken parent references, but it could affect significantly more VMs than the 2 that are already corrupted.
OUR QUESTIONS
Is anyone else using CBT on XCP-ng with Veeam v13.1 and has observed similar issues?
Is it known that the DeletePointTransformSpec can corrupt VHD parent references?
Why does Veeam report “Success” when the worker tokens have expired? Shouldn’t the job at least issue a warning?
Is Error 1920 (vPower NFS during MSI installation) a known issue? Is there a fix for it?
Has anyone found a way to safely verify whether the parent references in CBT metadata VDIs are valid?
Is there a best practice for regularly resetting CBT (Active Full) without the risk of a broken VHD chain?
OUR WORKAROUNDS
Deleted affected CBT metadata VDIs (xe vdi-destroy)
Restored VMs from backup
Disabled CBT on all VMs until the issue is understood
Restarted the Veeam Backup Service (reset worker tokens)
Scheduled Active Full backups instead of incremental ones
Thank you very much for your feedback and suggestions.
