@aqua-calc The problem is fixed. The XO server was missing NFS utils:

sudo apt install nfs-common

Thank you everyone for responding!

@Danp There were no entries regarding backup listed by the journalctl command for the target backup time.

I've updated my XO to commit 16498, and restarted the XO VM. The backup ran ok Today.

Thank you @DustinB and @Danp for responding to my post!
Alex

@Danp The log is empty -- no messages. I've changed the schedule to run at a different time -- waiting to hit that time...

@DustinB Not every minute, but only at 1:00AM of every Monday, Tuesday, Wednesday, Thursday, and Friday.

And no, the job is not running.

Also, I have the same schedule for my Pool Metadata and XO Config backups, which are get started and run successfully.

Hello,

I've setup and scheduled full VMs, XO config, and pool metadata backups.

Pool metadata and XO config backups were started automatically and run successfully.

VMs backup does not start automatically. When started manually, the VMs backup runs successfully.
The screenshot is uploaded in my next post.

Why the backups are not being started?
How to diagnose the failure of XO to start the backup automatically?

Thank you,
Alex.

@julien-f Any plan to introduce an ability to schedule monthly backups on a specific day of the week?

@DustinB Can we have something like this, for instance:
Run monthly backup on 1st Sunday of each month at 5:00AM

0 5 * * 7 [ $(date +\%d) -le 07 ]

@aqua-calc The problem is fixed. The XO server was missing NFS utils:

sudo apt install nfs-common

Thank you everyone for responding!

@gskger I've tried both -- the same result:

{
  "shortMessage": "Command failed with exit code 32: mount -o  -t nfs 192.168.1.200:/volume1/backup-xo/backup /run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279",
  "command": "mount -o  -t nfs 192.168.1.200:/volume1/backup-xo/backup /run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279",
  "escapedCommand": "mount -o \"\" -t nfs \"192.168.1.200:/volume1/backup-xo/backup\" \"/run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279\"",
  "exitCode": 32,
  "stdout": "",
  "stderr": "mount: /run/xo-server/mounts/813d5bc2-aaaf-4c9f-8841-64eebad52279: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.",
  "failed": true,
  "timedOut": false,
  "isCanceled": false,
  "killed": false
}

@AtaxyaNetwork XO from sources