@Greg_E hi there,

beyond number of minimal hosts to be supported (think it's 3) and minimal disks to get good redundancy (I think its minimal 3 per host, must be identical) you have a replication parameter when building an XOSTOR

it defaults to two (you have two copies of each workload) and this parameter can impact your total usable space.

also beware of network requirements (for satellites connections, and DRBD replication)
minimum of 2 nics per server, and DRDB replication should be at least 10Gb nics

tip : the linstor-controller is not always the pool master...

go here : https://docs.xcp-ng.org/xostor/#prerequisites

@kent you would have to rollback to early december 2025 XO/XOA (before the 10 of december)
quite a long way

I'm just waiting the devs to eventually fix it as we have other way to manage VDIs (API calls)

@benapetr you seem gifted with app development.

do you know RV Tools ? https://www.dell.com/support/kbdoc/en-us/000325532/rvtools-4-7-1-installer

this tool is pretty handy when auditing VMWARE infrastructures, it can connect to vcenter or directly to ESXi and full dump in csv/xlsx the infrastructure configuration (all aspects of the config, be it VM, hosts, networks, datastores, files, ...)

I could see a real production use of same tool, but for XCP Pools/XCP hosts

would be a great add to XenAdmin !

@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

@florent okay
but at 3 days without reboot i'm like this :

still on XOA 6.1.2

uptime is 2 days for me

but restarted xo-server yesterday

zoom on 2 hours

@pdonias nice !

@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

@florent rest and xo-cli
tunnel ID sent by message

@florent okay disabled.
We have quite an extensive use of API calls too, all over the place
and websockets (to get VM console in in-house web app)

I don't know if this could have an impact

@florent not really, it is activated and I tried to fiddle a bit with it, why ?

@florent said in backup mail report says INTERRUPTED but it's not ?:

is the memory stable on the proxy ?

can't really say, as i reboot them everyday with my XOA

but when I do not reboot them, they dont seem to be so impacted as I need to reboot them.
I will detach them from the reboot job and will report RAM consumption on proxies

@florent do you have (heavy?) use of backup jobs on your XOA ?
we all noticed this because of correlation between backup jobs & memory growth

I do have all my backup jobs through XO PROXIES though, and XOA still explodes in RAM Usage...

@acebmxer @ronivay stumbled upon this too
https://github.com/ronivay/XenOrchestraInstallerUpdater#backup-proxy

Backup proxy
Proxy installation method is experimental, use at your own risk. Proxy installation from sources is not documented by Xen Orchestra team. Method used here is the outcome of trial and error.

Proxy source code will be edited slightly to disable license check which only works with official XOA and there is no documented or working procedure to bypass it properly (there used to be but not anymore)

@acebmxer Great job (I guess, will need to give it a try)
looked the script and seems pretty complete.

Do you plan to add XoProxy install/update too ?

@acebmxer as per your screenshots, we can guess you have daily backup jobs operated by the XOA
and the memory graph is significant of a reguler OOM kill (out of memory)

there is some kind of memory leak happening and the devs are investigating it in another thread in here

upgrading to 8GB or 16GB your XOA memory will take it more days before OOM happens, but it will happen

check this thread https://xcp-ng.org/forum/topic/11721/backup-mail-report-says-interrupted-but-it-s-not/48

lol your previous post answered my questions. other-config.

@DustyArmstrong I have hard times to understand how the VM is aware of the XOA it is/was attached to...

a VM resides on a host
a Host in in a pool
a Pool is attached to a (or many) XO/XOA

how the hell your VM is aware of its previous XO ?

@DustyArmstrong said in Detached VM Snapshots after Warm Migration:

I mainly just want to know the best method to wipe XO and start over so it can rebuild the database.

ha, to wipe XO , check the troubleshooting section of documentation here :
https://docs.xen-orchestra.com/troubleshooting#reset-configuration

it is a destructive command for your XO database ! 

@DustyArmstrong mmmm what do you mean by pool master and pool slave ?

You have one pool with 2 hosts ? one master and one slave ?
could you screenshot the HOME/Hosts page ?
and the SETTINGS/SERVERS page ?