Server migration

[ergole]

Hi, we asked the following through a support case (ID 03685851) but maybe someone can answer quickly in this forum

We actually have a physical server with Veeam B&R, Enterprise Manager and Veeam One (versions 9.5.0) running.
Backups are stored on local harddisks.
Most of jobs are forever incremental backups running each night (between 22h and 05h) with guest files indexing enabled.
We keep around 90 restore point and make a synthetical full backup once a week.
We backup Windows wirtual machines, hosted on several standalone Hyper-V hosts (without System Center).

This physical server is running out of free disk space (only 2.5To free out of 36To total disk space).
We bought a new server with more disk space and made a fresh install of Veeam B&R , Enterprise Manager and Veeam One (versions 9.5.4).

Our problem is that transfering 34To from one server to antoher will take too long so we cannot disable all jobs, transfer backup data and configuration and reenable all jobs.

How we should proceed to migrate jobs progressively during from the actual server to the new one, keeping all guest files indexing history and restore points history ?

[Rick.Vanover]

If you have a case, please follow that guidance.

But I'm convinced the scale-out backup repository and possibly the configuration backup are part of your solution.

Do you have another backup storage device identified? If so - I would prepare it for use. If the scale-out backup repository is used, you can do the following:
-Add a new storage repository
-Create a scale-out backup repository
-Add the new storage to it
-Add the existing repository to the performance tier of what you have created (you will be asked if you want to update database configuration & jobs to the scale-out backup repository)
-Consider also optionally doing the configuration backup & restore to a new server if needed/desired

[ergole]

Thanks a lot for your comment.

Veeam support answered us to disable one job, copy backup data to the new server and enable the job on the new server...
That means a lot of manual operations so a big risk of mistakes...

We didn't knew what scale-out repository is but it seems to be exactly what we need !
We just asked to Veeam support why they didn't mention this solution.

What we do not well understand is : can we safely add our existing repository to a scale-out repository ? Will all jobs' configuration be updated with the new scale-out repository as new target automatically ? If yes that's definitely THE solution of our case !

[Rick.Vanover]

I can't go against support myself ergole, but the SOBR is designed to update the target to be the new repository (a SOBR).