@Greg_E Looks like you were writing a reply as I was... But yeah, Truenas is on the roadmap at some point in the future, once I've had the time to dig into the details and understand where this fits in the overall system architecture. Out of interest though, where would you see Truenas fitting in with this setup outlined below? My initial thoughts are that Truenas in this context would be either; A glorified USB Stick storing ISOs A glorified (RAID Redundant) of an External HDD running as the Backup platform Or both of the above Have I understood that context correctly? Current setup is essentially..... Bare Metal HBA Raid Controllers for Storage Primary Raid Array Backup Raid Array Dom0 XCP-ng Server DomU XOA VM Backups; Primary Raid Array -> Backup Raid Array Backups; Primary Raid Array -> Remote PC Backups; Primary Raid Array -> Dom0 Remote PC ISOs via SMB Share Truenas in the above context would simply be an additional backup to either; A Truenas VM on the Base Metal as a VM A physically separate Bare Metal running Truenas (aka. a glorified RAID'ed External USB Disk). Is that where you would see things fitting into the overall system architecture? Curious to get your thoughts on that.....

@Pilow Maybe at some point. Unless someone would like to contribute that part. I want to make sure XOA install is good and stable first. I just switch over my homelab to this install now.

@olivierlambert I wish I had newer generations of the big HP DL360 on the bottom, mine do not support uefi, and that's getting in the way. Sitting power off to keep the bios battery from running down. Those are 20 cores with 128gb each, and again 10gbe networking.

@olivierlambert It's even older than that. https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.v5.md#5540-2020-12-29 https://xen-orchestra.com/blog/xen-orchestra-5-54/

During the past month my backups failed (status interrupted) 1-2 times per week due to this memory leak. When increasing heap size (node old space size) it takes longer but the backup fails when RAM usage eventually hits 100%. I guess I’ll go with @Pilow ‘s workaround for now and create a cronjob for rebooting XO VM right before backups start.

@danp The POST /vbds endpoint allows configuring both "RW" or "RO" and a bootable Boolean. If I need to mount an OS installation ISO and a separate provisioning VDI to the same VM, I assume I must execute two distinct POST /vbds requests: For the CD-ROM (ISO): Set "mode": "RO" and "bootable": true. For the provisioning VDI: Set "mode": "RW" and "bootable": false. Would this work in mounting my OS .iso to my VM in the CD-ROM and also mount the VDI to the vm so it will read it on first boot? { "VM": "VM-UUID", "VDI": "VDI-UUID", "bootable": false, "mode": "RW" }

@Pilow Yeah I was following your post. At first I thought i was having random backup issues with backups via proxies with the occasional issue with backups via xoa. Then just yesturday see the error about memory. For now I just rebooted XOA and it down under 2gb currently. Will wait and see how long for it to build back up again or untill Dev team finds a solution to the problem.