I could be wrong but from VMware world the management interface didnt transfer much data if at all. It was only used to communicate to vsphere and/or to the to the host. So no need to waste a 10gb port on something only only see kb worth of data.
Our previous server had 2x 1gb nics for management 1x 10gb nic for network 2x 10tgb nic for storage 1x 10gb nic for vmotion.
Thanks for the quick reply. Is this what you were referring to? - https://xen-orchestra.com/blog/xo-proxy-a-concrete-guide/
Can someone please verify my steps are correct or provide documentation how to deploy XOProxy with remote host / location.
Currently Working:
Site 1
XOA
Pool1 - 2 XCP-NG host.
Thoughts.
Am I overthinking this, missing anything?
Updated to Commit 04338 and the backups are fixed Thank you.
{
"data": {
"type": "VM",
"id": "b25a5709-f1f8-e942-f0cc-f443eb9b9cf3",
"name_label": "SeedBox"
},
"id": "1756290916238",
"message": "backup VM",
"start": 1756290916238,
"status": "failure",
"tasks": [
{
"id": "1756290916244",
"message": "clean-vm",
"start": 1756290916244,
"status": "success",
"warnings": [
{
"data": {
"path": "/xo-vm-backups/b25a5709-f1f8-e942-f0cc-f443eb9b9cf3/20250816T170026Z.json",
"actual": 26680452096,
"expected": 26680452608
},
"message": "cleanVm: incorrect backup size in metadata"
}
],
"end": 1756290917313,
"result": {
"merge": false
}
},
{
"id": "1756290917697",
"message": "snapshot",
"start": 1756290917697,
"status": "success",
"end": 1756290934498,
"result": "53f984e4-0ac2-8f77-2c74-f71ed8e56a8f"
},
{
"data": {
"id": "95ba58d1-f202-4900-9b1f-7933adbc6764",
"isFull": false,
"type": "remote"
},
"id": "1756290934499",
"message": "export",
"start": 1756290934499,
"status": "success",
"tasks": [
{
"id": "1756290936032",
"message": "transfer",
"start": 1756290936032,
"status": "success",
"end": 1756290942108,
"result": {
"size": 1061158912
}
},
{
"id": "1756290955378",
"message": "clean-vm",
"start": 1756290955378,
"status": "success",
"warnings": [
{
"data": {
"path": "/xo-vm-backups/b25a5709-f1f8-e942-f0cc-f443eb9b9cf3/20250827T103536Z.json",
"actual": 1061158912,
"expected": 1063779840
},
"message": "cleanVm: incorrect backup size in metadata"
}
],
"end": 1756290956472,
"result": {
"merge": false
}
}
],
"end": 1756290956478
}
],
"infos": [
{
"message": "Transfer data using NBD"
}
],
"end": 1756290956478,
"result": {
"message": "Missing tag to check there are some transferred data ",
"name": "Error",
"stack": "Error: Missing tag to check there are some transferred data \n at IncrementalXapiVmBackupRunner._healthCheck (file:///opt/xo/xo-builds/xen-orchestra-202508271005/@xen-orchestra/backups/_runners/_vmRunners/_Abstract.mjs:76:13)\n at IncrementalXapiVmBackupRunner.run (file:///opt/xo/xo-builds/xen-orchestra-202508271005/@xen-orchestra/backups/_runners/_vmRunners/_AbstractXapi.mjs:407:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async file:///opt/xo/xo-builds/xen-orchestra-202508271005/@xen-orchestra/backups/_runners/VmsXapi.mjs:166:38"
}
},
{
"message": "Transfer data using NBD"
}
],
"end": 1756290942772,
"result": {
"message": "Missing tag to check there are some transferred data ",
"name": "Error",
"stack": "Error: Missing tag to check there are some transferred data \n at IncrementalXapiVmBackupRunner._healthCheck (file:///opt/xo/xo-builds/xen-orchestra-202508271005/@xen-orchestra/backups/_runners/_vmRunners/_Abstract.mjs:76:13)\n at IncrementalXapiVmBackupRunner.run (file:///opt/xo/xo-builds/xen-orchestra-202508271005/@xen-orchestra/backups/_runners/_vmRunners/_AbstractXapi.mjs:407:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async file:///opt/xo/xo-builds/xen-orchestra-202508271005/@xen-orchestra/backups/_runners/VmsXapi.mjs:166:38"
}
},
{
"data": {
"type": "VM",
I on commit a4410
Backup seam to break during one of the commits yesterday. I have not tried to run a full backup as of yet.
I just updated to Commit d1577 and I seam to have the bug now.
@olivierlambert said in Moving my homelab from vmware (vsphere8) to xcp ng:
Hi,
Since Vates doesn't develop VEEAM, I don't see how I could answer that question
A first closed beta started since yesterday. If you want to have your answer, you have to ask them
Glad to see strong movement with the Veeam team. @olivierlambert I know you are limiting beta testing to internal at them moment. But if you do need further testing from the community I would like to sign up.
keep up the hard work Vates team you doing great work.
When viewing the restore page I constantly have to press the refresh backup list button to see the correct value for total backups and to see the S3 restore points or wait 2 -3 min to have it update on its own. If i navigate way from the page and back again i have to press refresh again or wait.
Can xo-ce not store this information and then update periodically? Why does it need to constantly contact the S3 every time the page is visited?
This is probably something to do with nginx proxy manager but maybe someone can assist.
When i access xo-ce from proxy manager i can not see my custom tags.
If i access xo-ce from ip address i can see them...
You need to select a vm template.
Update - After shutting down the VM and removing the previous snapshot and creating new one. I left VM powered off after creating new snapshot. VM is migrating now.
Screenshots of VM settings and files...
I dont see a the file that it is looking for...
I am trying to complete my vmware migration and I have 2 more vm's to migrat. All have been successful until now...
This is the error message i get when trying to migrate the VM.
503 Service Unavailable https://192.168.1.125/folder/ArcDC01/ArcDC01-000001-sesparse.vmdk?dcPath=ha-datacenter&dsName=SSD_DataStore
Suggestions? I have since started the VM back up on vmware and the VM is working.
The only thing i did differently was take a snapshot from a shutdown state before removing the vmware tools. This server is our Primary Windows Active Directory.
@Danp said in XOA license issue:
@acebmxer It looks like you've resolved the first issue by binding the trial license. You haven't yet purchased support, so you won't be able to bind licenses to your XCP-ng hosts. This has no effect on the functionality of the hosts.
Ok thank you for the update that this is expected behavior. We do plan to pay for support just need to take care of a few things on our side before we do so.
I know this is an old thread but just incase others come accross it. @Greg_E did you resolve this?
Did you install the UEFI certs into the new install - https://docs.xcp-ng.org/guides/guest-UEFI-Secure-Boot/
I had some issues and had to do them manually see here - https://xcp-ng.org/forum/topic/11129/xcp-ng-8.3-uefi-certs-wont-install
Yeah i didnt do anything with disabling the vgpu. Just a standard Win 11 or ubuntu VM and attached the nivdia gpu.