Replacement Infrastructure. Existing Object Storage.

[mbroaders]

We will be replacing the infrastructure on a site that currently has Wasabi Object Storage as a capacity tier for the current SOBR. Copy Mode is enabled. The current plan involves building a new vCentre rather than updating and will have a new on premise hardened repository and new Veeam management server that we want to link to Wasabi also.


In this instance the VMs will have a new ID so will have full backups on premise. I assume the full backups will need to go to Wasabi again also or is it smart enough to be able to link the VMs in some other way?

[veremin]

Full backups need to be offloaded again, as there is no correlation between old and new VMs. Thanks!

[mbroaders]

Just back on this one. We have changed track here and are upgrading Vcentre and are planning on moving VMs to the new infrastructure with Veeam replicas and a planned failover.
New hardened repo will be added as an extent to the current SOBR.

Is it possible in this instance to avoid full backups going back up to Wasabi?

[veremin]

How exactly are you going to move existing VMs to the new infrastructure? The question is whether migrated VMs preserve the original identifier. Thanks!

[mbroaders]

Plan is to use Veeam to replicate then complete planned failovers of VMs so i suspect they will have new identifiers?

[veremin]

Correct, they will; adding replica VMs to existing jobs will result in an initial full backup.