migrate Veeam Proxy/Repo to new VBR server

[sandsturm]

Hi

We installed a new VBR server with some also new proxy/repository servers in one of our locations. Besides these local proxy/repository servers which we installed new, we have some remote proxy/repository servers in other locations we don't want to reinstall. My question is now: Is there a way to migrate these proxy/repository servers from one VBR server to another and if so, what is the process of doing this? (these remote locations consist of one virtual server with the proxy and repository role installed)
I wasn't able to find a documentation for this use case....

thx
sandsturm

[HannesK]

Hello,

we don't want to reinstall

I assume, that's about the operating system and not the few MByte of the Veeam services?

Remove proxy & repo from old VBR server and add to new VBR server (two VBR servers should not share the same components. sharing the same repository paths leads to issues). If you disconnect the network of the remote machine, the the old binaries stay on the machine and only the roles get deleted from the configuration. That means, the new VBR server finds "everything already installed" and does not upload the binaries again.

On the new VBR server, in the new job, map the backups

Best regards,
Hannes

[DanielJ]

As far as I can remember, mapping a backup to a job on a new server will automatically make the next run an active full. Is that still the case?

[sandsturm]

Hi Hannes

Thanks a lot for your help, I'll do it that way if it's so easy

thx
sandsturm

[HannesK]

the purpose of mapping backups is to avoid active fulls (well, and continue the backup chain)... if you see something else, I can only recommend open a support case.

[DanielJ]

Well, it would still be technically an incremental, but transfer (and contain) as much data as an active full. Or did I dream this?

[veremin]

Aren't you probably mixing this scenario with the vCenter migration case, where old VMs get new identifiers and considered as new ones from backup server perspective?

There indeed a new increment (with the size of full backup) is created.

However, your situation is different, VMs are still the same, so increment will be created as usual (without additional space required).

Thanks!