An issue was identified in backup jobs running in incremental with commit 100f113 or release 6.5.0. If one of your incremental backup chains was corrupted, it lead to a cleaning of vdis folder resulting into backup lose.
Please update your source at least to 4552fb9 or your XOA to 6.5.1.
If you encountered issues about a warning with aliases, you are concerned. You need to run your backup jobs again to have your backups back on track.
Hi,
The latest version of XO-lite has an issue, that is why we are temporarily reverting to version 0.19.0. Sorry for the lack of communication on our part.
@itservices Hi,
We did not forget you, working on it!
@Pilow Hi,
Thank you for your reporting! It should be fixed in the next version we are thinking releasing this month if no surprise happens. There is a big refactoring on the clean part which handles metadata (and size) updates.
@Pilow Hi,
Thank you for the report.
We are fixing this in https://github.com/vatesfr/xen-orchestra/pull/9362.
It will be fixed during in a patch.
If you need to install something from hub now, you can get back to Stable branch
@itservices Can you check your health dashboard where you should see " Unhealthy VDIs" ? If there are too many VDI in it, they need to be coalesced before restarting a backup.
@itservices Hi,
It seems the parent of the backup chain is not found (a delta backup links to another delta and another, until you have a full backup, it seems a backup on this chain is missing).
Can you restart a backup chain to have a full backup? You can do it by reducing the retention in your backup job.
@MajorP93 We are building an automated QA that we keep updating and running regularly (preferably nightly) to add any event possible. We missed this one because we did not took enough failures into account, so we added a regression test for this too.
@itservices Hi, xen-bugtools is in xcp-ng hosts. You can directly get the logs from the hosts if you don't have the command.
@itservices
Can you export your logs with xen-bugtool --yestoall please? If you prefer to avoid exporting everything, we especially need /var/log/xensource.log and /var/log/SMlog
@Team-Storage do you have an idea about the source of the issue?
@skipthompson81 Hi, as you have an XOA, can you open a support tunnel to allow us to investigate further into this issue please? You can open a ticket and ask for Pierre Brunet.
This warning is a log we added to be sure we check everything in the backups but it can be alarming indeed but the checks are hard to do and can be false positive so we don't want to panic everyone.
@itservices Can you check your health dashboard where you should see " Unhealthy VDIs" ? If there are too many VDI in it, they need to be coalesced before restarting a backup.
@itservices Hi,
We did not forget you, working on it!
@itservices It may be a storage or a xo issue. You can try to restart xo-server and retry the backup. If it is solved, it was an issue with xo-server not freeing your vdi. If it still happens, it will be a storage issue
@itservices Hi,
It seems the parent of the backup chain is not found (a delta backup links to another delta and another, until you have a full backup, it seems a backup on this chain is missing).
Can you restart a backup chain to have a full backup? You can do it by reducing the retention in your backup job.
@CGB Hi, are you running XO from source with root or another user?
If it is another user, it may be not accessible from it
@FagnerMoraes The delta backups are in vdis folder. You can see it just below cache.json.gz
@FagnerMoraes I just realized you are not listing the same folder that what is backed up in your NAS backup job: on the left, you are listing incremental backups from a given folder, but in the logs I analysed the xva are in another folder
