@Forza Actually not all is lost. I have off site backups, so I could restore the backup target remote from it's off site backup.

I'm wondering if I power off XO, then restore the contents of the directory where my backup target remote points to, will XO then be able to see the old backups, before they were wiped? Or, will it be very confused because it's metadata is not stored on the remote but rather on the XO VM.

Hello, so I screwed up. I was playing with backups and I wanted to see if I can do a manual backup (triggered by me, no schedule). Well apparently this is not sported. I realized this after I deleted the schedule and the backup job would not save, saying I need a schedule. So I created a (default) schedule and then disabled it. I then manually triggered the backup to test this approach. Of course the backup went through just fine. Soon after I realized that I messed things up good. The default backup schedule defaults to only retaining one copy. My half a dozen previous backups have now been automatically removed. The problem is I need my first backup in case I want to start over working on my VM. Well, that gone now

I get that I caused this myself. I'm wondering if a function for manually triggered backups without deleting any previous backups can be added.

My use case is as follows. You start working on a new VM, you get the basic setup done. Now I want to be able to get back to this point at any time should the changes I make next not work out so I'd like to trigger a manual backup. Next few weeks are keeping me busy with other work. I finally come back to what I started earlier and continue my configuration. In the next few days I realize that what I have done is not going to work. At this point I would like to simply restore my first backup that already has the basic configuration done and I can go for attempt two.

I guess another way of saying this is I would like to tag certain backups as protected so that they will never be erased automatically to reclaim storage space. Does anyone agree that this would be useful?

Cheers.

@thenorthernlight Thanks! It appears I had two problems with the configuration I posted earlier that were causing the Test plugin to fail:

Use StartTLS should be off
User filter should be (userPrincipalName={{name}})

Now onto testing if actual AD logons are working.

Cheers.

Well, if the software and support are poor, than maybe different vendor is best.

I found this: https://www.digi.com/products/networking/infrastructure-management/usb-connectivity/usb-over-ip/anywhereusb

Not cheap but they mention "virtualization" and "software license key fob" in their marketing blurb.

I would prefer a cheaper USB 2.0 version as I don't need the speed of USB 3.1.

It would be great to hear what brands/products people are successful using for this. I have no experience with this technology.

Re: Attaching USB storage via XOA

I'm trying to use XCP-ng and Xen for software testing. I have software that uses Thales USB licensing dongles (to use software, you need a hardware dongle attached).

I have been following instructions on here mostly: [XCP-ng USB Passthrough(https://www.techtutorials.tv/sections/xcp-ng/xcp-ng-usb-passthrough/) I have been able to get it to work.

My concern is that there may be problems down the road. Apparently, the pass through does not survive Xcp-ng host reboot. I also read that USB pass though interferes with snapshots and backups.

Could someone elaborate what additional constraints USB pass though brings to snapshots and backups? Does it matter if I'm passing though an actual USB device rather than a USB flash drive?

I would like to +1 on more love for USB pass through in Xcp-ng and Xen Orchestra.

I just tried to reproduce the issue on Debian 11, and guess what, the issue DID manifest its self on Debian as well.

kajetan@debian:~$ sudo mount -v -t nfs -o vers=4.1 optinas1:/volume1/test_nfs_share /var/test_nfs_share/
mount.nfs: timeout set for Tue Aug 30 16:33:58 2022
mount.nfs: trying text-based options 'vers=4.1,addr=172.22.1.49,clientaddr=172.22.1.100'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting optinas1:/volume1/test_nfs_share

Moments later I executed the same command on pop!_os
code_text:

kajetan@pop-os:~$ sudo mount -v -t nfs -o vers=4.1 optinas1:/volume1/test_nfs_share /var/test_nfs_share/
mount.nfs: timeout set for Tue Aug 30 16:33:32 2022
mount.nfs: trying text-based options 'vers=4.1,addr=172.22.1.49,clientaddr=172.22.1.51'
kajetan@pop-os:~$

And the mount worked fine. It looks to me like somewhere along the chain (Debian -> Ubuntu -> Pop!_os) the issue got fixed. And yes, I did apply

apt-get update && apt-get upgrade

to the Debian box.

@olivierlambert Oh, I was just referring to all the software that is needed for NFS to work.

@Andrew Hello Andrew, yes this is XO Source. Thank you for the clarification, I did not know who is "responsible" for the "NFS bits". Maybe I should try with Debian 11 and report back my findings.

@Darkbeldin So the min:8G/max:28G and 4/16 is for the static memory settings and leave Dynamic disabled?

It's more important for me that the RAM utilization is optomized than being able to live migrate the VMs (for these particular VMs).

Run a backup of a VM in XO to a remote NFS share on a Synology device A.
Use Synology’s Hyper Backup to back the NFS share folder on Synology A device onto another Synology device B
Power down XO.
Delete the folder on Synology A that contained XO’s backup (simulating losing our XO backups).
Restore the backup folder on Synology A from Hyper Backups stored on Synology device B.
Power up XO VM and check on the status of NFS remotes: all remotes on Synology A are off line.

Log shows:

Command failed with exit code 32: mount -o  -t nfs optinas1:/volume1/test_nfs_share /run/xo-server/mounts/c9966433-081a-4d59-b109-3dbe9b054ad4
mount.nfs: access denied by server while mounting optinas1:/volume1/test_nfs_share

However, executing:

sudo mount -t nfs optinas1:/volume1/test_nfs_share /var/test_nfs_share

on a POP!_OS VM is successful. (POP!_OS is a Ubuntu variant)

Now, ssh to XO and execute:

sudo mount -v -t nfs optinas1:/volume1/test_nfs_share /run/xo-server/mounts/c9966433-081a-4d59-b109-3dbe9b054ad4

Gives:

mount.nfs: timeout set for Fri Aug 26 17:29:08 2022
mount.nfs: trying text-based options 'vers=4.2,addr=172.22.1.49,clientaddr=172.22.1.42'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting optinas1:/volume1/test_nfs_share

After restarting the NFS service on Synology A and executing on XO:

xo@xo-ce:~$ sudo mount -v -t nfs optinas1:/volume1/test_nfs_share /run/xo-server/mounts/c9966433-081a-4d59-b109-3dbe9b054ad4
mount.nfs: timeout set for Fri Aug 26 17:41:49 2022
mount.nfs: trying text-based options 'vers=4.2,addr=172.22.1.49,clientaddr=172.22.1.42'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=172.22.1.49,clientaddr=172.22.1.42'
xo@xo-ce:~$

The NFS shares work just fine now.

Maybe the NFS components in XO are a bit out of date?

I'm using: Xen Orchestra, commit 82452
xo-server 5.98.1, xo-web 5.100.0

Hello, I'm having difficulties understanding how to provision RAM to VMs.

I want to be able to have two scenarios. Scenario one: One VM is offered almost all the available RAM on the host. Scenario two: I want to have two VMs running, each getting 50% of memory and CPU resources available on host.

It would be nice to be able to switch from scenario one to scenario two without rebooting VMs. Equally nice, it would be to start with scenario two, then shut down one VM and have the system switch to scenario one.

Both VMs will be running Windows 10 Pro.

It seems dynamic memory has issues and have been deprecated.

Let's say my host has 32GB of RAM. If I create two VMs with minimum memory of 16GB and maximum of 32GB, would this satisfy my requirements? Assuming no other VMs are running on the host, will starting one VM cover scenario 1 and then when starting the second VM, the hypervisor will claw back half of the RAM from VM one and assign it to VM two, covering scenario 2?