Taxi cab confession. I was using an install script to build XO from source due to laziness. I started troubleshooting and found there was a memory leak, no matter how many resources I gave to XO it would max out memory and eventually cause the interrupted error.
I decided to build XO from source following the guide. Everything is working perfectly now. SMB write is about 50% faster, read is almost 300% faster.
I'm on XO from sources, xo-server 5.53.0 & xo-web 5.53.3 on Debian 9. Does Netdata require Debian 10 or XOA? I am unable to click on "Enable Advanced Live Telemetry" on my host, when I mouse over I see the notification that the Netdata plugin is required.
I've verified all plugins are available and enabled, but I don't see the Netdata plugin in the web interface nor in the packages directory.
I updated to the latest yesterday afternoon, not long after making this post then tested. Backups ran successfully, but it started a new backup so it took a full backup of the VM. Not sure if it removed the previous backups from the remote. The backup scheduled to run at midnight also completed successfully.
I would consider this resolved for now.
The error presented in the UI is 0 === 512 and the backup log is attached. All other VMs in the job are succeeding, so I removed those details from the log.
XO installed from sources following the guide
Installed on Debian 9
Is there an existing method to allow backup retries on failure? Something like retry up to X amount of times after Y minutes/hours after the last failure.
@olivierlambert then there must be either an issue with @mts environment or with XO. Per his post it isn't working. I'd be curious to see what the actual issue is.
This wouldn’t be a custom script. Linked below is a write up of application-aware processing in Veeam.
https://helpcenter.veeam.com/docs/backup/vsphere/application_aware_processing.html?ver=95u4
Guest tools for Windows may already have support for Microsoft VSS built in. If so, Backup NG would just need to take advantage.
You could also enable circular logging on the mail databases. In Exchange 2016 it's under Servers -> Databases -> Maintenance