Move proxy and repository servers to new hosts

[richs24]

Hi all,

we have a number of proxy and repository servers using Windows 2012, and as such, we need to move these roles to new servers running 2019.

With the proxy servers, is it better to just add in new Proxy servers and then "retire" the older ones, or is there a migration method that we could/should be following?

With the repositories, is it a case of building a new server with the same name/ip/etc and then remounting the storage and rescanning?

any help appreciated

Regards
Rich

[Mildur]

Hi Rich

Welcome to the forum.

With the proxy servers, is it better to just add in new Proxy servers and then "retire" the older ones, or is there a migration method that we could/should be following?

Migrating the proxy server is normally an easy task. Just deploy a new machine and it as a new proxy. This would be the cleanest option. Personally, I don't like doing in-place OS Upgrades.
It's easy, if you use virtual appliance (Hot-Add) or network (NBD) proxies. If you use a "direct storage access" - proxy server, more tasks will be involved because you have to allow the new proxy server to have access to the storage luns (FC, NFS, iSCSI).

With the repositories, is it a case of building a new server with the same name/ip/etc and then remounting the storage and rescanning? /quote]
Just rescanning won't work, because on the new server no Veeam components are installed. You have to add the new server as a backup repository to get the components deployed. You can follow Option A in this kb article on how to move the backup files --> https://www.veeam.com/kb1729
Remounting the storage is one of the options (Step 3 in the kb) to move the backup files.

Thanks
Fabian