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 🙂

I am running the latest XO. I ended up fixing the issue, it has backed up successfully 2 times now without any errors. What I did was removed ALL snapshots for the specific VM. Once the tasks finished for removing the snapshots, I created a new manual snapshot. Then let the backup happen as normal. What I noticed though is the backup snapshot replaced my manual snapshot so the VM still only has 1 snapshot. But it seems to be working now.

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

Also adding @MathieuRA

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.

Ping @florent

Ping @florent

@flakpyro for now there is no tag selector , but you can now select the VM list to be replicated

Hi,

For reference, it's in our "Product management" backlog on ref PRODU-69. Now we need to find the time to prioritize this and investigate on it first (how much effort needed).