Double CR backup

[ph7]

@pilow
https://xen-orchestra.com/blog/xen-orchestra-6-2/

[Pilow]

@ph7

still not clear what it does
"one backup archive of each VM"... on first remote ? on second ? alternatively ?

[Pilow]

haaaaaaaaaa

perhaps if you have 4 VMs in the backup job, it will put 2 VMs on first remote, and 2 other in second remote...

[ph7]

@Pilow RTFM

The system spreads data intelligently across the pool. It prioritizes available capacity, while keeping incremental chains consistent.

[flakpyro]

My understanding is this should only be happening during backups, not a CR run though.

[DustinB]

https://xen-orchestra.com/blog/xen-orchestra-6-2/

In the above blog posting this feature is explained that @ph7 referenced.

[DustinB]

@flakpyro said:

My understanding is this should only be happening during backups, not a CR run though.

CR is a form of backup.

[Tristis Oris]

@ph7 i have 3)

still don't get anything.

[ph7]

@Tristis-Oris
weird

[DustinB]

@Pilow said:

@ph7

still not clear what it does
"one backup archive of each VM"... on first remote ? on second ? alternatively ?

You get to add multiple backup repo's to your XO instance, if your backup SR becomes full, XO starts using the second, third etc storage repo so you don't have to lift and shift your backups.

[Tristis Oris]

@DustinB but this is impossible scenario. CR requried a VM SR, not a backup one) weird option.

[DustinB]

@Tristis-Oris said:

@DustinB but this is impossible scenario. CR requried a VM SR, not a backup one) weird option.

You're still replicating a VM to a storage repository.

Maybe the system will allow you to create a more flexible CR job using different hosts, rather than 1:1 . . . ?

[ph7]

@Tristis-Oris You are correct
It doesn't work in a CR

[ph7]

@olivierlambert
It did say replication in the blog post

[olivierlambert]

Ping @Team-XO-Backend