We have a pretty simple setup: Veeam 8 physical server with 20TB local storage (and connected to SAN), one additional VM proxy on the same LAN (but not same IP segment) and multiple proxies across a WAN. With automatic proxy selection on my BACKUP jobs, it always picks the right ones... but today I did a VeeamZIP for a VM I'm decommissioning, and it chose two proxies ACROSS THE WAN to use to back up to LOCAL storage (the other local VM proxy was disabled because of something else I was testing.)
Is this expected behavior, where VeeamZIP jobs just pick random proxies? I went ahead and stopped the job, enabled the local VM proxy, and restarted it... now it chose that one, but STILL didn't choose the Veeam server itself as a proxy, which would have been the best choice as this is a SAN-accessible VM going to local veeam storage. (and no, the veeam server wasn't doing any other jobs at all.) It's as if it was insisting on using hotadd for this job, and since the only proxies available (first job) that can do hotadd were across the wan, it chose them.
Just trying to understand what happened here... not a huge deal since my backup/replication jobs ARE choosing sane proxies and I don't VeeamZIP that often. It's also curious that VeeamZIP has no ability to let you select the proxy... unless I'm just missing it.