Thank you for the response.
To be 100% sure I am not compromising backups, can I clarify that I am able to have a CR retention value of 13, and the warning can be ignored?
When I started a replicated VM, I opt to start a copy, not the original. Would the 13 snapshots still impact performance?
So for CR backups it is safe to have a retention value of 13 and just ignore the warnings?
Is it possible to have a CR backup with a retention value greater than 4 without generating the too many snapshots error?
We have tested and concluded that as the new CR backups generate snapshots, a retention value of anything greater than 4 will generate a too many snapshots error.
We wish to have hourly CR backups between 7am and 7pm so we need a retention value of 13; however, it does not appear that anything greater than 4 is possible without generating errors.
I did check this and it definitely completes within the hour.
I am testing a lesser value for CR retention to see if this resolves it.
Thanks.
The old snapshots are being removed as the total never increases beyond 16, so when a new snapshot is added, the old one is removed.
The number of snapshots shows 16, which makes sense as I have two backup schedules, one with a retention of 15 and one with a retention of 1. The daily backup with a retention of 1 resets the chain, as it is a full backup.
CR jobs are not failing just XO reports too many snapshots under:
Dashboard >> Health
All good if I can just ignore this warning but thought best to check in case it was an issue.
I got the value of 3 from here.
https://docs.xen-orchestra.com/manage_infrastructure#too-many-snapshots
If each CR backup is now created as a snapshot, instead of a new VM, and the alert triggers after a VM has more than three snapshots, this logically means that the alert will trigger if the CR has a retention value greater than 3.
Have I misunderstood how the CR backup process works?
@tjkreidl
The offsite backup runs at 8 pm and takes 6/7 hours, whereas the hourly runs from 7 am to 7 pm and only take a few minutes.
The backup job has 19 VMs, suely this is not too many.
I wish to maintain 16 restore points using CR, being an hourly restore point over the last two days (8 per day)
I perform a full backup nightly to reset the chain.
It appears that each CR creates a new snapshot and the old snapshot is removed when a new one is crated
The documentation states this error is shown then there are more than 3 snapshots on a VM
https://docs.xen-orchestra.com/manage_infrastructure#too-many-snapshots
Is this a problematic backup strategy?
@Pilow
Was there an announcement about the change in how these CR backups are done with snapshots now?
I'd love to read up on it.
Thank you. I did not know this change had been made.
So now I have the master VM with a snapshot for each backup schedule.
And a CR created VM with 16 snapshots.
I wonder why the health check shows too many snapshots as I am well under 30 per VM
Currently set to 15 on one schedule and 1 on the other schedule
I have 15 VMs included in a CR backup job.
Recently, I have seen notifications of "too many snapshots".
Whereas previously, each CR job would create a new VM, it appears now that each CR job creates a new snapshot.
The job itself appears to be configured correctly
I am sure I have a setting wrong, but I cannot find which one.
We currently perform:
I am happy with this; however, I am not 100% sure how best to manage the offsite backups.
We currently perform:
I wanted to add to this:
2) a weekly full backup - retention 8
3) a monthly full backup - retention 12
My question is, how can I schedule these three so they do not conflict with each other?
