• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 827
  • Last Modified:

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
0
jskfan
Asked:
jskfan
  • 3
  • 2
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
This is normal behaviour, when you have SLOW disks in your vSphere infrastructure or ESXi servers, and this has always been an issue since the creation of the snapshot technology, all the way back to ESXi 1.0.

You are *NOT* using 7,200rpm SATA disks are you ?

I would follow the article you have posted about VMware Tools Quiescence, and TEST IT, however you may have no choice but to upgrade your vSphere infrastructure datastores, or drop Exchange DAG VM from backups.
0
 
jskfanAuthor Commented:
In our environment we are update when it comes to hardware versions.
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:DWORD

cluster /prop CrossSubnetThreshold=10:DWORD

cluster /prop SameSubnetThreshold=10:DWORD

How are they all related? maybe they treat different things than what I am thinking of
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Basically, when the backup runs, the snapshot API call suspends or stuns the VM to create and merge the snapshot, on a slow datastore, this period of time takes too long, in some VMs, e.g. SQL, and Active Directory this causes data corruption in the database, on Exchange Mailbox Servers this can cause Outlook Clients to become disconnected from the Server.

In your DAG, it failovers, because the machine is non-responsive for a period of time, and this is detected and fails over.

These are all different methods of trying to prevent fail over, because your datastore is SLOW.

So back to my question which your AVOIDED ANSWERING!

You are *NOT* using 7,200rpm SATA disks are you ?

With all the options there are workarounds to try and fix the problem, and then you will have to test.
0
 
jskfanAuthor Commented:
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:DWORD

 cluster /prop CrossSubnetThreshold=10:DWORD

 cluster /prop SameSubnetThreshold=10:DWORD
0
 
jskfanAuthor Commented:
Thanks
0
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now