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:

• one CR with enabled Rolling Snapshot which will backup your VM from XCP01 to XCP02 and will create 5 snapshots.
• two 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.

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.

@shadowdao @sccf

Hi,

This issue isn't easy to reproduce in our lab. Can you please provide a VM export with steps to reproduce this issue please?

It will help us to diagnostic the issue.

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

@goorooj said in Manual Cronjob editing Backup NG:

This is for emergency scenario, the backups on the local storage are done with snapshots.

Hi,

You can do it using the Backup NG UI. Simply click on Switch to week days located in the schedule creation modal.

Then, you can choose the days which you want the backup to be done.

Yes, to use it, the plugin need to be in the xo-server's node_modules.

@pnunn I'm sorry my bad. The plugin will work for the source version. Did you have the Audit plugin enabled in the settings/plugins ?

Hi,

The Audit logs functionality is only for users with a Premium plan. It'll not work for XO source.

We'll update the UI to mention it.

Edit: The Audit plugin works from source, only the storing of the hashes in our servers will not be available for the source version.

You're welcome.

I see, what i can suggest you is to define it per days and update the schedule each mouth until this feature request will be implemented.

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.

If you create two separated jobs. One for the CR and one for the Rolling snapshot they will not interfere.