@vmpr there is a high chance that we improve the scheduler , so maybe be able to plan more precisely when the full occurs, but we will always keep one full backup as the beginning of the chain You can mitigate the risk on infinite schedule by using health check : restoring the backup automatically after the job, this ensure that , at the time of backup, the files are correct, and that if an issue occurs in the backup you can start a new chain, thus detecting a backup storage issue before needed it after having a production issue

@julien-f thanks! I have tested it and its working now! cheers Ringo

@jedimarcus thank you i will have a look!

@julien-f @olivierlambert thanks guys I will wait until the end of the month you rock!

Thanks guys! Absolut Legends

@olivierlambert here it is: https://github.com/Stevesibilia/check_snapshot Keep in mind i'm not a developer

@vmpr Great work and example!

@vmpr Not much, this is a system issue which means that it's either due to your NFS server or to the connection between your XO and the NFS server. First, try to unmount the share and restart xo-server, if it keeps happening, restart the whole machine on which XO is. If that does not help, you should mount the share manually and do some tests directly on it.

@vmpr Please create an issue on Xen Orchestra GitHub repo, this way XO dev will see it