Migrating to new SoBR

[fgcitig]

Hi all,

We are in the process of moving our offsite backups from AWS to Wasabi. We have successfully moved one SoBR without issue. I would like to move only some of the backup jobs from our second SoBR over to Wasabi for now.

My initial idea was to create a new SoBR that targets Wasabi and move a few of the backup copy jobs over to the new SoBR.
Keep in mind, the only thing that will change is the offsite target. I will still be doing an initial copy to a NAS on the network. My concern is if Veeam will be able to handle the SoBR changing, while the backup repo stays the same.

Would Veeam be intelligent enough to realize this is the same backup repo and continue incrementing to the same spot or would it initiate a new FULL backup resulting in the use of extra storage space on our NAS?

Cheers and thanks in advance!

[veremin]

Did I get it right that you want to:

- create a new Scale-Out Backup Repository
- add existing NAS repository as Performance Tier
- add new Wasabi repository as Capacity Tier
- point existing backup copy jobs to the new SOBR

And you are wondering whether the initial cycle of backup copy jobs will be full or incremental one?

Thanks!

[fgcitig]

That's correct.
My thought was that since the local copies are still going to be in the same place, Veeam would be able to continue to current backup chain.

[fgcitig]

Did I get it right that you want to:

- create a new Scale-Out Backup Repository
- add existing NAS repository as Performance Tier
- add new Wasabi repository as Capacity Tier
- point existing backup copy jobs to the new SOBR

And you are wondering whether the initial cycle of backup copy jobs will be full or incremental one?

Thanks!

Sorry, didn't quote you initially...but yes this is what I am trying to achieve.

[veremin]

In this case, as soon as you add the existing NAS repository as Performance Tier, the existing backup copy job (that has this NAS repository as its destination) will be automatically repointed to new Scale-Out Backup Repository, and its initial run will be incremental. Thanks!