@olivierlambert Ahh sorry. I'll give that a shot this weekend and report back.

Sorry @olivierlambert, I don't understand the question. I'm using XOA to make the changes and run the backup.

@olivierlambert Updated to commit 395d8, same issue. Re-enabled health check, ran backup (failed as expected), and then disabled health check and ran backup again and it still failed with the same error. Seems stuck.

@olivierlambert Sorry, meant to reply earlier. I'm on source, commit 1643d.

@olivierlambert 100%. I even checked to see if I could uncheck it, click OK and then not save it and when I do that it's back to checked as it should be. I also tried a few times over the last couple of weeks to re-check, save, un-check, save, and it makes no difference.

I enabled Health Check on my backups just to see if it worked, and it didn't, which is fine. So I turned it off, but despite that, it appears the backups are still attempting to run a health check. Here are the backup settings with health check unchecked:

The backups however now show as failed as it appears to be trying to do a health check against the NFS share that I'm using as the remote destination. Any ideas why this is happening?

@julien-f Not really, no haha. So we use a PSA software called Halo for our business and they have a concept of service monitoring whereby you can setup a service and have Halo monitor for when an email is not received on time (every 24 hours, for example), when an email is received in a success state, and when an email is received in a failure state. Then it can be setup to automatically create a ticket when a failure is noted. So I really just need to know the subject line for when a backup encounters an issue.

Is there somewhere I can see the backup report templates? Or, does anyone know what the different possible subject lines are? We are sending the backup reports somewhere we can parse the emails and need to know what to trigger alerts on. Thank you!

@olivierlambert Haha, it's so obvious! Didn't even think to select both at the same time. Genious, thanks.

I'm just trying to understand and architect a backup configuration that doesn't result in so many snapshots on my main server. Right now we are using continuous replication to keep our primary server synced with a secondary server. We were originally going to also have delta backups to an external NFS, but that would result in 2 snapshots kept on our main server, which we don't have space for. So my next thought was to setup delta backups off the secondary server that has the continuous replicated backups on it, but that doesn't work either, I suspect because the UUID changes every hour (as we are replicating every hour). Is there a way to configure this so we have a nightly copy of our backups without it having to keep a snapshot? Worst case scenario, we can run a 3rd party backup off our secondary server, but was hoping to avoid that if possible. Thanks.

We were originally planning to have an external VPS running XOA so that if there were issues with either of our servers, we could still access XOA independently. What we noticed after doing this was that backups go through XOA, which is blowing through the available bandwidth we have on our VPS. Is there a way around this? Or will backups always go through XOA? Thank you.

Long story short, whatever we set for the "xoa" password after installing Xen Orchestra doesn't work. Probably my screw-up. Is there a way to reset that password from XOA web interface (which I can login to)? Failing that, what would I lose by deploying a new XOA? I assume perhaps backup configurations?