Hi,

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.

@mauzilla

Indeed, all backups are independent. Each execution results on a backup and only removes its created backups regarding the retention.

For the third point, you want to backup VMs using a live ISO? What do you expect as backup behavior? Thank you

Hi @mauzilla

1. Job's schedules backup all VMs, so, you need to create two jobs to do that.
2. Backups are executed in parallel, so you need to distance their executions to ensure that they will not overload your NFS remote.

Hi,

This error can be triggered on parsing a non-JSON data by using JSON.parse() or JSON.parse('u').

Please install xo-cli and give me the resulted file of the bellow command.

xo-cli backupNg.getAllLogs ndjson=json:true @=<outputFilePath>

Hi @xo-g ,

We don't use any specific order to pick the VMs to backup.

@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.

Hi @S-Pam

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.

badrAZ created this issue in vatesfr/xen-orchestra

closed [VM/Snapshot] Export via browser #5535

@nodesocket Hi,

Can you check how many parallel VMs can you export in this configuration /etc/xo-server/config.toml? Did you canceled an export before?

Thank you

@tarkh

Please give me the resulted file of this command:

wget http://<user>:<password>@<host>/rrd_updates?interval=5\&json=true\&start=$(($(date +%s) - 595))

Hi @tarkh

To see what values XAPI RRDs returns, you can use this xo-cli command:

xo-cli host.stats host=<hostUuid>

Hi,

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.

Hi,

Audit logs aren't in the same location than the xo-server logs.

To get Audit logs you can use this command xo-cli audit.getRecords which returns an array of records.

xo-cli audit.getRecords

This command has an option ndjson, which allows you to export logs in a ndjson format.

xo-cli audit.getRecords ndjson="json:true" @=<outputPath>

Hi,

Currently, it's not possible to export logs into a remote, but you can export them locally on clicking on the button Download records.

Hi,

For the first question, you can use cpusMax to set the CPUs limit. xo-cli vm.create cpus=2 cpusMax=4

Yes, backup jobs require attached schedules to be executed properly.

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 cron.

You can let your cron run manually the backup job using xo-cli backupNg.runJob id:jobId schedule:scheduleId.

Hi @pianon

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
https://en.wikipedia.org/wiki/Cron

So, we have no way to tell cron to execute a backup job each Sunday of the first week of the month.

These VDI-snapshots are linked to the snapshots with memory created by the delta backup. They shouldn't be listed here.

There is the dedicated github issue. Please follow it to get its evolution.