How would one migrate/move from AWS S3 to Wasabi ?

[lrhazi]

For many months now, we have been using S3 as capacity tier, copying all backups as soon as they are created to an S3 bucket, with object locking enabled...

If we were to move to Wasabi, or I guess any other vendor for that matter, what would the process be like?
Would we need to crate new SOBR and start moving backup jobs to it? Would migrating existing backups be something to consider?

Thanks,
Mohamed.

[dalbertson]

The most cost effective solution would be to create a new sobr and start new backups going to it.

There are services that will move the data to wasabi for you but it costs.

Also pulling the data down to vbr and then to wasabi costs.

Just start fresh and let the old backups age out.

[vtjim345]

What mechanism would age out the old SOBR if the new SOBR is referenced by the backup job?

I have a similar issue where the size of the wasabi bucket was > 100 TB with some performance problems. We removed the original wasabi bucket from the SOBR and put a new wasabi bucket in the SOBR but i don't see what would be aging out the original bucket now.

[Gostev]

This requires V11, where GFS backups retention is processed independently of the job as a background process.
Once they all age out, you'd need to delete the remaining (recent) backups manually.

[Dima P.]

Just wanted to note that with Veeam Backup & Replication V12 or later such migration between primary repositories is a child's play: you just use the Move feature to migrate your backups from one repository to another. Thank you!