@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

Hi @McHenry If you still have the problem, you can increase the healthCheckTimeout value as Olivier recommended (e.g. healthCheckTimeout = ‘30m’), however this value should be in the [backups.defaultSettings] section of the configuration file (or in the [backups.vm.defaultSettings] section) rather than in the [backups] section. We've detailed the documentation a bit to make this more understandable: https://github.com/vatesfr/xen-orchestra/blob/a945888e63dd37227262eddc8a14850295fa303f/packages/xo-server/config.toml#L78-L79

Hi, I'm not sure to get it, pinging @julien-f

It's up to you to do whatever you need with the VM copy. Clone the replicated VM, remove the NICs (for example) and boot it.

@DustinB Drives from a secondary NAS

@DustinB Yes, I completely agree and understand everything you're saying. All of my compute is used elsewhere and I have no spares. In my situation where I lack the budget (and time) for something more robust, USB HDD manual backups will work perfectly well for me (atleast temporarily in these early stages) to preserve my investment of months of work on my datacenter. I appreciate your insights though.

@olivierlambert Great. Posted here and didn't open ticket because this is interesting for all ...

@Danp Ah, thank you for that. I need to restructure things a bit but I was already thinking I would do that. The issue is that this VM also runs NUT so it's the last VM running before shutting down the servers. I reduced the memory because it takes a LONG time to suspend a VM with 16GB RAM but doesn't take long to shut one down. Between the 8 to 10 minutes it takes for XCP-ng to shut down and the time it takes to suspend a VM with 16GB RAM, I don't think my batteries will last that long. I'll have to move NUT into a leaner VM that doesn't handle backups. That's something I was thinking I would do anyway because if there was a power outage during a backup I don't think my NUT script would be able to do what it needs to do. Based on the cron job I run to make sure my xo-cli registration is good, the xo-cli stuff won't run when the VM is hammered like this. Thanks for helping me understand why this happens and how to fix it.

Yes, the default timeout for XAPI tasks is 24 hours. This can be modified as explained in the documentation -- https://docs.xcp-ng.org/management/manage-locally/api/#24h-task-timeout

Your backup won't be affected if the VM is rebooted while the backup is running.