Hi,
For the first question, you can use cpusMax
to set the CPUs limit. xo-cli vm.create cpus=2 cpusMax=4
Hi,
For the first question, you can use cpusMax
to set the CPUs limit. xo-cli vm.create cpus=2 cpusMax=4
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
.
@Anonabhar It seems that the property snapshot-of
isn't correctly reported by XO
. Did you tried to disconnect/reconnect the server containing this snapshot to see if it resolves your issue?
And please give me the version of your xo-server
.
Hi,
Thank you for your report.
Indeed, there is an issue with the display of Disk (Used/Total)
.
The fix for this issue is under validation, it will be merged ASAP.
@pdonias Indeed, it's related to the audit changes.
@cocoon Thank you for your report.
I've just created a PR on Github which fix this issue.
Please follow it to get it's evolution. Feel free to test it and give us your feedback.
Thank you!
Hi,
Unfortunately, it's not possible to do it. You can only define days which the backup will be executed or a days of the week without week interval.
I've created a feature request on Github. Please follow it to get its evolution.
The CR
is a functionality which exports the VM
at the first time then it exports only the diff for optimization.
This functionality needs a snapshot to be kept on the VM
. Unfortunately when a job contains two schedules which one is for CR
, one schedule will delete the snapshot created by the CR
then the CR
will always export the full VM
instead of the diffs.
Hi,
For your first question, created snapshots will not interfere with the CR
.
For your last question, by design and performance, you can' t set one CR
for rotating servers.
So, you need:
CR
with enabled Rolling Snapshot
which will backup your VM
from XCP01
to XCP02
and will create 5 snapshots.CRs
one will backup your VM
from XCP01
to B01
and the second will backup it from XCP01
to B02
. These jobs will create 2 snapshots.Total snapshots created by these jobs: 7
Hi,
It's possible to do it using the UI, simply create a schedule with 7 as Backup retention
and 2 as Replication retention
.
Thank you. The fix for this issue was merged today. Please pull and build your XO.
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.