Every VM in a CR backup job creates an "Unhealthy VDI"
-
Greetings,
I'm experimenting with CR backups in a test environment. I have a nightly CR backup job, currently for 4 VMs, all going to the same SR, '4TB on antoni'. On the first incremental (second backup after the initial full) an unhealthy VDI is reported under dashboard/health... one for every VM in the job. A subsequent incremental result in an additional reported unhealthy VDI, again one for each VM.
For example:
The following VMs each currently have the initial full, and three subsequent incrementals in the CR chain:- HR-FS
- maryjane
- zuul
Note that there are three reported unhealthy VDIs for each.
The remaining VM, exocomp, currently has only 1 incremental after the initial full, and there is one reported unhealthy VDI for that VM.
Is this normal? If not, what details can I provide that might help get to the bottom of this?
-
@joeymorin That's correct. They need time to coalesce after snapshots change. Length of 1 is normal. They should clear up after a few minutes.
-
@Andrew, they do not clear up. Please read my OP carefully and look at the screenshot. They remain forever. They accumulate, one for each VM for every incremental. Nightly CR, four VMs, four more unhealthy VDIs. Tomorrow night, four more, etc.
-
We made some fixes very recently (yesterday), can you check you are on latest commit? (if XO sources)
