@hawkpro I believe it will be worse with continuous replication because your replica will be in a shut down state. When you decide to start it, you will have to shut down the original VM and start the replica. You will have a downtime during shut down and start up sequence. Downtime during VM migration is a necessity so there is nothing unexpected there. All types of migrations require a VM to be suspended for some time (usually seconds) during the switchover from one host or SR to the other host or SR. If you have extended downtimes of your VM migrations, then something is not quite right with your setup.

@AtaxyaNetwork Hello! I am on an XOA trial with no airgapping.

All vms still on host 1 after setting Migration cooldown time to 0 this morning. Maybe bug or just ui bug. When set to 0 save config when you load the page the "Fill information" for Migration Cooldown setting is unchecked but 0 is still applied. If set to 1. and reload the box is check as expected.

502 is an answer coming from your S3, telling the server is having an issue. Adding @florent in the loop

I looked into the backup job and i forgot to enable a few settings when recreated the backup job. After renabling the below settings i reran the backup job. The vm in question did a full backup. All passed. [image: 1772848089214-screenshot_20260306_204613.png] { "data": { "type": "VM", "id": "fb72a8d7-a039-849f-b547-24fc56f056ba", "name_label": "Work PC" }, "id": "1772833993844", "message": "backup VM", "start": 1772833993844, "status": "success", "tasks": [ { "id": "1772833993868", "message": "clean-vm", "start": 1772833993868, "status": "success", "end": 1772833994233, "result": { "merge": false } }, { "id": "1772833994652", "message": "snapshot", "start": 1772833994652, "status": "success", "end": 1772833997235, "result": "16f5fe19-207a-4d89-017c-3f9405d22231" }, { "id": "1772834490355:0", "message": "health check", "start": 1772834490355, "status": "success", "infos": [ { "message": "This VM doesn't match the health check's tags for this schedule" } ], "end": 1772834490356 }, { "data": { "id": "a5e54e04-d7e4-48cb-bafc-b2f306d39679", "isFull": true, "type": "remote" }, "id": "1772833997235:0", "message": "export", "start": 1772833997235, "status": "success", "tasks": [ { "id": "1772834004185", "message": "transfer", "start": 1772834004185, "status": "success", "end": 1772834489032, "result": { "size": 119502012416 } }, { "id": "1772834490368", "message": "clean-vm", "start": 1772834490368, "status": "success", "end": 1772834490475, "result": { "merge": false } } ], "end": 1772834490476 } ], "infos": [ { "message": "will delete snapshot data" }, { "data": { "vdiRef": "OpaqueRef:31692cb3-7c43-de83-2cc8-f2e39a0105c8" }, "message": "Snapshot data has been deleted" } ], "end": 1772834490476 }

@wralb it is in master, we are preparing a patch release for XOA on monday morning with this fix

I've had a lot of updates happening in the homelab. I've replaced the T620 with an R740, expanded my storage for both HDD and NVME pools. Also did a little min-maxing on the hardware to help separate traffic, decrease some latency and jitter for internet traffic and introducing IDS There are a lot of additions and modifications, but I guess the other big one is setting up a Dell Precision 5820 with XCP-NG as a studio and prototyping rig. Replaced Ansible with AWX, added some more VMs and migrated others but in all that I've updated the diagrams as well! Will say that XCP-NG offers up the flexibility and performance that I've needed so far. Would love to try out the XOSTOR storage at some point but will have to move around my entire setup haha. This reference diagram breaks down each VLAN [image: 1772850854389-networking-and-vlans-reference-diagram.drawio.png] The physical equipment reference diagram gives a breakdown of the server equipment and NAS at both locations, including the home rack. It also shows a basic breakdown of each server configuration. [image: 1772850854434-physical-equipment-reference-diagram.drawio.png] The physical topology reference diagram gives a simplistic overview of the major networking and server equipment. [image: 1772850854468-physical-topology-reference-diagram.drawio.png] The logical topology reference diagram gives a more in-depth view of the networking, servers, VMs, VLANs and endpoint devices. [image: 1772850854364-logical-topology-reference-diagram.drawio.png] The colo reference diagram contains my off-site location with a rented dedicated server [image: 1772850854295-colo-reference-diagram.drawio.png] The Authentication reference diagram gives a break down of how user access is sourced or what security route it takes. [image: 1772850854275-authentication-reference-diagram.drawio.png] The shared storage and access reference diagram gives a break down of how most hardware interacts with each other in regards to network routing for users, endpoints, and member servers. [image: 1772850854483-shared-storage-and-acess-reference-diagram.drawio.png]

@florent I have tested in our dev environment backing up a 30GB VM, which compressed into 22GB and was uploaded in 739 parts of 40MB each. I will test a larger VM next week but I think this was successful test is already conclusive. Thank You

I am in the same situation as @vhaelan. same as in same iGPU (alderlake) passed-through, same output for those latest commands, same OS (Fedora CoreOS on latest Xcp-Ng stable). Tried current avenues suggested in this thread with no progress. It seems vhaelan has settled with CoreOS under Proxmox (which works!). He also mentioned it works in Debian under XCP-ng, though I haven't tested that myself. I would appreciate additional suggestions for troubleshooting to take this further, in case anyone has any other ideas.