Cloning Veeam Proxy

[LEWISF]

One of my VM proxy servers died over the weekend. Thinking about cloning an existing proxy and doing the rename, re-ip, remove from the domain, add back into the domain. Saw some old posts where there could be an issue with cloning a proxy but there was still some unsureness as to whether the issues were fixed. I believe some of the issues were about hot-add. Anyone know if you can clone a proxy without Veeam having an issue with the clone?

TIA

Lewsi

[david.domask]

Hi LEWISF,

I think main thing would be about BIOS UUID getting cloned -- hotadd is a bit sensitive to duplicate BIOS UUIDs (this can result in incorrect VM selection, which is why we have a VM picker when duplicate BIOS UUIDs are detected, so just make sure that it gets updated. Since you're removing the original proxy anyways, I don't anticipate this being an issue, but if you find that the new proxy "can't be found" even when set as specific proxy, recreate the BIOS uuid on the VMware side and then rescan the proxy.

[LEWISF]

Thank you David.

[Provogeek]

Lewisf,

When I did such a task, I shutdown the machine and converted it to a template. Deployed a new VM from template using a Customization Specification to make sure the SID was changed. I then needed to uninstall the Veeam components manually before I was able to successfully add the proxy to Veeam. Only really saves on the time needed to patch Windows after a new install.

I would suggest looking into the Linux Proxy.