Hi @olivierlambert, No performance gain to keep the snapshot. It's more the opposite. Leaving the snapshot means it will be only removed in the next job, meaning you'll have more to coalesce. However, it's very stable, CBT tends to have some quirks from time to time, so worth trying on few VMs first. Thanks - perhaps the backup documentation could have a page that covers each of these options and the pro's / con's of enabling / disabling each of them. They seem to be newer options added as they weren't even shown in the webinar video and I couldn't find any mention of them anywhere. Also, if it's better to have this option enabled, then perhaps it could be enabled by default ? I don't think it's possible now. I can ask internally if it's something that's planned already or doable in the future Thanks - that'll be good. Either option will be good. The ability to set the 'Full Backup Interval' against the individual schedule instead of the whole backup task may be all that needs to change. I'll submit a ticket to get this feature request started. Thanks Kent.

@Danp Thank you very much! Missed it

As a separate thought, do you have another instance of XO (or XOA) running somewhere which may have been configured with the xo-config file?

@florent Clear now, thanks!

Question for @florent

@olivierlambert Is this listed on GitHub so I can track any discussion/progress? I am keen to see this implemented as currently we receive backup reports of failed jobs and have no idea which host is came from.

@olivierlambert That's awesome. Would they just show up in the detached backups list? Or is there another way to find them? Disregard. I see that they still show up in the restore tab. This is great!

@Danp said in Running a Backup Job for a Pool that wasn't previously in said backup job: @DustinB said in Running a Backup Job for a Pool that wasn't previously in said backup job: Are you suggesting for just this run I remove the old pool from this section and rerun the job? Yes. Making those changes now and running the job. Thanks for confirming

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 !!