Team - Storage group | XCP-ng and XO forum

florent

so that is probably only a off by one error in the task code
Thanks andrew

florent

@ndrew nice catch andrew I will look into it
is it keeping disk attached to dom0 ? (in dashboard -> health )

florent

@cHenry xo-cli backupNg.getLogs --json limit='json:500' should work ( the command line parameter are considered as string )

florent

@keven we don't have ( for now) the feature to create bucket directly from XO. Also I think it is more secure if XO don't know at all the credits of the bucket admin

florent

@atapaltes hi, I do think we didnt handle this case.
To be fair, the sheer breadth of the capabilities of vmware is always impressive

Would you be able to show us the VM metadata (especially the .vmx and .vmsd ) to see how we can detect them ? We'll probably won't be able to read this snapshot data for now, so we'll have to at least document a reliable process

On the fast clone side : did you try the checkbox on the bottom (fast clone) ? It should be pretty fast since no data are copied.
On the native snapshot side : I now it's on our roadmap, bu can't give you ETA

florent

@mpr there is a high chance that we improve the scheduler , so maybe be able to plan more precisely when the full occurs, but we will always keep one full backup as the beginning of the chain

You can mitigate the risk on infinite schedule by using health check : restoring the backup automatically after the job, this ensure that , at the time of backup, the files are correct, and that if an issue occurs in the backup you can start a new chain, thus detecting a backup storage issue before needed it after having a production issue

dthenot

For people testing the QCOW2 preview, please be informed that you need to update with the QCOW2 repo enabled, if you install the new non QCOW2 version, you risk QCOW2 VDI being dropped from XAPI database until you have installed it and re-scanned the SR.
Dropping from XAPI means losing name-label, description and worse, the links to a VM for these VDI.
There should be a blktap, sm and sm-fairlock update of the same version as above in the QCOW2 repo.

If you have correctly added the QCOW2 repo linked here: https://xcp-ng.org/forum/post/90287

You can update like this:

yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-qcow2
yum update --enablerepo=xcp-ng-testing,xcp-ng-qcow2
reboot

Versions:

blktap: 3.55.4-1.1.0.qcow2.1.xcpng8.3
sm: 3.2.12-3.1.0.qcow2.1.xcpng8.3

Team - Storage

Posts

Versions:

Member List