@Pilow

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.

@henri9813

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.

@Pilow

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.

@Pilow

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

@tjkreidl

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.

@tjkreidl

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

I am rerunning the backups after recreating the schedule to see if the error clears

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

@jr-m4

Recreated, testing now.

@Pilow

SR is local storage

@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

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

@Andrew

Is this it?

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:

1. hourly CR during business hours - retention 15
2. daily full CR at 8 pm (full) - retention 1

I am happy with this; however, I am not 100% sure how best to manage the offsite backups.

We currently perform:

1. Daily Delta at 8 pm

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?

1. can run Mon-Thurs at 8pm
2. can run Fri at 8pm (usually takes 3 days to complete a full offsite)
3. will conflict with 2

@itservices

Thanks Marc

@dinhngtu

So I need to reinstall and not check the option for Manage via Windows Update?

I am seeing this error on all VMs on a host.

https://docs.xcp-ng.org/vms/#xsa-468-multiple-windows-pv-driver-vulnerabilities

I have checked the Xen Tools and the latest version is installed.

https://www.xenserver.com/downloads

@Pilow

Agreed however as our xcp-ng hosts are in the cloud with OVH Cloud we cannot use a physical appliance. We are currently setting up a dedicated OVH server for pfSense.