Moving your capacity teir from AWS to Azure

[jcofin13]

WE ave AWS currently added to our SOBR.

IF we want to "switch" to Azure once it supports immutable storage what is the best way to move the data from one platform to another?

https://helpcenter.veeam.com/docs/backu ... ml?ver=110

"If a performance extent is unable to accommodate data being copied due to lack of free storage space, Veeam Backup & Replication will find another extent in the associated scale-out backup repository that has sufficient storage capacity to receive the data. If your scale-out backup repository has no performance extents other than the one running out of space, the copy will not be possible."


As this says if you dont have enough space locally to accept in all that data from AWS on your current local repo you cant download it in order to "move it" to azure. This makes total sense.

WE certainly dont have that kind of space locally to do that. Would the best plan of action be to add the azure capacity tier to veeam and the existing SOBR and just "seal" the AWS extents until the required retention is met in Azure over time?

[HannesK]

Hello,
the question sounds irrelevant for V11 (because V11 does not support immutability on Azure), so what I write right now might change depending on how V12 development goes.

Only same kind (S3 & S3, AWS S3 & AWS S3, Azure & Azure) of object storage can be added together in capacity tier in V12 (in V11, you can only add one object storage to SOBR capacity tier). So Azure & AWS cannot be added to the same capacity tier. That means you can keep Azure as standalone repository. Sealing in a new SOBR is optional and not required. I recommend to wait what V12 brings, there might even be another way, but that's not certain yet.

Best regards,
Hannes