How to move backups between different S3 (blob) providers and different Veeam B&R servers?

[rjv1971]

I have Veeam B&R server1, with a SOBR repo, the capacity extend going to Azure. i have a Veeam B&R server 2, with a SOBR repo, with the capacity tier going to Wasabi.

What is the best way of getting the backups going to Azure on Veeam server 1 to Wasabi on Veeam server 2? Goal is to eventually decommission server 1.

I can recreate the backup and backup copy jobs on server 2, so then point forward, it will use Wasabi. But how will I get the existing historical backups in Azure on server 1 to Wasabi on Veeam server 2?

[oleg.feoktistov]

Hi Ron,

Currently I see two options with your scenario.

Option 1

On VBR server 1:
1. Download data from Azure Blob capacity to a performance tier.
2. Evacuate backups from one of the performance extens to another (if it's more than 1 of them).
3. Remove performance extent you moved your backups to from the SOBR or delete the SOBR completely.

On VBR server 2:
4. Add the repository with backups you downloaded to VBR server 2.
5. Add this repo as a performance tier to the SOBR 2 (the one with Wasabi).
6. Upload data to SOBR capacity manually (since the backups will be considered imported).
6a. Or [urlhttps://helpcenter.veeam.com/docs/backup/vsphere/backup_job_storage_vm.html?ver=120]map the backups[/url] you imported to the job that targets your SOBR with wasabi. In that case backups will not be considered imported anymore and will be offloaded to capacity tier automatically.

Option 2

DISCLAIMER
I'm mentioning it as an option but according to our QA tests, a lot of things can go wrong using this approach. And since migration will be happening outside VBR management, we will not be able to assist in case of migration issues. Also, this way is not applicable to immutable data.

Direct migration from Azure to Wasabi using 3rd party tools. In this case you will need to re-add performance repos and rescan the whole SOBR.

Coming in vNext:

Option 3

You will be able to perform an inter-vendor backup migration in scope of one capacity tier given that the extent you want to migrate backups from is in inactive state (sealed, maintenance).

If you are not restricted in time with decommission process, I'd say Option 3 would be the best for you scenario.


Best regards,
Oleg

[chrisWasabi]

You can move it with WCSM

https://wasabi.com/cloud-object-storage ... nc-manager

[rjv1971]

Follow up question on this topic:

When would option 3 be available?

Other question:
I am trying to move backups from a SOBR with Azure as the capacity tier to a SOBR/ regular repository using Wasabi. The target doesn't even have to be a SOBR, it could just be a Wasabi Object storage repository.

Option 1 mentioned above; it would require to move every backup in the Azure Capacity tier to the on-prem performance tier. I do not have that kind of on-prem capacity laying around.

On many of the backup-copy backups I have, I do not have the 'copy/move' option available as per this article: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

I see this option (provided by Wasabi) https://docs.wasabi.com/docs/how-do-i-m ... -to-wasabi
BUT.. the backup copy jobs I want to move do not show up in the list where I add jobs (step 3) even though I can see them in the B&R server.

Support tells me there is no way that I can download backups from the Azure capacity tier to the performance tier and then move them to a Wasabi object repository? Again, it doesn't have to be a SOBR type repository, it could just go straight to a Wasabi repository. These are only .vbk files (monthly/yearly) backups that I need to keep per the companies retention schedule. It seems odd to me that I cannot do this in Veeam?