@DustinB thanks all, the agent based backups seem to work the way we need, we removed the older alike backup appliances so fully on xoa backup now. I saw alike is going opensource but almost no activity on the github account, i expect that the product will discontinue as it is allready pretty outdated, nice chance for XOA to fill the gap.

@florent As part of the documentation updates for the backup sequencing, can we get a sequence diagram of the actual backup process? Showing what gets sent to where and in what order. Both with and without the XO Proxy.

This would help clarify a lot of the issues, I think. Right now it's not clear what connections are made by the host vs XO and to what SR.

Thanks.

@olivierlambert nope not at all. i have a feeling that it's not the disks but more like the overhead on cpu of that boxes. V3 is more lightweight.

So far this seems to work well. we will test this and inform if there is any issue with it. On behalf of my customer i would like to thank you for the quick response!

@ph7 thanks guys!

@rtjdamen NBD scales relatively well, yes.

@julien-f maybe there can we some recoverypoint endpoint? or remotes?

In the end it turned out the license was bound to the network card, we needed to recreate it with the original mac and the license server started again! Case closed!

Documented at https://xen-orchestra.com/docs/xoa.html#other-interfaces

A good specification is always better to do things correctly 🙂 (and to estimate the work needed)

@olivierlambert We observed that a VM with higher memory usage on XenServer reacts more slowly compared to VMware. This might be related to the different functioning of XenServer tools. We resized the VMs where customers had complained, and this led to significant improvements.

Additionally, we adjusted the VGA switch. While it's unclear if this had a major impact, after increasing the memory and setting the switch, we received positive feedback from the previously dissatisfied customers.

Okay then try CPU cap at 400 🙂

@rtjdamen said in Vinchin:

i run into some issues related to specific vms, most likely caused by storage issues from the host or by the backup itself. We will give that some time to experience, in the meantime i want to understand the alternatives as well.

No problem

From a high level view, it appears that there is at least some integration of the product to support XCP-ng, likely either through an agent or API call.

It's not a single pane of glass to view at the environment though, which might be irritating.

As for the product itself I can't say as I've never used it.

We are using XOA, i have tried restarting XOA but that does not resolve the issue.

You get a red exclamation mark direct when u select the virtual disk, then u reclick the disk and u get a list of partitions but it does not show the content. Maybe this first step is allready causing the issue?

Robin

@olivierlambert is it possible to apply this changes allready to our XOA? it would help with the development.

We have already a branch started with CBT (we had first to store the backup metadata outside the snapshot itself because we'll remove it with CBT). This work is now done and now Florent is directly working on CBT 🙂

@rtjdamen Copying my reply to your official support ticket (any reason for duplicating support tickets on the forum as well?):

given XOA is built on standard debian, you can assign multiple IPs to the same interface quite easily by just duplicating another "iface eth1 inet static" line. Also keep in mind XOA does not add extra interfaces under the main /etc/network/interfaces file, but in files under the /etc/network/interfaces.d/ directory. So in your case given it was eth1 you wanted a second IP on, you can add your required second IP in this file like so:

[09:43 12] xoa:~$ cat /etc/network/interfaces.d/eth1 allow-hotplug eth1 iface eth1 inet static address 192.168.1.80 netmask 255.255.255.0 #second IP iface eth1 inet static address 172.16.100.5 netmask 255.255.255.0