VeeamZip options

[lando_uk]

Using v9.

When I do a VeeamZip on one of my VMs, it doesn't give me the option of choosing which proxy to use. So when I have 2 or more vdisks, sometimes one of them gets processed by a remote proxy that has slower network connectivity, so my VM data goes over the WAN and back again for no reason, the whole zip would run much faster if it was using a local proxy.

The interface really needs a new option to choose proxy, like on backup and restore jobs.

Thanks

[PTide]

Hi,

In v9.5 we've added the proxy affinity technology which is probably another way to achieve what you want. As a workaround for v9 you might want to create a one-time backup job for the VM.

Thanks.

[foggy]

Another option is to ensure there's a hotadd proxy available for this VM, since the behavior you're describing indicates NBD transport mode is used.

[mma]

Hello veeam

Can you please add manual proxy selection for VeeamZIP jobs?

We have a setup with 1 physical proxy and 5 virtual proxies, all of them in different networks.
I need to save a VM from an "isolated" ESX Hosts. The only proxy which has access to it (becauseof firewall rules) is the physical one. None of the proxies is in the same IP range as the ESX host, so the proxy selection is some sort of nontransparent.
The Veeam proxy selection algorithm selects one of the virtual proxies as there is no direct SAN access to the datastore of this host - no backup possible.

Thanks

[mma]

Proxy affinity will not help:
- All proxies write to the same repository
- Does not work at all if I do VeeamZIP to a folder

[Ollo]

Hello,
we are using Veeam with storage integration. When we like to zip a VM with VeeamZIP, Veeam decided always to use the hardwareproxy and ALWAYS try to make an storage snapshot.
I couldn't find an option to choose a proxy when using VeeamZIP. If the option is not presented, thats a must have feature.

Regards

[Gostev]

What's wrong with storage snapshot? VeeamZIP can take a while since it's a full backup, so storage snapshot will help you avoid those typical large snapshot commit issues.

[Ollo]

Storage Snapshot needs an license an IBM SVC for a maximum concurrent use.
And a snapshot binds a lot of ressources on the svc.
The backup admin should decide which backup method has to be used.

[Ollo]

Next problem we have is, that not all proxies as the same rights in the dmz. Veeam always desided to choose the "wrong" proxy.
So please implemented a manual proxy selection and a manuel selection, if a storage snapshot will be taken or not.