XO Team group | XCP-ng and XO forum

pierrebrunet

@johnnezero You can use the docs directly in /rest/v0/docs. You just have to connect and fill in the uuid you need. It will work

mpiton

@jr-m4

Hi, your journalctl output has the answer: vectura: data plane: could not connect: timed out.

With a vCenter as source, the login and the CBT query go through the vCenter on port 443, but the disk itself is read directly from the ESXi host running the VM, on port 902. Your new XO reaches the vCenter fine, it just can't open a connection to that ESXi on 902. The stream has ended without data error is only the side effect of vectura exiting. CBT has nothing to do with it.

The old instance works because it can reach that host (VDDK needed the same port). I'd check firewall/VLAN rules or DNS on the new VM. From the new XO, using the ESXi name as vCenter shows it for that VM:

  getent hosts <esxi-host>
  nc -vz -w 5 <esxi-host> 902

and compare with the old instance.

~Mathieu

pierrebrunet

@johnnezero Hi,
Sorry, it seems it is only in Rest API for now:
You can check it here:

<xoa-url>/rest/v0/docs/#/backup-repositories/ReclaimSpaceBackupRepository

MathieuRA

Issue identified.

@spelon If you're using XO from source, you can try this mra-fix-undici-xen-api branch, otherwise, feel free to open a tunnel so I can fix your XOA.

pierrebrunet

@johnnezero It just came out with the release... now
Just one thing, you may have empty directories even after the reclaimSpace task but they should be empty

MathieuRA

@acebmxer If you can open a support ticket with a tunnel, it would be nice. I am not able to reproduce in my lab nether on our QA lab

MathieuRA

Hello, thank you. I'm taking a look at it.

pierrebrunet

@henri9813 Hi,
There should be a new "reclaimSpace" in next release which help you to clean repositories.

Just to let you know, we prefer to not remove orphan backups in case a VM removal is accidental and you want to bring back it from a backup repository

JorisK

Wonderful !

julienXOvates

@jacob.becker said:

Hi!
In XO-5 you can see clearly if a host is in maintenace mode" or not. I'm missing a similar thing to the little green/gray dot from XO-5 in the XO6 treeview.
You can see it in the System- Tab under General Information, but only if the host is already selected.

I personally find it difficult to distinct between hosts and VMs in the treeview if a large amount entries are shown. Especially while scrolling.

Hi @jacob.becker, this is going to be fixed in XO 6.9 (ie. the Disable state for a host).
I share your point of view about hosts & VM icons, we should also change them.
Thanks !

XO Team

Posts

Member List