Different transport mode for different job

[sogapex]

Hi,
currently, we have 3 jobs in our backup scheme =
* incremental during night and at lunchtime => NAS over ethernet
* full each night => usb "rotated" drive on physical Veeam B&R server
* incremental/full each month on saturday night

We have 2 VMs proxy on the vsphere infrastucture

It seems ndb transport mode is best for the "lunchtime" incremental NAS backup because there is no need to mount the disk on the proxies to start backupping
But in all other cases, hotadd is best

I know this is possible to force a specific transport mode at the proxy level, but wouldn't it be nice to be able to specify that at the job level ?

In our case =
if we allow the hotadd mode, the lunchtime backup slow down all the users but all the backup jobs are quite fast
if we force the ndb mode, at lunchtime, this is transparent, but during night, slower

[Andreas Neufert]

Hi, can you please share why the HotAdd mode slows down all the users?

[sogapex]

I guess it is using too much resources (disk activity or network ?)
sometimes, the main RDP server is nearly irresponsive during the backup.
And as far as "low activity" VMs are concerned, it takes "a lot of time" to just hodadd the disk whereas the network transport mode finished the job within minutes

[foggy]

I know this is possible to force a specific transport mode at the proxy level, but wouldn't it be nice to be able to specify that at the job level ?

At the job level, you can select the backup proxies that should be used.

[sogapex]

so, my best solution would be to give another VMs the proxy role, force the transport mode to network and then force this specific proxy to handle the job ?
I will give it a try, since "network mode" doesn't rely on the datastore on which is run the proxy, this shouldn't be a problem, I guess.
Thanks Foggy

[Andreas Neufert]

correct

[sogapex]

Ok, everything went right during the night
This is working as expected now, thanks