@olivierlambert about local mount vs xo nfs. i made new tests, XO implementation works not worse than native. That really good result.

local nfs
Size: 5.98 GiB
Speed: 70.76 MiB/s - 81.33 MiB/s

xo nfs
Size: 5.98 GiB
Speed: 79.01 MiB/s - 82.22 MiB/s

yes i understand, just a interesting solution.

@florent said in Import from VMware:

@Olest
that's a nice catch, every day I discover new limits of the vmware licensing . At least we could catch the error and show something useful to the user

Just wait, everything free from VMWare is going away, so it'll just be the assumption that if you should be able to do it, you won't be able to.

@Danp said in VM import:

m pode ser devido a nenhum servidor definido/habilitado em C

It worked out, I added my xcp-ng to servers. Thanks xD

I have no idea why or how it's fixed 😆 But at least it is, so good news 🙂

@mestafin XOA/XO is an appliance with a web UI that should run as bare-metal or virtualized instance. It is a multi user management solution, that can handle different pools and user. Backup of a VM allows for easy restore. No need to install it on a notebook.

Hi!

The issue should be resolved on the branch fix-smb-storage

@gskger works thanks

This will be done in XO 6 and XO Lite, not XO 5.

@julien-f @olivierlambert That fix it. Thanks guys

@Danp said in Backup Error: "302 Found":

@DustinB You could try the same backup job using XOA. If that works correctly, then that would eliminate some of the environmental causes.

Got it sorted out, and addressed a speed issue I was experiencing.

The advanced options of the pool, I had set ETH1 as the backup network, which for some reason keeps falling back to 10FDx and is generally just bad.

Undid that change as well as moved my XO over to a different vNIC which appears to have addressed the issues.

Alright I updated XO again and the problem is gone.
I would just like to comment that unlike described by another user that was only happening on single-node installs, this was happening to me in 2 out 4 nodes in a cluster. Two hosts would show normal, and another two showed glitched.

Anyway, SOLVED!

I'm talking about VM snapshots (and by transitivity, VDI snapshots). Retention is the number of backup you save on the backup repository, and it's totally unrelated to the number of snapshots when doing full or incremental backups.

The code is entirely open source. It's just that the deploy is exposed in the XOA UI 🙂

@Hannes_5253 No, my mistake.... I think it was this post. (off buy a digit... 8117 vs 8177)

Of real RAM usage? Eg with htop, take care of the cache too, because even if the cache is used doesn't mean it's really important. Maybe 8GiB is enough for example.

Nothing like that could happen. If your orphaned VDI is in use, it will error out with "VDI in use".

You are welcome, thanks for the feedback 🙂

@olivierlambert I can do it pretty easily, but there may be a good reason for XAPI to throw this error instead.

I second 4 being a good sweet spot, I personally have seen very little improvement from going higher than 4 in my environments.