The recommended way of moving Veeam capacity tier backup

[Nas]

We are using SOBR, local disk as performance tier and Azure Cool Blob immutable as capacity tier.
Recently we discover that the blob storage account is not created as per our organization standard settings and our Azure team wants to create new storage account and move the data from old blob to new blob.

What is the best method to migrate from Veeam perspective? Add new capacity tier to the current SOBR and set maintenance on old capacity extend and evacuate backups? This way data transfer will occur between the two Azure blob only and not between Veeam gateway server?

If I recall correctly, we are not recommended to use azcopy in this workflow, is this still valid in v12.3?

The helpcenter link no longer accessible https://helpcenter.veeam.com/docs/backu ... ml?ver=120

[veremin]

If you plan to migrate data from one capacity extent to another, we recommend using the native mechanisms of our product rather than a 3rd-party tool such as Azure Copy or similar.

For this migration, you need to add the new repository to the existing Capacity Tier, enable maintenance mode on the old extent, and start the evacuation from it.

The evacuation will occur between the gateway server selected for the old extent and the gateway server selected for the new extent.

Thanks!

[Nas]

The current gateway server is the on-premises backup repository.

So if I understand correctly, data will first egress from Azure to on-premises gateway, and then ingress back into the destination Azure storage account extent, potentially incurring higher costs for the backup transfer?

What if, I deploy a temporary Azure VM in same region as the extents and add it as gateway server, will this lower the egress cost as technically the evacuation traffic occur within Azure region without flowing to on-premises?