@ph7
Thanks for the help...I think that gets me close. I will tinker with it some more. Thanks again for the answers.

@ph7
Wouldn't that run the health check daily though? I have a daily delta backup but only want to run the health check on the weekends or maybe monthly. I think this is where I am misunderstanding how to set it up.

Hi everyone,

I want to set up a backup health check to run weekly or monthly for just a few VMs, but I’m getting stuck on how to properly schedule it.

We currently back up about 90 VMs daily using delta backups, split across multiple jobs. From what I understand, I need to add the health check as another schedule within a job. However, when I try to do this, it asks for a retention setting, which is where I’m getting confused.

Does adding a health check as another schedule in the job actually create an additional backup?
For example, if my backup job runs on Sunday at 9 AM, and I add a health check schedule for Sunday at 2 PM with a retention of 1, what happens?
Does the backup run again at 2 PM before performing the health check?
Does this effectively create two backups on Sundays?
How does the retention setting of 1 affect this process?
Is there a better way to handle this without unintentionally doubling backups?

Thanks in advance for any guidance!

@olivierlambert Thanks! Seems obvious now that I clicked on it but I didn't know I could get to them through there.

How should one go about manually deleting S3 Backblaze backups?

I totally created this problem myself and I'm just working to clean it up and free up space.

Early in our XO journey I moved some vm's around from one SR to another and moved them to a different on prem backup job and also a different S3 mirror.

This left the existing backups in place and did not purge them. After their retention was passed I manually deleted (via XO) the on prem NFS backups. However, the S3 backups still live on and I can't figure out how to remove them.

What's the best way to purge those?

Thanks!

@tjkreidl Gotcha and thanks!. In our scenario we wouldn't have a VM on more than one SR but I understand that some people would.

@olivierlambert Thank you! That helps to clarify significantly. I have a couple follow up questions if you don't mind....I'm trying to make this as bulletproof as I can...ie.....the building burns down and I have to recover everything from Backblaze.

Would I be able to recover from scratch if I was only ever using incremental (with the 20 day full interval)?

Will running a separate full basic backup outside of the incremental break/upset the backup chain in any way?

Thanks again!

@Nick-085 I had it like that originally and the Backblaze transfer seemed to slow down the entire job.

That's why I am testing the mirror job. Backup to fast local storage at night and transfer to Backblaze during the day.

I've been doing backups with various products for a long time so I understand the concepts. I'm trying to learn the Xen Orchestra way and I think it just hasn't clicked with me yet.

I’m building out backups and doing it by SR.

I have 4 NFS SR’s and I have built 4 backup jobs to match those SR’s.

We are planning to use it like backup tiers:
NFS-1 = high priority vm’s
NFS-2 = med priority
NFS-3 = lower
NFS-4 = nobody cares lol…..or only backup weekly or only keep 30 days…stuff like that.

Is there a way to target the backup job to the SR? I know we can tag vm’s but if a coworker moves a vm to a different SR and forgets to change the tag it could get messy over time.

Thanks!

I configured a delta backup to an NFS remote.
-Run daily
-Full backup interval: 20

I want to run a mirror backup of that to Backblaze B2.

The documentation says-
If you have full and incremental backups on a remote, you must configure 2 mirror backup jobs, one full and one incremental.

Does that mean I need 2 different mirror backup jobs or am I misunderstanding?

Thanks!