-
- Novice
- Posts: 8
- Liked: never
- Joined: Jul 28, 2014 9:13 pm
- Full Name: Andrew
- Contact:
Feature Request - Transport Mode on Per Job Basis
Just a suggestion, not sure if it would be taken in to consideration, but it would be handy for us anyway...I know I can "pin" a specific proxy to a backup job and change the mode for that proxy, but that would require creating yet another 1 or 2 proxies. In my case hot-add is causing an exchange DAG fail over, even with the tweaks to the cluster settings when using hot add. It'd be great if we could set only for our exchange server backup jobs to use NBD, while allowing the other jobs that use those proxies to use hot-add (or automatic).
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Feature Request - Transport Mode on Per Job Basis
Maybe try to fix the HotAdd processing:
There is a way to reduce the stun time at HotAdd. Please check procedure "For environments with NFS Datastores" from KB http://www.veeam.com/kb1681 This can help as well if you use block storage. Just give it a try. => Option 2
Just a guess... do you run Exchange on NFS?
There is a way to reduce the stun time at HotAdd. Please check procedure "For environments with NFS Datastores" from KB http://www.veeam.com/kb1681 This can help as well if you use block storage. Just give it a try. => Option 2
Just a guess... do you run Exchange on NFS?
Who is online
Users browsing this forum: kwangilsung and 149 guests