Storage capacity for a Veeam Repository is mounted via “Server A”. Now the storage should be provided by a new “Server B”. The repository is part of a Scale-out Repository. After these changes, everything should behave as usual.
Looking for a How-to where the repository is NOT part of a scale-out backup repository? For simple repositories read on here
Starting point is a Scale-out Repository containing two extents. Both are provided via “Server A” (Servername = VeeamV10):
Repository “TestMoveRepo1” already contains backup data. We will change the host server of the repository in this example to a new installed windows server:
To provide the repositories by “Server B” instead of “Server A” you have to process the following steps:
- Stop and disable all backup jobs and backup copy jobs using the involved Scale-out Repository as target or source
- in the console change to “Backup Infrastructure” – “Scale-out Repositories”
- open the properties of the involved Scale-out Repository and remove the repository (in our example “TestMoveRepo1”) from configuration
- answer the upcoming warning (see screenshot) with “Yes”
- in “Backup Repositories” right-click the repository you want to change and select “Remove”.
- answer the question ” Delete this Backup Repository?” with “Yes” (no backup data on the repository will be deleted. It will only be removed from configuration):
- disconnect the storage capacity from Server A und reconnect it to the new Server B
- in the console select “Add new Repository” to add the repository now connected via Server B. Take care to provide the same configuration settings as before.
- as soon as the repository is available you can add it to the Scale-Out Repository as an extend
- finishing the wizard will update the repository information:
- in the overview you can see that the host server changed from “VeeamV10” to “192.168.209.11”:
Verify your configuration changes:
- running a backup job using the moved repository as target should work as expected. As you can see in the screenshot below, an additional incremental file was created in the moved repository without any issues: