Too many snapshots

Pilow

@McHenry for TOO MANY SNAPSHOTS in this case, better look the RETENTION applied to this CR schedule

how many retention points do you have in the schedule of this job ?

McHenry

Currently set to 15 on one schedule and 1 on the other schedule

Pilow

@McHenry could you screenshot the SNAPSHOTS tab of a problematic VM ?

the new backup & CR code changed the way it is handled as you understood... no more "one VM per replica point", but "one VM with a snapshot per replica point"

you should see 16 snapshots on the VM ?

EDIT : my bad, its the first screenshot you provided... indeed 16 snapshots

I do not remember the snapshots limit per VM (50?) , but you seem to bee far from it

Pilow

the limit enforced by XOA is 30

https://docs.xen-orchestra.com/backup_troubleshooting?utm_source=chatgpt.com#vdi-chain-protection

McHenry

@Pilow

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

Pilow

@McHenry could be another cap limit on the SR
can you screenshot homepage GENERAL tab of HST150 SR ?

how many VDIs present ?
what type of SR is it ?

jr-m4

Throwing my two cents into the hat, as well.

I had a similar situation. Snapshots would't be rotated out of retention, regardless of what I set on the retention setting (on a subset of VMs ie not all of the).. The thing that solved it for my, was to recreate the affected schedule.
Do note that this will mark the previous backups taken by that technically deleted schedule, as being abandoned/orphaned.

But after I did this, snapshots would be properly rotated as expected.

McHenry

@Pilow

SR is local storage

McHenry

@jr-m4

Recreated, testing now.

McHenry

@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.