File Restore : error scanning disk for recent delta backups but not old
-
@mtango said in File Restore : error scanning disk for recent delta backups but not old:
It looks like vhdimount doesn't like more than 99 backups.
Indeed, it's a known issue: https://github.com/vatesfr/xen-orchestra/issues/4032
-
If we pay for support, are there any feasible options to remove this limitation in the next few days? Our target is to be able to have at least 365 backups.
Since it is very easy to reproduce, you shouldn't need access set up, I assume. -
It probably won't be easy to remove this limitation, especially in the next few days.
If you can use the full backup interval setting, it should remove this issue.
-
Indeed, the full backup interval seems the right option.
-
It is not clear to me if I can simply activate that option right now, in the state that I am with backups of 121 days that don't work past 99. Will vhdimount be needed to perform the first full backup or not?
Also we're planning on setting that interval somewhere around 60 (2 months). Can this open issue be encountered: https://github.com/vatesfr/xen-orchestra/issues/4987 ?
closed Delta backup "out of range" error in merge phase #4987
-
@mtango said in File Restore : error scanning disk for recent delta backups but not old:
Will vhdimount be needed to perform the first full backup or not?
No, it's only used for file restore.
@mtango said in File Restore : error scanning disk for recent delta backups but not old:
Can this open issue be encountered: https://github.com/vatesfr/xen-orchestra/issues/4987 ?
We have no idea what trigger this condition, it may be old corrupted VHD files.
If you want to check your backups, you can take a look at this post
-
Thank you for your help @julien-f. We will change our backup strategy according to this limitation.
I'd suggest adding a warning in the web UI and xo-server console logs regarding File Recovery if the number of delta backups is set to a number greater than 99. It is a bit troubling that it took so long to find out this was a simple limitation known for more than a year.
-
Hi, I've noticed the addition of the commit about the 99 limit warning. That's good news.
I am now having trouble trying to understand the meaning of the Full Backup Interval setting.
I have the following scenario:
- Backups for the last 30 days, daily.
- Backups for the last 52 weeks, weekly.
- I want to make sure that the delta backups are not corrupt periodically (let's say once a month).
I don't understand how to set the schedules, the backup retention, the full backup interval.
I also need answers to the following questions, and I haven't been able to understand this from the documention.
- Do I need one delta backup with 2 schedules, or 2 backups with one schedule each ?
- I've noticed that full backup interval is per backup, whereas retention is per schedule. How do these two settings interact with multiple schedules?
- On what dates will the transfers be large ?
- How many full backups will be stored on the remote at any given time ? When will the merges happen?
Thanks
