Availability for the Always-On Enterprise
Post Reply
janatecx
Veeam ProPartner
Posts: 7
Liked: 3 times
Joined: Oct 25, 2012 2:26 pm
Full Name: Jan De Smet
Contact:

Re: Exchange 2010 DAG backup ?

Post by janatecx » Jul 15, 2013 2:40 pm

We backup both Nodes as the customers requires a full vm backup at both sites.

We did however adjust the backup schedule. One node backup starts at 8P and the other around midnight. Just to make sure both vm's aren't being snapshot at the same time.
For Database backup, one node should suffice.

dellock6
Veeam Software
Posts: 5489
Liked: 1510 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Exchange 2010 DAG backup ?

Post by dellock6 » Jul 16, 2013 10:33 am

If you want to be sure the two jobs do not overlap, you can also schedule only the first, and have the second one chained to the first, so it will only start when the first is completed.

Luca.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com/en/
vExpert 2011-2012-2013-2014-2015-2016-2017-2018
Veeam VMCE #1

v.Eremin
Veeam Software
Posts: 15150
Liked: 1141 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Exchange 2010 DAG backup ?

Post by v.Eremin » Jul 16, 2013 11:01 am

you can also schedule only the first
Or make corresponding changes with the number of concurrent tasks that can be processed by repository or backup proxy. Thanks.

janatecx
Veeam ProPartner
Posts: 7
Liked: 3 times
Joined: Oct 25, 2012 2:26 pm
Full Name: Jan De Smet
Contact:

Re: Exchange 2010 DAG backup ?

Post by janatecx » Jul 19, 2013 9:33 am

Ok, After running a week without any problem.

The problem occured again last night. Does anyone have more info on this issue, or why this could happen suddenly?

Many thanks in advance.

Jan

Andreas Neufert
Veeam Software
Posts: 2884
Liked: 501 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Exchange 2010 DAG backup ?

Post by Andreas Neufert » Jul 25, 2013 10:43 am

Some ideas and tips from another discussion about DAG backup here in the Forum. Maybe they are helpful here as well.
My very personal list of tips to optimize Exchange DAG backups at this point are:

1) Increase the DAG heartbeat time (no reboot needed)
cluster /prop SameSubnetDelay=2000:DWORD
cluster /prop CrossSubnetDelay=4000:DWORD
cluster /prop CrossSubnetThreshold=10:DWORD
cluster /prop SameSubnetThreshold=10:DWORD
2) Use new Veeam Storage Snapshot Feature (Lefthand/3PAR/VSA) if you can (after v7 release)
3) Backup only an DAG member that hold only inactive databases (no cluster failover because of no active databases) (Logfile Truncation will be replicated by Exchange in whole DAG)
4) Try to avoid any changes at the backup time window (User, Background processes, Antivirus, ....). Also try to avoid that on all LUNs on the storage System itself (faster writes at snapshot commit).
5) Use Forward Incremental or if you Need space Forward incremental with daily transform into rollbacks. Do not use Reverse Incremental (Reverse Incremental took a bit longer than the other backup methods)
6) Use new parallel Prozessing with enought ressources to backup all of your disks at the same time (after v7 release)
7) Use Direct SAN Mode with minimal needed disks connected at selected Proxy. If not possible use NBD mode with 10GbE. (Do not run Proxy in Autoselect mode). Disable VDDK Logging for Direct SAN Mode if your backups themself run stable (ask support for the registry key and consequences).
8 ) Use actual VMware Versions (newest VADP/VDDK Kits with a lot of updates in it) and actual Veeam Versions (newer VDDK Integration)
9) Use at Minimum VMware vSphere 5.0 because of changes in the snapshot places and Background things.
10) User Fast disks for all of the VM disks (also the OS disk)
11) Less disks can help to reduce snapshot creation (and commit?) time.
12) Check your vcenter load and optimize it (or use direct ESX(i) Connections for Veeam VM selection.
13) Maybe another Option (unsupported from VMware) is to change VM Setting snapshot.maxConsolidateTime = "1" (see discussion above).

Hope that this informations can be helpful.

CU Andy

janatecx
Veeam ProPartner
Posts: 7
Liked: 3 times
Joined: Oct 25, 2012 2:26 pm
Full Name: Jan De Smet
Contact:

Re: Exchange 2010 DAG backup ?

Post by janatecx » Oct 23, 2013 6:53 am

Hi All,

The above steps have resolved the issue.
I changed the job this weekend from reversed incremental to forward incremental, and the job finishes almost 50% faster, en the DAG cluster remains online.

Thank you for the info.

Andreas Neufert
Veeam Software
Posts: 2884
Liked: 501 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Exchange 2010 DAG backup ?

Post by Andreas Neufert » Oct 23, 2013 8:08 am 3 people like this post

My updated list of tips, if you run into Exchange 2010 backup challenges:
1) Increase the DAG heartbeat time (no reboot needed) to avoid cluster failover
cluster /prop SameSubnetDelay=2000:DWORD
cluster /prop CrossSubnetDelay=4000:DWORD
cluster /prop CrossSubnetThreshold=10:DWORD
cluster /prop SameSubnetThreshold=10:DWORD
2) Use new Veeam Storage Snapshot Feature (Lefthand/3PAR/VSA) if you can (after v7 release) => Reduces Snapshot Lifetime to some seconds => No load and problems at commit because of less data.
3) If you have problems with cluster failover at Backup, one option is to backup DAG member(s) that hold only inactive databases (no cluster failover because of no active databases) (Logfile Truncation will be replicated by Exchange in whole DAG)
4) To reduce Snapshot commit time (and to reduce data in the snapshot), try to avoid any changes at the backup time window (User, Background processes, Antivirus, ....). Also try to avoid that on all LUNs on the storage System itself (faster writes at snapshot commit).
5) If you can not avoid many changes on block level at your backupwindow? Use Forward Incremental or if you need space Forward incremental with daily transform into rollbacks. Reverse Incremental took a bit longer than the other backup methods => longer snapshot livetime => more changes in the Snapshot to commit
6) To reduce Snapshot lifetime and reduce amount of data to snapshot commit, use new parallel processing with enought ressources to backup all of your disks at the same time (after v7 release)
7) To reduce backup time window and snapshot lifetime, use Direct SAN Mode with minimal needed disks connected at selected Proxy. If not possible use NBD mode with 10GbE. (Do not run Proxy in Autoselect mode). Disable VDDK Logging for Direct SAN Mode if your backups themself run stable (ask support for the registry key and consequences).
8 ) Use actual VMware Versions (newest VADP/VDDK Kits with a lot of updates in it) and actual Veeam Versions (newer VDDK Integration)
9) Use at Minimum VMware vSphere 5.0 because of changes in the snapshot places and Background things.
10) If you still facing problems, use faster disks for all of the VM disks (also the OS disk!!!)
11) Less VM disks can help to reduce snapshot creation (and commit?) time.
12) To avoid VSS timeouts (hardcoded 20 seconds at Exchange VSS writer), Check your vcenter load and optimize it (or use direct ESX(i) Connections for Veeam VM selection, so that the snapshot creation took less time.
13) If you facing VM downtime because of Snapshot commit, maybe another Option (unsupported from VMware) is to change VM Setting snapshot.maxConsolidateTime = "1" (in sconds) (see discussion above).
14) If you see Exchange VSS Timeout EventLog 1296 => Change Log setting => Set-StorageGroup -Identity "<yourstoragegroup>" -CircularLoggingEnabled $false
15) VSS Timeout Problems => Add more CPU/Memory to the VM

Peejay62
Expert
Posts: 181
Liked: 24 times
Joined: Aug 06, 2013 10:40 am
Full Name: Peter Jansen
Contact:

Re: Exchange 2010 DAG backup ?

Post by Peejay62 » Nov 05, 2013 2:23 pm

Very interesting thread this is. I am currently preparing everything to bring our exchange 2010 environment under Veeam. Already did various tests on a very small test-environment and that all works fine. But the production environment is of another magnitude. We have a 6 node DAG. Each node holding appx 9 tb of data, based on 1 and 1.5tb luns. The nodes each have 24gb mem and 4vcpu's. we run vsphere 5.1 and Veeam 7.
I don't have any reference in determining us having a small or big environment and I am trying to put all the things talked about in this thread into perspective. Obviously, i cannot do any testing in our live production environment so I am kind of swimming dry.Anybody with a similar environment wants to share on this...

Jonathan
Enthusiast
Posts: 52
Liked: 1 time
Joined: Oct 15, 2009 8:52 am
Contact:

Re: Exchange 2010 DAG backup ?

Post by Jonathan » Nov 07, 2013 12:37 pm

You could also go really wild and not back up the mailbox stores at all. Just configure your deleted items retention times to whatever period you normally keep your backups. This enables your users to restore any item they deleted themselves. Microsoft supports circular logging for DAGs of 3 members or more, so log files will be truncated automatically so long as the databases are in sync.

We've been doing this since (the year) 2010 and so far it has worked flawlessly.

chrisdearden
Expert
Posts: 1530
Liked: 225 times
Joined: Jul 21, 2010 9:47 am
Full Name: Chris Dearden
Contact:

Re: Exchange 2010 DAG backup ?

Post by chrisdearden » Nov 07, 2013 8:35 pm

Jonathan wrote:You could also go really wild and not back up the mailbox stores at all. Just configure your deleted items retention times to whatever period you normally keep your backups. This enables your users to restore any item they deleted themselves. Microsoft supports circular logging for DAGs of 3 members or more, so log files will be truncated automatically so long as the databases are in sync.

We've been doing this since (the year) 2010 and so far it has worked flawlessly.
I assume each node is on a different storage / site?

tsightler
Veeam Software
Posts: 5195
Liked: 2078 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: Exchange 2010 DAG backup ?

Post by tsightler » Nov 07, 2013 9:25 pm

I'm also curious if you have any lagged nodes in the DAG group?

Jonathan
Enthusiast
Posts: 52
Liked: 1 time
Joined: Oct 15, 2009 8:52 am
Contact:

Re: Exchange 2010 DAG backup ?

Post by Jonathan » Nov 07, 2013 9:27 pm

chrisdearden wrote:I assume each node is on a different storage / site?
Yup. Two VM nodes on a fibre channel array, one VM node in a separate site half a mile away on a different vSphere cluster existing of heavy Supermicro machines with local storage (SATA/SSD). All three nodes run CAS, Mailbox and Hub transport roles. Client access through a loadbalancer.org R16 cluster (MAPI) and a TMG 2010 cluster (ActiveSync\OWA\Outlook Anywhere).

Jonathan
Enthusiast
Posts: 52
Liked: 1 time
Joined: Oct 15, 2009 8:52 am
Contact:

Re: Exchange 2010 DAG backup ?

Post by Jonathan » Nov 07, 2013 9:30 pm

tsightler wrote:I'm also curious if you have any lagged nodes in the DAG group?
No, but I'm considering it for my new EX2013 setup.

hscox030
Novice
Posts: 5
Liked: never
Joined: Mar 22, 2012 5:27 pm
Full Name: Sean Cox
Contact:

[MERGED] first time Exchange 2010 backup question

Post by hscox030 » Nov 10, 2013 9:41 pm

I just virtualized my two Exchange 2010 mailbox servers so I'm setting up my first Veeam Exchange backup job and I have a question. I have two mailbox, CAS, Hub servers with 5 databases per server. Each server has a database copy of the other servers databases so each has 5 activated DB's and 5 DB Copies.

So my question is when I setup the job do I exclude the DB Copy drives (databases/logs) or do I include them in the backup job of one server? I plan to backup each of the two Exchange Servers. I am currently using Backup & Replication 6.5.

Thank you

Vitaliy S.
Veeam Software
Posts: 21544
Liked: 1285 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Exchange 2010 DAG backup ?

Post by Vitaliy S. » Nov 11, 2013 7:52 am

I believe it's fine to backup both databases, please review this topic for a detailed information on Exchange backup best practices.

Post Reply

Who is online

Users browsing this forum: ag_ag, andreaf-it, bavo.vdk, Bing [Bot] and 64 guests