Our future backup code: test it!
-
@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
-
I created a new CR job for another VM and it worked. However, it didn't work with the XO VM.
So maybe the root cause of the problem is that the old CR copies have disappeared. Maybe they still exist, but I can't find them?
