Replace Proxy but keep its repositories

[sfbpf42]

Hello to all

I need to replace my VBR proxies, because of windows issues. But, one of them has attached virtual disks that are used as repositories.
If I remove them, I loose all jobs that use it from the configuration

Is there an easy way to attach these disks to a new proxy and use them with minimum damages?

[Mike Resseler]

Hi Odysseas,

Is that windows proxy also a repository? (I assume so). Can you look at this article and see if it helps your case? https://www.veeam.com/kb1729

[sfbpf42]

Hello Mike
Thank you very much for the reply

Well, I cannot copy/move the backup files, since there is no need for that

I will try to be more detailed, hoping that I will not frustrate you:
I have a proxy server, which has 2 additional virtual HDDs attached (1 for system and 2 additional HDDs). Now what I want is to detach these 2 HDDs from this proxy server, attach them to another one and use them again as repositories?
Is there an easy way to do this?

[foggy]

Well, technically you do not need to move files, since they will still reside on the same disks, however, the path to repository will change and you need to let Veeam B&R know about that. For that you need to follow the instructions outlined in the KB Mike has mentioned - create new repository, rescan it and edit the jobs to re-point them to the new repo.

[sfbpf42]

Hello foggy

So, I have to perform these actions, but without first remove the "old" repos, correct?

[foggy]

You can remove old repositories after checking that everything is fine. Also, the second part of the article doesn't apply to your case - you do not need to perform mapping, since you keep your jobs intact, just repoint them.

[sfbpf42]

Good morning guys

Well, today things look promising: I attached the virtual disks to a new Proxy, added them as repositories and re-pointed the jobs to these repositories. Until now, all jobs work fine
Minor think though: I try to remove the inaccessible repositories but I get error that they are used from jobs I have already pointed to the other one

Any idea what this may happen? Is there something that I have to restart (like a service or something)?

Again, thanks for all the help and suggestions

Best regards

[foggy]

You should be able to remove the old ones. I suggest asking support for assistance in cleaning things up, may be some obsolete records in the database.

[sfbpf42]

OK, sorry about that, I had to change also some seeding and the metadata repository