Hi, I am Karlis, I manage small server/network infrastructure, our VMs are hosted on Xenserver. Some time ago we needed to redesign management and backup system for our VMs and we found XO. Now we are in process to upgrade our hosts to XCP-NG.

@Ascar In XO cloud means pool, "hamburger" means host. If VM is running, it belongs to host where it runs, and receives host icon, no matter where it is kept in stopped state. If VM is stopped, it belongs to pool if kept on pool shared storage (cloud icon), or to host, if on host's local storage (hamburger).

WinServ 2025 on xcp-ng 8.2.1, xcp-ng tools v.8.2.2 rc1. No additional roles, except Windows Admin Center preview installed. Uptime about 2 months. No conhost processes at all.

ISO works, installed already on 2 Ubuntu 22.04 VMs

@waveguide said in What are recommended ways to grant XCP-ng and XO access to the internet?:

Do you poke holes in your firewall so the Management network can resolve DNS requests and reach the IP addresses

Outgoing communication from management and xcp-ng hosts to Internet is not very dangerous, because hosts are the initiators. Generally I don't block it. You can monitor these connections or restrict to certain addresses.

@olivierlambert Done

Right now one of my CR jobs are stuck, symptoms are the same as with XO from sources.
XOA 5.43.2 (xo-server and xo-web 5.56.2)
Hosts where VM is running and where it is replicated to, both XenServer 7.0
Backup log:

{
  "data": {
    "mode": "delta",
    "reportWhen": "failure"
  },
  "id": "1582750800014",
  "jobId": "b5c85bb9-6ba7-4665-af60-f86a8a21503d",
  "jobName": "web1",
  "message": "backup",
  "scheduleId": "6204a834-1145-4278-9170-63a9fc9d5b2b",
  "start": 1582750800014,
  "status": "pending",
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "04430f5e-f0db-72b6-2b73-cc49433a2e14"
      },
      "id": "1582750800016",
      "message": "Starting backup of web1. (b5c85bb9-6ba7-4665-af60-f86a8a21503d)",
      "start": 1582750800016,
      "status": "pending",
      "tasks": [
        {
          "id": "1582750800018",
          "message": "snapshot",
          "start": 1582750800018,
          "status": "success",
          "end": 1582750808307,
          "result": "6e6c19e2-104c-1dcf-a355-563348d5a11f"
        },
        {
          "id": "1582750808314",
          "message": "add metadata to snapshot",
          "start": 1582750808314,
          "status": "success",
          "end": 1582750808325
        },
        {
          "id": "1582750808517",
          "message": "waiting for uptodate snapshot record",
          "start": 1582750808517,
          "status": "success",
          "end": 1582750808729
        },
        {
          "id": "1582750808735",
          "message": "start snapshot export",
          "start": 1582750808735,
          "status": "success",
          "end": 1582750808735
        },
        {
          "data": {
            "id": "4a7d1f0f-4bb6-ff77-58df-67dde7fa98a0",
            "isFull": false,
            "type": "SR"
          },
          "id": "1582750808736",
          "message": "export",
          "start": 1582750808736,
          "status": "pending",
          "tasks": [
            {
              "id": "1582750808751",
              "message": "transfer",
              "start": 1582750808751,
              "status": "pending"
            }
          ]
        }
      ]
    }
  ]
}

Perhaps there is something with my environment but then why it is working with older XO versions.

@tts said in Backup jobs run twice after upgrade to 5.76.2:

Can we import the config from our XO from sources to XOA or should we setup everything from scratch?

Today I got XOA trial ready and imported config from XO-from-sources. Manually started CR jobs are working. Will test it with scheduled CR next couple of days.

https://docs.xen-orchestra.com/advanced#job-manager

@gudge25 I have also CHR 6.49.13 and XO reports Management agent 6.6.80-71 detected.

Edit: can confirm OP - no management agent detected, tried back to ROS 6.47.9. Perhaps something with xcp-ng version? That CHR v6 with management agent was originally installed on xcp-ng 8.1, which is now upgraded to 8.2

@Prilly said in XO backup, is this mess made with intention?:

@karlisi Could you please elaborate why you cant use open source in production?

In short
"If you are considering using Xen Orchestra in production, please subscribe for one of our professional support plans."
https://docs.xen-orchestra.com/support#community-support

Oh, yes, this is something, I don't understand too. I feel, new things like long term retention etc. could be useful, but... OK, I'm using from sources, no support, learn to swim by yourself. And don't use in production But why by introducing completely new features, no clue in documentation how it all interacts, what goes first, what overrides.
XO perhaps needs some backups overview page, to see what will be result of all my complex backup schedules, sequences and settings.

@Ascar In XO cloud means pool, "hamburger" means host. If VM is running, it belongs to host where it runs, and receives host icon, no matter where it is kept in stopped state. If VM is stopped, it belongs to pool if kept on pool shared storage (cloud icon), or to host, if on host's local storage (hamburger).

Sometimes we want to try harder
Perhaps the confusing part is, if I go to https://xen-orchestra.com/ there is no download link. One could not realize, the download option is behind login. I'm only guessing.

@olivierlambert I believe, it is from here
https://xen-orchestra.com/docs/xoa.html#via-a-manual-xva-download

Installed AD DS role on my test Winserv2025 VM and conhost processes are appeared and already gone from 7 to 10 in about hour. In the same pool Winserv2022 AD DC VM no conhost processes at all.

WinServ 2025 on xcp-ng 8.2.1, xcp-ng tools v.8.2.2 rc1. No additional roles, except Windows Admin Center preview installed. Uptime about 2 months. No conhost processes at all.

If you need to restore one DC from VM backup, this can help
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/virtual-dc/restore-virtualized-domain-controller#restore-the-virtual-dc-with-a-vhd-file