Hello all,
We are currently running a backup server on Windows Server 2019 and local Scale-Out Backup Repositories (2x3 Volumes). We acquired a new server that will run Server 2022 and will have a different storage layout (1 Scale-Out Repository with 3x Volumes).
Now, I am used to migrating simple server setups, but in this case, we are not sure how to most efficiently migrate.
We have a couple of backup jobs that run daily and due to specific requirements around 100 backup jobs that we run manually on request. We want to keep all backups created for those 100 backup jobs and we also need to keep the backup jobs. In addition, there are a couple of tape jobs.
Now, we can of course import the configuration, but we will need to adjust the scale-out backup repository and also adjust all jobs to point to that repository. That will involve some work, but seems doable.
The main question we have is: how do we migrate the actual backups on the disk? If we look at the thing from a volume perspective, we have 6 volumes and in certain cases the backups could be spread across multiple volumes.
Does anyone have experience with this and has some recommendations on the best way to proceed?
Many thanks!
-
- Enthusiast
- Posts: 36
- Liked: 2 times
- Joined: Nov 13, 2014 10:29 am
- Contact:
-
- Veeam Software
- Posts: 92
- Liked: 31 times
- Joined: Apr 07, 2021 9:15 pm
- Full Name: Pete Ybarra
- Contact:
-
- Enthusiast
- Posts: 36
- Liked: 2 times
- Joined: Nov 13, 2014 10:29 am
- Contact:
Re: Server Migration with Local Scale-Out Repositories
Hello there,
Thanks for your answer.
I had a look, and I assume Method A would be the way to go.
However, I'm not 100% clear whether we can proceed the same way for scale-out repositories. In our case, the backups are spread across multiple volumes and there are also multiple vbm files. Can we just merge those (i.e. overwrite the vbm file) in the new location, then perform a rescan?
So:
1. Restore configuration on new backup server
2. Copy all backups from all repositories and extents (2 scale-out repositories with 3 extents each) and consolidate them on the new server (1 scale-out repository with 3 extents)
3. Perform a rescan/adjust job options, as described in the linked article
I was just mainly unsure about the scale-out repositories, as previously we always had backups within a single repository and not spread across multiple folders/volumes.
Thanks for your answer.
I had a look, and I assume Method A would be the way to go.
However, I'm not 100% clear whether we can proceed the same way for scale-out repositories. In our case, the backups are spread across multiple volumes and there are also multiple vbm files. Can we just merge those (i.e. overwrite the vbm file) in the new location, then perform a rescan?
So:
1. Restore configuration on new backup server
2. Copy all backups from all repositories and extents (2 scale-out repositories with 3 extents each) and consolidate them on the new server (1 scale-out repository with 3 extents)
3. Perform a rescan/adjust job options, as described in the linked article
I was just mainly unsure about the scale-out repositories, as previously we always had backups within a single repository and not spread across multiple folders/volumes.
-
- Veeam Software
- Posts: 92
- Liked: 31 times
- Joined: Apr 07, 2021 9:15 pm
- Full Name: Pete Ybarra
- Contact:
Re: Server Migration with Local Scale-Out Repositories
Your welcome, @RWeiss please look over the documentation for "Service Actions with Scale-Out Backup Repositories" https://helpcenter.veeam.com/docs/backu ... ml?ver=120 this should give you some ideas to work with
.

Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 37 guests