Solved

Veeam Backup of Exchange DAG

Posted on 2015-02-01
5
494 Views
Last Modified: 2016-02-25
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
Comment
Question by:jskfan
  • 3
  • 2
5 Comments
 
LVL 119

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40582990
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
 

Author Comment

by:jskfan
ID: 40583128
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
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40583427
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
 

Author Comment

by:jskfan
ID: 40583503
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
 

Author Closing Comment

by:jskfan
ID: 40655169
Thanks
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question