Also, can you go into the directory of xo-server and show me the output of this command please:

> node -p '[require("./package").version, require("@xen-orchestra/cron/package").version]'

It would help if you could reproduce the issue with the official XOA, because we know the environment and how it was built.

Or give me a step by step process (with all the backup config) to reproduce the issue.

Cannot reproduce.

I've setup some tests, we should know more in a couple of hours.

@vapaa Can you show me the scheduling config of your job please?

This is strange, are you sure you are up to date?

You should be using at least xo-server 5.50.1 and its dependency @xen-orchestra/cron 1.0.4.

Just look at the hour of the datetime, the first one is 02:22, the second 03:22 and the last one 04:22

> xo-cli --list-objects type=message \$object=<VM UUID>

@asai said in Backup NG: "value" argument is out of bounds:

if it's helpful, I recently increased the size of the VMs disk by 40 GB.

Yep, thank you that may be relevant.

Also, you can copy in the clipboard the full backup log from the details modal of the run.

@psutty I don't see anything obvious, as @olivierlambert said, please open a support ticket for more advanced support.