Would be nice to share our homelabs, might interest new users:

I'll begin:

1 pool with 2x Protectli VP6670 (64GB and 96GB RAM) (2x 10G bonded for VM network, 1x 2,5G for management network).
Both with Internal 1TB SSD as local ext4 SR, 1TB nvme for OS and SR.
NFS-SR on QNAP TBS-h574TX (10G connection) and QNAP TVS-h1288X for backups (10G connection, NFS).

2 switches:
Mikrotik CRS312-4C+8XG for 10G network
Mikrotik CRS328-24P-4S for 1G and POE

Netgate 8200 pfsense for firewall
ODROID-N2+ for HomeAssistant, Uptime Kuma moitoring

@gduperrey 1 HomeLab-Pool (via cli: yum update and reboot), 3 Business-Pools (via RPU), total 7 servers updated without issues.

@olivierlambert Master, commit fcefa: fixed!

@florent Updated.

Did a backup job: OK
Did the mirror job: OK

Great!

@Prilly Man you need to calm down. Your post(s) with shit here shit there has bad "tone".

I don't think this will get a lot of help/attention from Vates.

And they are more than helpful, even without payed support.

@olivierlambert The units are top notch!

I still have 1 FW6C 2 FW6E's (had them running proxmox before, xcp-ng after that but switched to the VP6670 because of 10G network).

NEVER ever had one single issue with them. Also bios updates are easy.

@gduperrey Updated 2 pools/2 servers @home, updated 3 pools/5 servers @ office with RPU.
All fine.

@gduperrey Installed @home and @business. RPU had no issues this time.

@john.c Will apply to business EPYC servers right away

@bleader All pools updated via RPU without issues.

Confirmed. Backups run successfully again.

@simonp NFS and S3

Updated XO to Master, commit a3139 and now the backups are failing.
Log sample:

  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "11393959-0b52-7c05-7b02-3fe6d645256d",
        "name_label": "XO"
      },
      "id": "1771281894926",
      "message": "backup VM",
      "start": 1771281894926,
      "status": "failure",
      "tasks": [
        {
          "id": "1771281894938:0",
          "message": "clean-vm",
          "start": 1771281894938,
          "status": "success",
          "end": 1771281895646,
          "result": {
            "merge": false
          }
        },
        {
          "id": "1771281897732:0",
          "message": "snapshot",
          "start": 1771281897732,
          "status": "success",
          "end": 1771281912046,
          "result": "6ab9cc35-95c2-0139-d996-7beafced8d6b"
        },
        {
          "data": {
            "id": "5f5c2608-bd80-4682-addc-dab062e9962c",
            "isFull": false,
            "type": "remote"
          },
          "id": "1771281912060",
          "message": "export",
          "start": 1771281912060,
          "status": "failure",
          "tasks": [
            {
              "id": "1771281916065",
              "message": "transfer",
              "start": 1771281916065,
              "status": "success",
              "end": 1771282018684,
              "result": {
                "size": 6650068992
              }
            },
            {
              "id": "1771282024895",
              "message": "clean-vm",
              "start": 1771282024895,
              "status": "failure",
              "tasks": [
                {
                  "id": "1771282027367",
                  "message": "merge",
                  "start": 1771282027367,
                  "status": "failure",
                  "end": 1771282031803,
                  "result": {
                    "code": "NOT_SUPPORTED",
                    "message": "Can't init vhd directory without using alias",
                    "name": "Error",
                    "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
                  }
                }
              ],
              "end": 1771282031803,
              "result": {
                "code": "NOT_SUPPORTED",
                "message": "Can't init vhd directory without using alias",
                "name": "Error",
                "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
              }
            }
          ],
          "end": 1771282031850
        }
      ],
      "infos": [
        {
          "message": "Transfer data using NBD"
        }
      ],
      "end": 1771282031856
    },
    {
      "data": {
        "type": "VM",
        "id": "fb7c36ab-2f26-b049-6fcd-2dfcabd37361",
        "name_label": "Windows 11"
      },
      "id": "1771281894928",
      "message": "backup VM",
      "start": 1771281894928,
      "status": "failure",
      "tasks": [
        {
          "id": "1771281894938",
          "message": "clean-vm",
          "start": 1771281894938,
          "status": "success",
          "end": 1771281895970,
          "result": {
            "merge": false
          }
        },
        {
          "id": "1771281897733",
          "message": "snapshot",
          "start": 1771281897733,
          "status": "success",
          "end": 1771281898773,
          "result": "3ce54f0c-8fa4-d71f-7693-8cf0c5c5a004"
        },
        {
          "data": {
            "id": "5f5c2608-bd80-4682-addc-dab062e9962c",
            "isFull": true,
            "type": "remote"
          },
          "id": "1771281898774",
          "message": "export",
          "start": 1771281898774,
          "status": "failure",
          "tasks": [
            {
              "id": "1771281900165",
              "message": "transfer",
              "start": 1771281900165,
              "status": "success",
              "end": 1771282339491,
              "result": {
                "size": 68675436544
              }
            },
            {
              "id": "1771282341068",
              "message": "clean-vm",
              "start": 1771282341068,
              "status": "failure",
              "tasks": [
                {
                  "id": "1771282341203",
                  "message": "merge",
                  "start": 1771282341203,
                  "status": "failure",
                  "end": 1771282345026,
                  "result": {
                    "code": "NOT_SUPPORTED",
                    "message": "Can't init vhd directory without using alias",
                    "name": "Error",
                    "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
                  }
                }
              ],
              "end": 1771282345026,
              "result": {
                "code": "NOT_SUPPORTED",
                "message": "Can't init vhd directory without using alias",
                "name": "Error",
                "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
              }
            }
          ],
          "end": 1771282345027
        }
      ],
      "infos": [
        {
          "message": "Transfer data using NBD"
        }
      ],

reverting back to commit a3139 and all is well again

Answering myself:

@dinhngtu downloaded on a windows server 2022, extracted and did the inf install. No visual feedback.
How do I know it was installed?

@Greg_E You've got a point, actually several.

The scripts exist for a reason because the official way is way to complicated. I still use them, having converted to xcpng @home (scripts) and @business 3 yrs ago.

There should be an official script, definitely. So all are on the same page. They have nothing to loose, everything to gain! The more people use it the better and having a simple way to officially install XO would help that.

Regarding XO6, I don't personally like it at all, mainly because I have to hunt around to find stuff, where in XO5 it's already automatic (not talking about missing features which revert us to XO5).
I actually don't like the UI, it is cramped especially on smaller laptop screens... But this is a personal preference.....

@gduperrey updated 2 hosts @home. 5 @office.
Had to run yum clean metadata ; yum update on cli (cancelling to run RPU in XO) for updates to appear.

Also here the task progression can't be followed (stays at 0% until completed):

instead of

As shown above the evacuation tasks are not shown.
The last steps migrating thre VM's to the original place are shown:

Just did my RPU and checked on the new v6 interface.
The old one has task details that are missing on the new one (or I didn't find them:

I like to see the evacuation tasks happening (in the past I could identify hangs etc)

Here instead of the ID of the VM host the real names should be shown: