Procedure to add an existing repository on a new Veeam BR server during migration

[mcgregor]

Hi all,

We are planning to migrate Veeam Backup & Replication server to new hardware and want to keep the existing backup repositories with all data and restore points intact. We have physical disks with repositories on the disk array which will be connected to the new server.

I would like to ask what is the best recommended procedure to ensure that Veeam on the new server correctly maps these repositories and recognizes all existing backup data without losing backup history or requiring a new full backup?

Specifically, I am interested in:

How to properly connect the disks/repositories (mount points, drive letters) on the new server and add to Veeam

Any recommendations or pitfalls to watch out for during this process.

If you have experience or official documentation links outlining the correct steps, I would appreciate your sharing them. I am not sure, if following source is applicable, since the old backup server should be migrated, not after the hardware fault - https://www.veeam.com/blog/migrate-repo ... erver.html


Thank you in advance for your help!

[david.domask]

Hi mcgregor,

Just to confirm, the old Backup server will be decommissioned entirely? And the storage backing the existing repositories is sourced from a separate storage array?

https://helpcenter.veeam.com/docs/backu ... figuration

Please note this point from the linked page:

If you have local repositories, after migration to another machine they may be displayed as empty. In this case, add them again and remap the jobs.

So adding "new" repositories and re-mapping the jobs will be required. Since the repositories will be associated with the old Backup server, they will show as offline unless the old backup server is also added as a managed server, so remapping is going to be required regardless, but once done there will be no need for an active full. The blog post you linked indeed is not applicable here as that's about replacing a managed server, not the Veeam server itself.

[mcgregor]

Hi @david.domask, thank you so much for your response.

Indeed, the old backup server will be decomissioned.The storage respresents a separate storage array. Nevertheless, what actually means "adding repository again" - it consists of adding the storage/volume disk through Disk management in Windows and what to do in Veeam? Is it necessary to create the repository under the new name or the same name? Remaping the jobs should be most likely intuitive through Veeam?

Your answer will be much appreciated!

[david.domask]

Happy to help mcgregor

Adding a repository again means go through the add repository wizard and create a new repository in Veeam pointing to the correct location.

If you have the existing repositories in a scale-out backup repository (SOBR), you can add the "new" repositories to the SOBR and remove the old ones at the same time, and everything will be fine.

If you use stand-alone repositories, process would be:

1. Add the "new" repository
2. Edit the jobs to point to the new repository(-ies)
3. Remove the old repository(-ies)
4. Rescan the new repository(-ies) to import the backups
5. Edit the jobs to map to the imported backups