jskfan
asked on
Veeam Backup of Exchange DAG
When Backing up Exchange DAG with Veeam, it causes Failover which is not desirable.
Veeam talks about working around this issue in this link:
http://www.veeam.com/kb1744
However in different link Veeam talks about :VMware Tools Quiescence
http://helpcenter.veeam.com/backup/80/vsphere/tools_quiescence.html
I do not understand which approach should I go with in order to prevent Exchange DAG failover.
*Veeam also has an option(checkbox) for VSS integration. So it makes it much more confusing which approach to go for.
Any help will be very much appreciated.
Thank you
Veeam talks about working around this issue in this link:
http://www.veeam.com/kb1744
However in different link Veeam talks about :VMware Tools Quiescence
http://helpcenter.veeam.com/backup/80/vsphere/tools_quiescence.html
I do not understand which approach should I go with in order to prevent Exchange DAG failover.
*Veeam also has an option(checkbox) for VSS integration. So it makes it much more confusing which approach to go for.
Any help will be very much appreciated.
Thank you
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
In our environment, what I know is Veeam verified the hardware and the compatibility before they gave green light to install VBR. However our Backup Admin, when he ran the back of Exchange DAG, it failed over, there was no Outlook user Impact, since it is just a failover.
What I was trying to understand is, if the answer is YES or NO to your question:
You are *NOT* using 7,200rpm SATA disks are you ?
Which of the approaches will avoid the DAG Failover? is it going to be:
**VSS integration
OR
**VMware tools quiescence
OR
the work around to Fix DAG nodes failover by changing timeout values to max with no server reboot (command line):
cluster /prop SameSubnetDelay=2000:DWORD
cluster /prop CrossSubnetDelay=4000:DWOR D
cluster /prop CrossSubnetThreshold=10:DW ORD
cluster /prop SameSubnetThreshold=10:DWO RD
What I was trying to understand is, if the answer is YES or NO to your question:
You are *NOT* using 7,200rpm SATA disks are you ?
Which of the approaches will avoid the DAG Failover? is it going to be:
**VSS integration
OR
**VMware tools quiescence
OR
the work around to Fix DAG nodes failover by changing timeout values to max with no server reboot (command line):
cluster /prop SameSubnetDelay=2000:DWORD
cluster /prop CrossSubnetDelay=4000:DWOR
cluster /prop CrossSubnetThreshold=10:DW
cluster /prop SameSubnetThreshold=10:DWO
ASKER
Thanks
ASKER
What I need to understanding is the difference between :
**VSS integration
**VMware tools quiescence
**and the work around to Fix DAG nodes failover by changing timeout values to max with no server reboot (command line):
cluster /prop SameSubnetDelay=2000:DWORD
cluster /prop CrossSubnetDelay=4000:DWOR
cluster /prop CrossSubnetThreshold=10:DW
cluster /prop SameSubnetThreshold=10:DWO
How are they all related? maybe they treat different things than what I am thinking of