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.

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.

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.

If you wan't your CR to be done in the same time with the Rolling snapshot you only need one schedule with 5 as Replication retention and 5 as Snapshot retention.

If you want them to be executed in different time better create two jobs instead of two schedules because it have a known issue with this case which the patch will be released soon.

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.

Indeed,

On selecting a SR, the user should be able to select the associated network and to choose its configuration.

Unfortunately, it will not be possible to give an IP address to the deployed VM during the deployment process because the VM is started quickly.

Indeed, in your case you need to give the VM an IP address.

To make this possible, we'll improve our solution to let users be able to select the VM's network and to choose the network configuration.