Migrate Azure Blob storage to new Veeam server

[_james]

Hello everyone,
We are currently in process of changing Veeam servers. Old configuration is not being used, everything is built from scratch. There are no issues for regular jobs.
However for the old server we have connected Azure Blob repository that we do offsite backup-copy jobs to. We wish to connect to the new server to avoid large initial backups etc.
What would be the correct steps to map Azure repo from old to new Veeam server?

In my mind it looks something like this:

• Add the Azure repo to the new Veeam server

• Rescan te repository to build existing backup catalog

• Set backup-copy job destination to be Azure repo and then map backups

Other note - when I tried to add Azure Repo to the new server at the last step I got message that the repo will stop working on the old server. So for now it is not added.

Has anyone done this before and can share his success?

[pybfr]

You can not share a repository between 2 VBRs.
So you can add it to the new server but like the warning said, it will not be usable by the old server.

[_james]

Thank you for the reply. It is okay for us as our main goal is to succesfully attach it to the new server and for it to recognize all the existing backups in the repository.

[KirillChuxlancev]

Hello,

Kirill from QA here.

I'd like to provide a sequence of steps that will guarantee the data integrity during the migration of Azure repository between two Veeam servers.
1) Place existing Azure repository into maintenance mode (if it is a part of SOBR) or remove it from the configuration database of Veeam Server 1 (if not used anymore) - this step is needed to guarantee no data manipulation will be done on Veeam Server 1 after the repository is added to Veeam Server 2.
2) Add Azure repository to Veeam Server 2, agree to take ownership (protection from modifications outside of Veeam Server 2), provide the password (if needed).
3) Rescan the repository (if the repository was used as a standalone target for Backup Copy Job) using the Rescan button; decrypt backups if needed.
4) Edit Backup Copy Job, changing the target to newly added Azure repository. Map the existing backups to the new Backup Copy Job.

Hope that helps.

[Nas]

If the existing repository is part of SOBR in the old VBR server and we set to maintenance mode and remove the Azure storage.

After adding the Azure repo to the new VBR as standalone repo (no more SOBR) and we did a repository rescan but old backup is not appearing, do we to run import backup https://helpcenter.veeam.com/docs/backu ... ml?ver=120

[KirillChuxlancev]

Hello,

If the repository was added to SOBR as a Capacity Tier extent then Import Backup functionality is one of the ways to import backups on the new VBR server. Another way would be to add it as Capacity Tier extent to new SOBR. The former way imports backups for restores only, while the latter allows to map the imported backups to the backup jobs and continue them.

If the repository was a part of SOBR Performance Tier on the old VBR server, then rescan is the correct action to import backups. If that is the case and the rescan does not import the backups that used to reside on the Performance Tier - I suggest opening a support ticket.