Thank you for your report.
The bug is introduced by the recent version of a library that we are using.
We'll fix it ASAP.
This error can be triggered on parsing a non-JSON data by using
Please install xo-cli and give me the resulted file of the bellow command.
xo-cli backupNg.getAllLogs ndjson=json:true @=<outputFilePath>
@s-pam said in Multiple remotes in a backup - how is retention calculated:
OK Great. So if I set retention to 10, it would keep 10 copies on each remote?
Yes. it will keep 10 copies on each remote.
The backups' retention is specific to schedules. So, the schedule's retention is applied to all backup job's remotes.
@nodesocket Did you previously canceled a VM export? This can be linked to this issue https://github.com/vatesfr/xen-orchestra/issues/5535.
Please restart your
xo-server to see if it resolves your issue.
Remotes and SRs aren't managed the same way by XO.
XO is connected directly to the remotes to do some read/write operations, unlike SRs which is connected to them via XCP-ng.
So the SRs aren't directly managed by XO, but are managed using the XCP-ngs' XAPI and we are limited to what the XAPI provides as information.
Audit logs aren't in the same location than the
To get Audit logs you can use this command
xo-cli audit.getRecords which returns an array of records.
This command has an option
ndjson, which allows you to export logs in a
xo-cli audit.getRecords ndjson="json:true" @=<outputPath>
Currently, there is no way to add a predicate to the job execution.
But, it's possible to do a work-around that responds to your need using
xo-cli and your
You can let your
cron run manually the backup job using
xo-cli backupNg.runJob id:jobId schedule:scheduleId.
Unfortunately, there is an exception in cron when the
day of week and the
day of month are set together.
if both "day of month" and "day of week" are restricted (not "*"), then one or both must match the current day
So, we have no way to tell cron to execute a backup job each Sunday of the first week of the month.