If you create two separated jobs. One for the CR and one for the Rolling snapshot they will not interfere.

@akurzawa xo-server is not explicitly multi-processed, but it uses async IO calls in Node which should lead to multi-threaded operations. Anyway, we are currently working on reimplementing backups for the proxy and it will eventually lead to using multiple processes. These changes will at the end be merged back to xo-server as well.

Changed it to run after every 10 mins. I was missing the correct configuration. Thank you very much.

I've found two references to installed cron module version but the path differs from yours: /opt/xen-orchestra/node_modules/@xen-orchestra/cron/package.json = 1.06 /opt/xen-orchestra/@xen-orchestra/cron/package.json = 1.0.6 The upgrade itself was done using the updater from Jarli (https://github.com/Jarli01/xenorchestra_updater/blob/master/xo-update.sh) and no errors were visible during the build process. I guess it leads to errors on one of the two concurrent backup jobs because the same VM is backed up a few seconds earlier/later. Maybe this is unrelated but when starting xo-server, we noticed syslog entries about two non existent plugins (xo-server-test and xo-server-cloud) Error: Cannot find module '/usr/local/lib/node_modules/xo-server-test/dist'. Please verify that the package.json has a valid "main" entry Error: Cannot find module '/usr/local/lib/node_modules//xo-server-cloud' We can see errors relating to backups as well: 2020-02-18T20:38:56.041Z xo:xo-mixins:backups-ng WARN BackupNg#_deleteVhd /xo-vm-backups/30774025-8013-08ec-02a5-5f1bb1562072/vdis/2f07028b-aa99-49c2-ab54-2a6e5986bb01/294d9087-4583-4335-bae7-2f7fec17354d/.20200218T200141Z.vhd error: AssertionError [ERR_ASSERTION]: footer1 !== footer2 at Vhd.readHeaderAndFooter (/opt/xen-orchestra/packages/vhd-lib/src/vhd.js:161:7) at /opt/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng/index.js:1900:11 { generatedMessage: false, code: 'ERR_ASSERTION', actual: false, expected: true, operator: '==' } } [load-balancer]Execute plans! Error: no object with UUID or opaque ref: 869612ec-7f53-457d-5b83-a372a833e757

Hi, It's possible to do it using the UI, simply create a schedule with 7 as Backup retention and 2 as Replication retention.

@badrAZ thank You. In my setup during weekend I'm doing some heavy-load backup tasks, so I wanted avoid running another tasks concurently.

Just deploy XOA, register it and request a trial. You'll be automatically on Premium after an update.

Aslo You can copy a VM to the target SR

Check host logs to understand why. Maybe those VHD were attached to the control domain or something like that.

OK the tasks (it been 8 hours since I've checked) are gone, but the VHDs localted on backup server's localstorage remains. QUESTION: How to delete VHDs that are not realted to any vm? I think it will not be deleted automatically. EG. For example - I've deleted "Atlas" VM, but big atlas VHD remains on BackupHost's local storage:

Ah crap... thought I had it right this time Some time.... I've got a docker container of pi-hole running OK, just can't see it in the console anywhere. Any other options for this if core is not the way to go? Would be great to be able to manage the containers from the XOA (did I get it right?? ) dashboard. P.

@bberndt said in Create job to migrate several VMs: Tring to create a job, to schedule the migration of several VMs to another host. At the bottom, there are a couple things I don't know. There are two check boxes here for each of these: mapVdisSrs mapVifsNetworks They don't seem to do anything. What are these? Also, what goes in the box Migration Network. The name storage1, or network1 don't work. thanks. Ah! the UUID of the storage Migration network on the destination is what I need, apparently.

ok, logged into linux, su root, and tried the command on the console mount -t nfs 192.168.30.60:/mnt/Brutus/Remote /run/xo-server/mounts/86109d77-9600-48c6-b131-0ca475cd1ad4 -o vers=3 mount.nfs: requested NFS version or transport protocol is not supported tried without -o vers=3 and it worked.