https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzQ0IiwiaGFzaCI6IjdmZWYxNzA5LTk0NDYtNDgyZi1hY2YzLWRmNmJlNzk1OTM0YiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Tips for DAG Exchange Backup and Replication in vSphere

KB ID: 1744
Product: Veeam Backup & Replication
Version: All
Published: 2013-03-27
Last Modified: 2021-01-08
Languages: FR

Challenge

During snapshot creation or commit phase of a Veeam Backup or Replication job using vSphere, a primary node in a DAG cluster may lose the heartbeat long enough to cause a failover to the secondary node. 

Cause

This problem is caused by the lack of connectivity that can occur in VMware vSphere during snapshot operations.  It is sometimes referred to as the "stun" period.  All Veeam Backup and Replication jobs require snapshot operations in vSphere.

Solution

The suggestions below are general advice intended to help alleviate and prevent issues. Every environment is different, and while these settings and suggestions may work in one environment, they may have little or no impact in others. Generally speaking stability issues which occur are often environmental, and will require investigation of all components involved, both physical and software.

The suggestions below include configuration changes to VMware as well as Microsoft Exchange. Veeam is not responsible for any issues incurred after making the suggested changes. You are advised to contact and review all setting changes with the respective product support organization.

  • Place the Exchange Virtual Machines disks on the fastest disks (Datastores) that are available.
  • Disable all background scanning and/or maintenance tasks occurring in Exchange, or any other tools that are being leveraged against the system at the time of backup.
  • Perform the Exchange Backup singularly as opposed to concurrently with other jobs.
  • Review cluster failover sensitivity using this command line tool and switch.
    See note below if running Server 2012 or newwer.
    cluster /prop
    
    Adjust Microsoft settings for failover sensitivity (in bold, run from command line)
    cluster /prop SameSubnetDelay=2000:DWORD ::(Default: 1000 in Server 2008 R2)
    cluster /prop CrossSubnetDelay=4000:DWORD ::(Default: 1000  in Server 2008 R2)
    cluster /prop CrossSubnetThreshold=10:DWORD ::(Default: 5  in Server 2008 R2)
    cluster /prop SameSubnetThreshold=10:DWORD ::(Default: 5  in Server 2008 R2)
    
  • Add the line snapshot.maxConsolidateTime = "1" to the .vmx (configuration) file for the primary node.
    Please note that this is an undocumented vmx alteration, and should be validated by VMware support prior to using.
  • Reduce total amount of disks (.vmdk's) for primary node if possible, reducing impact of snapshot operations.
  • If the VM resides on a datastore backed by NFS storage, consider migrating the VM to VMFS storage.
  • Test snapshot operations directly to ESX(i) host instead of vCenter. (In some cases, gaps in communication between vCenter and ESX(i) host can impact snapshot operations, including VSS operation timing.)

Note: With Server 2012 or newer cluster.exe may not be available, as such you will need to install and use the PowerShell cmdlets. The cmdlets may need to be enabled using the following command:

Install-WindowsFeature -name RSAT-Clustering-CmdInterface

View cluster settings:

Get-cluster | fl *subnet* - provides current settings for timeout

Adjusting cluster settings:

(get-cluster).SameSubnetThreshold = 20   #(Default 10 in Windows 2012R2+)
(get-cluster).SameSubnetDelay = 2000     #(Default 1000 in Windows 2012R2+)
(get-cluster).CrossSubnetThreshold = 40  #(Default 20 in Windows 2012R2+)
(get-cluster).CrossSubnetDelay = 4000    #(Default 1000 in Windows 2012R2+)

More information

Backing up just the passive node of a DAG cluster will still provide full recovery options.  Provided replication of information is current between each cluster node, a backup of the passive node should still properly truncate Exchange transaction logs.  Please confirm transaction logs are truncating after backing up the passive node.  Then it should be possible to use Veeam Explorer for Exchange (VEX) to restore mail objects (2010 and newer).
KB ID: 1744
Product: Veeam Backup & Replication
Version: All
Published: 2013-03-27
Last Modified: 2021-01-08
Languages: FR

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.