Our future backup code: test it!
-
@florent All my backups have this set! And this only happens with the new backup code, never with the old.
-
@florent Giving up on mirror backups. Switching to direct backups to remore storage.
At least until this works again as expected. -
At least I reproduce it locally , when going from a non block remote to an encrypted remote
Is your target remote encrypted ?
-
@florent Simple NFS, no encryption.
-
@manilx said in Our future backup code: test it!:
@florent Simple NFS, no encryption.
I have a potential fix here on the branch fix_backup
( https://github.com/vatesfr/xen-orchestra/pull/8635/files)closed fix(disk-transform): backup omnibus fix #8635
-
@florent waiting for final master
-
@manilx said in Our future backup code: test it!:
@florent waiting for final master
this will reach master today, and probably be released in the may version of XO
-
So are we now at the point that Delta backups, Mirrors and CR backups are all working and considered stable? I have only been able to test delta backups with my home lab setup which have been working without missing a beat since the May 22nd fix for tasks not clearing. (MS-01 running XCP-NG, TrueNAS for storage)
We do use make use of CR jobs pretty extensively with the full XOA appliance for our DR site at work but because its full XOA and "production" i have not tested anything there. That said hoping for no nasty surprises with the may XO update if this is planned on being pushed to the stable XOA release!
-
@flakpyro Very good question. I really don't need the aggravation of any backup job breaking on our production site......
-
@flakpyro the stable branch, is the stable xoa. The latest release is " it is tested, but on limited hardware". The "pull from master and use it" is on best effort, I wouldn't advise to use it on any critical use.
the april's release is stable and will be promoted to stable today.
the may's release probably won't be promoted to stable in june, given the massive changes. my guess is that the june's release maybe , if we deem it stable enough -
@Tristis-Oris have CR jobs started working for you with the latest master code?
@florent Understod! Our XOA appliance has been on the latest branch since we deployed it almost a year and a half ago. Though with all these changes i may consider dropping it down to stable for a bit as backups are pretty critical. We only use Delta jobs (Which seem to be working well) and Continuous replication jobs. (Which i have seen some issues with recently in this thread). -
@flakpyro nope. same error.
-
@olivierlambert @florent I still hit a single thread limit in the XO VM that makes backups CPU bound limiting performance as before.
-
@florent so testing a CR job with the latest XOA release. The job runs successfully and i can see the virtual disk on the remote SR however the replica does not appear in XOAs VM inventory view.
Edits:
They do appear in XCP-NG Center,and XO Lite
They do NOT appear to show up using xo-cli list-objects
This also appears to ONLY happen to Windows VMs. Maybe related to missing templates?VMs that have not yet even ran their daily replication job also seem affected. Replicas that ran last night and appeared in inventory before the update now now longer appear in the VM inventory list. This might be related to something else that was changed in the new XOA update?
-
@flakpyro Nice catch! I see the same problem.
@olivierlambert @florent Running XO source (master 6ed35). I see the Windows VMs in the CR backup job report, but they no longer appear on the destination host as a VM. Some have updated tools, others do not. It worked before... Non-windows VMs seems to be fine. These are all old VMs, so it's a new problem on existing systems.
-
@Andrew weird, never seen that.
too many tasks maybe? -
The windows VM disappearing is likely a web UI bug. I'm reporting it.
-
@olivierlambert I think so! All my regular Delta+CR combination jobs run as usual tonight without issue which is good news after such a massive change.Ii can see the newly replicated copies when looking in XO-Lite or XCP-NG center so likely just a UI issue that is hopefully a quick and easy fix!
-
@olivierlambert @flakpyro Commit 2fd5759 seems to solve the issue for me.
-
Seems fixed in XOA 5.107.1
