We just merged a PR that changes the UI to allow offline backups for delta backups, disaster recovery and continuous replication: https://github.com/vatesfr/xen-orchestra/pull/9228

Now, if your delta backup makes offline backups, you can disable that without having to change the backup type.

b-Nollet opened this pull request in vatesfr/xen-orchestra

closed fix(xo-web): allow offline delta backups #9228

Hi @Forza,

I made a fix to prevent the "No new data to upload for this VM" message from appearing if it is only true for a part of the backup jobs of one VM.

It's available here: https://github.com/vatesfr/xen-orchestra/pull/9286

You can test it by switching branch if you're running XO from sources, otherwise you'll need to wait for the next end of month release.

b-Nollet opened this pull request in vatesfr/xen-orchestra

closed fix(backups): fix incorrect info on mirror backups #9286

@Forza

Thanks for the details, I managed to reproduce after a few trials.

I'll try to fix it and keep you informed.

@Forza

As the named are greyed-out, could you confirm that the delta backup job saves the backup to remotes srv04-incremental and srv12-incremental, and the mirror backup job copies the backups from srv12-incremental to srv04-incremental? (or at least confirm these are the same couple of remotes)

Also, could you tell me if the VM with which you got the "No new data to upload for this VM" message was backed up by your backup job "Incremental backup every 4 hours - 8 days retention"?

Thanks @Forza,
I'll try on my own with a similar configuration.

I confirm that this is the current behaviour, as @pilow reported here https://xcp-ng.org/forum/post/99446

We might change it in the future to make it better, but it won't be trivial to change.

Hi @Forza,

Could you send us a screenshot of your backup job configuration so we can try to reproduce?

Hi @k11maris,

I think the situation you showed in your screenshot where both options are selected but are both greyed out should not happen.

We will try to reproduce it on our side and fix it.

Hi @cbaguzman,

We just merged a PR that should allow you to use vhd-cli check on encrypted remotes: https://github.com/vatesfr/xen-orchestra/pull/9235

Please note that, as stated in the PR description, this PR changes the parameters you need to give to several vhd-cli commands, including the parameters of vhd-cli check. You can use vhd-cli check --help for details.

Here's an example of a command I ran on an encrypted remote:

vhd-cli check --chain 'file:///localRemoteEncryptedTEST?useVhdDirectory=true&encryptionKey=%2219876543210987654321098765432109%22' 'xo-vm-backups/695550e5-16e4-4728-6669-ac39e79f19e2/vdis/2656e4f4-efbc-47a6-95aa-0ba88632e545/7a1b144e-1ec8-44e8-9f5e-2d39119a228d/20251125T095729Z.alias.vhd'

b-Nollet opened this pull request in vatesfr/xen-orchestra

closed feat(vhd-cli): accept all types of remotes #9235

Hi @k11maris,

You can either specify the snapshot mode or check the "Offline backup" option.

It's a bit counter-intuitive, but to uncheck it, you can set "Snapshot mode" to "Normal", and you should be able to modify it. (then you can put back the snapshot mode to offline)

Hi @cbaguzman,

Currently there's no way of performing the vhd-cli check command on an encrypted remote, but this is also annoying for us and it shouldn't be too hard to fix, so I'll fix it.

I made a fix for this: https://github.com/vatesfr/xen-orchestra/pull/9228

I'm not that familiar with disaster recovery, I'll discuss your point with the team.

b-Nollet opened this pull request in vatesfr/xen-orchestra

closed fix(xo-web): allow offline delta backups #9228

Ok, thanks for the information.

I think I saw somewhere a bit of code that saves the value of 'Offline backup' so users don't have to re-check it if they go back to full backups, but it shouldn't interfere with delta backups.

I'll investigate this and keep you informed.

Hi @k11maris,

I just noticed I originally misread your message, you were already talking of the 'Snapshot mode' option I mentioned.

Could you send us a screenshot of the backup job configuration?

Hi @k11maris,

I reproduced the same behaviour, but I think this is perfectly normal.

If you want to only do an offline snapshot and restart the VM while the export is happening, you should uncheck the 'Offline backups' option and set 'Snapshot mode' to 'Offline'.

Hi @jshiells,

After some tests, I don't think it can be caused by the load balancer.

If the load balancer tries to migrate a VM that is being backed up, the migration instantly fails and nothing happens.

Reversely, if a backup job starts when a VM is being migrated by the load balancer, the backup will fail for that VM with error "cannot backup a VM currently being migrated".

Hi @jshiells,

Sorry for not answering earlier, Pierre wasn't working during the past weeks.

I'll soon investigate on how the load balancer interacts with backups.

@Pilow You might be right, this may be simpler to implement than we imagined.

We'll keep you informed when we progress on this.

Thanks @Pilow for the test

Hi @Pilow,

We might improve this in the future, but for the moment you'll have to create two different schedules, one for the day with healthcheck, and another one for the six other days. Then, create two different sequences, one for each schedule.