you can also schedule only the first
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.
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.
chrisdearden wrote:I assume each node is on a different storage / site?
Users browsing this forum: Bing [Bot], dcheung, Google [Bot] and 14 guests