Proxy at colo, ESXi mgmt network or ESXi host?

[moc44]

We run Veeam/VMware and have a cold/warm colo we use for DR.

Doing some VM restore testing and speed was really slow because we don't have a proxy server at the colo, yet.

When we setup the proxy at the colo, does it need to be on the ESXi mgmt network, or does the proxy VM just need to be on the ESXi host we restoring to and the proxy can be on any local network?

[PetrM]

Hello,

There is no requirement to keep it in the management network. Also, I recommend using HotAdd mode to achieve better performance.

Thanks!

[moc44]

Thank you, got it almost working...

We are on version 11a.

The restore works, but it's pulling from the performance repo and not capacity SOBR as we want it to for the colo.

We've tried putting the performance repo into maintenance mode, and the restore pulls from SOBR, but instead of directly downloading to the colo using the colo proxy, the restore uses the BR server to download from SOBR and then it transfers it to the proxy at the colo.

The only relevant log entry seems to be "Cannot find a proxy meeting the proxy affinity rules"
What does this mean?

We are selecting the proxy during the restore process "Use the selected backup proxy servers only"

How do we get the proxy at the colo to download/restore from SOBR?

[PetrM]

Hello,

Did you try to specify the colo proxy as a gateway server in the Capacity Tier extent settings (select "Through gateway server") ?

Thanks!

[moc44]

That worked for us, we got the restore to work how we want - thank you!

Do you happen to know if v12 has any options for selecting a gateway as part of the restore job rather than changing config?

[PetrM]

Hello,

Nope, this is the only way at the moment.

Thanks!