Can confirm [NOSNAP] [NOBAK] works with xen 8.2, xo 3a212. Well NOSNAP can't technicaly work, but it don't break anything.

I decided to install a new server and use ronivay's script from github to install and later update XOCE. It is working well for me and I'm not going to work on fixing the other server now.

@cgasser This sounds like a perfect candidate for the new Backup Sequence feature. See https://xen-orchestra.com/blog/xen-orchestra-5-99/ for full details.

@julien-f Merciiii my config.toml file was located under /root/.config/xo-proxy after restarting xo-proxy.service, I was able to use its local storage as a backup target. It's cleaner than creating an NFS loopback

@Bambos try restarting your hosts.

@McHenry Interesting that the CLI doesn't show the active job, but you still see it running on XO. Though I wouldn't call it a "Hidden Job" since the web console shows the operation. Jobs run in the XO API and not on a given host directly, so this is expected behavior. Would be interesting to see if a given host or pool master can see the running jobs from XO though. . .

@DustinB said in XOA Retention - entries must be sorted in asc order: I've since removed the entries in the long-term-retention field, and will validate if the backup succeeds here in a bit. Once removing the LTR records, backups succeeded. @olivierlambert said in XOA Retention - entries must be sorted in asc order: Hi, It's a known issue that will be fixed this month Good to know, thanks!

@MathieuRA Thank you!

This will come for some vendors (with their own APIs). We do not want to use SSH for that though (XO never use SSH).

@olivierlambert @florent @MathieuRA ?

Hi Guys, Just to report back. Got it working. Two ways to do this. 1.) Create 2 schedules for one backup job, forcing one to run as full. 2.) Run backup until the next backup interval is going to do a full. Disable backup, and wait until a time that when enabled will hit the time you want the full to run. In my case after 5pm. I appreciate this way is not practical, but does work. [image: 1736498866320-12291419-456e-4cd7-8a67-5cc6430a9c4f-image.png] Appreciate you help guys !!

@olivierlambert Dou! Thanks for clarifying the speed limit - I've adjust to 100MiB, which should use about 80% of my available bandwidth. Resolving the VDIs' appears to have worked as backups going now. I just have these long running tasks which have been going multiple days with no end in sight that I can't resolve. I suspect they may be related to why I can't migrate VM's between hosts now. Cheers Kent. [image: 1736362940089-screenshot-2025-01-09-at-7.59.46-am.png]

@DustinB Yes

@olivierlambert A quick follow up for anyone performing warm migrations. If you elect for the migrated VM to be powered on post migration, then the option to protect from accidental shutdown needs to be off to enable the source VM to be turned off when the migrated VM it turned on. [image: 1736209112115-c09859e7-b32d-486a-90ed-e44061d68ead-image.png] If you like the thrill of adrenaline and elect for the source VM to be deleted post migration then the protect from accidental deletion would also need to be turned off. I am not that brave.

Great! You are right! I had completely forgotten about it! Thanks a lot!

@olivierlambert Makes sense! I would schedule the replication to occur a couple hours after the backup runs are complete to ensure its a replica of all data and not a partial replica!

Q1. Yes. IB & IR share the same principle. Q2. Key backups are a plus to be on the safe side, but it's not the only way to do it. You also have backup health check, as you suggested. To me, it depends on the criticality of your data. To me, health check after 20 IR isn't bad but it's really a "personal" choice

Hi, IIRC, the scheduler is smart, if it's using the same time, it will reuse snapshots as possible. @florent could give more details when he's around