@andreas Hi Andreas,

After testing it on my side i can confirm i reproduce the issue.
I will discuss it at dev level and get back to you.

Yes, you can do that on your user settings.

Click the user button, down left on the toolbar, and in the settings set your default filter to none:

@pierre-briec I'm happy it's solved, and happy i was right

Have you tried restarting the toolstack for the host could clear a bad VM state?

@pctechs Hi,
This is one of our next feature, no timeframe at the moment but it's coming soon.

It's seems I'm able to reproduce the issue with OVA i'm unable to export without an error.

@olivierlambert Trying it now I keep you updated

@vbits said in Delta backup fails on SMB remote:

NexentaStor SC216

Yes that was the question If you have better speed with SMB stay with it NFS should be better in theory but sometime you have to go with real world reality.

@northportio Please could you try this and report back:

create this file /etc/xo-server/config.httpInactivityTimeout.toml:

# XOA Support - Work-around HTTP timeout issue during backups
[xapiOptions]
httpInactivityTimeout = 1800000 # 30 mins

And rerun the backup job.

@andrewreid XO team has released a new version 5.66.2 for XOA and new sources for the XO community that should fix most of the recent backup issue, so please update to latest and report back if needed.

@KPS Hi,
I don't think it's possible but I could be wrong perhaps an advance filter could do that.

@geep87 Installing 2022 on XCP is not a problem, in your case most probably the issue is with the ISO you are using that is dell server specific imho.

@toragmichael Hi,
First you don't have only one VM on your host, you also have your dom0 that is running there.
Second on one side you have virtual CPU attach to a VM on the other you have the physical CPU attached to the hardware so not having the sale result is quit normal.
Still 37% usage for one VM is quit a lot, mostly I think you are using your host heavily.
For the performance part I'm really not sure without testing it trying to push your host further could result in better or worth perf because an hypervisor is not really optimise to run only one VM but more to share the ressources between VMs.

@damjank

@damjank If I remember correctly you just need to restart your xo-server to solve this.
On your XOA VM systemctl restart xo-server.
Are you also sure your host as been restarted after update?

@jsauve Jacques, Yes Vates is a French firm we are Xen orchestra developers and also XCP-ng developers and we provide pro support for XOA and XCP-ng. you can find our main website here: https://vates.fr/
For the loading time it's really difficult to say, this kind of infrastructure don't come handy for testing ;). It could also depend on the connections between the host and the main XOA, how much load the XOA is under, how many users are connected at the same time, how much ressources you have allocated to the XOA VM. Really hard to give you accurate metrics.
No if you have more than one XOA you will have to connect to each one to manage the part of the infrastructure linked to the XOA connected to it.

@jsauve Hi Jacques,

Hosts number is one thing but the number of VMs is also a very important one, at the moment the main issue with infrastructure this size is that all the infos are loaded during the first connection so yes if you have a very big infra with a lot of VMs you can see loading time increase with XOA.
So yes your idea of splitting the load between two or three VM can be a good idea but we are also hoping to be able to manage this kind of bigger infra with XOA 6 when it will come out.
I recommend you contact our team directly at help@vates.fr to see how we can help

@nickdsl Best way to go would be to update to 8.2.1 first and see if you still see the issue.

@gduperrey My host asked for a reboot yesterday after patching IIRC but I could be wrong.

@eoin Asking @stormi or @gduperrey if it's possible but mostly you should suppose it's mandatory