XOA - backups skipped to protect VDI chain
-
Click on the link "Job canceled to protect the VDI chain", this will lead you to our documentation explaining everything
edit: in very short, you are replicated faster than your storage can keep up.
-
hi Olivier
thats the first thing i did, so i may do my backups every other day now
what about if i manually delete each vms snapshot
i rescanned the SR in question, on XOA and on xen server
how long do you think it will take to coalesce
if need be i will shut down each vm, copy them to the same SR but change the vms name, this works, as i have done it before but its very slow
-
Don't remove a snapshot if you don't need too. That's removing a snapshot that cause coalesce.
You can check disks needing coalesce in Xen Orchestra (SR, Advanced tab)
-
i have and theres 37 that need coalesce
is the only option to wait or to copy the vm to a new SR or copy it to a new name so it appears to be a new vm?
-
Please wait first, until there's nothing to coalesce. Use snapshots wisely because you probably created/removed a lot in few time. And more to coalesce, longer it will be.
-
so is the reason because of that snapshot, stopping the auto backups on XOA?
its been 3 days but now i have changed my auto backups from everyday to every other day, so lets see
-
I'm not inside your infrastructure, but if you delete a snapshot on your side, this will need a coalesce after. So if you removed a lot of snapshot, then a large coalesce on numerous disks should be done.
-
and to do a coalesce, you just rescan the SR?
-
Yep, then wait.
-
thanks Olivier
-
just another question about this
do you think i should stop my backups on XOA, will it only interfere and make the coalesce even longer?
-
Don't do any snapshots manually. XOA should skip if the chain isn't clean.
-
what about if i get rid of orphaned vdi disks on the SR, will this work
-
Orphaned VDIs are something else, that might indeed need to coalesce after that. But that won't change the principle: clean everything first.
-
how do i know what vm was causing the backups from running as there all saying "Job canceled to protect the VDI chain"?
thanks,
rob -
Because XO will backup only VM without coalesce issue. So all skipped VMs needs to coalesce first.
-
Think I've found the solution
https://www.quadricsoftware.com/knowledge-base/orphaned-vdi-prevents-coalesce/
-
I'm not sure it's related to your issue. Do you have spotted the exact message in question in this page? If it's the case, you can clean everything from the UI of XO in Dashboard/health.
-
think i have answered my own question -
basically dom0 is protecting the source vdi until vbd operations complete but theres nothing to complete
you think this is worth a shot
-
Same answer as the other topic, as I exactly said in my previous post here: you can solve this in XO, Dashboard/health view.
