backup mail report says INTERRUPTED but it's not ?
-
From my XOA
One of my pools have been offline for 24hrs due to power outage.
Standard XOA can open support tunnel if needed.
-
On tomorrow 's release we will:
- reduce the polling for the patches list
- add more debug to know exactly what request go through the xo6 api (rest api)
following this we will add core xo metrics to the openmetrics ( prometheus) export to allow users and support to dig through real world data when needed
-
@florent thanks for working on this!
-
@florent since your early patch of my XOA (xo-server restart at the disk activity peak)
noticing vif0 transmitting a bit on the network and different ram activity on a timespan of 2 hours
something has changed, is it for the better ?
let the night decide -
Updated to XOA 6.2.0 Will monitor memory usage and report back.
Current use before backups after update. All host and pools connected as of yesterday.
-
uptime is 2 days for me
but restarted xo-server yesterdayzoom on 2 hours
-
@Pilow we really did only add one small log . we'll need to dive deeper for a real cause ( and fix)
-
@florent okay
but at 3 days without reboot i'm like this :
still on XOA 6.1.2
-
I may have fixed the issue myself. I have moved our Windows VM backups to Veeam and leaving XOA to backup linux VMs.
-
@acebmxer That is very interesting! So according to your tests the XOA backup memory leak is only occurring when Windows VMs are being backed up?
-
No by reducing the number of vms that are being backed up by xoa.
I moved Windows vms to veeam as we need application aware backups.
-
-
@MajorP93 we have almost same size 30 backup jobs (mixed delta/cr/repl/dr) for 95+ VMs
but these are not operated by XOA but dispatched in 4 XO Proxies
and still XOA get OOM killed
