Database Availability Group backup best practices
– To decrease the load on the production Exchange server, specify that the backups are taken from a healthy passive database copy. If no passive copy is available, the backup is made from the active copy of the database. To specify that backups are taken from a healthy passive database copy, add
/PREFERDAGPASSIVE to a backup command.
– Use the command-line backup options /EXCLUDEDAGPASSIVE, /EXCLUDEDAGACTIVE, or /EXCLUDENONDAGDBS to exclude certain databases from backup processing.
– For databases in a DAG that have two or more healthy copies, you can skip the
database integrity check by using the /SKIPINTEGRITYCHECK option.
– To maximize availability, schedule multiple servers to back up copies of each
database. Use the /MINIMUMBACKUPINTERVAL option to ensure only one copy is
backed up for each backup cycle.
Database Availability Group restore best practices
– Run restores to the active database copy.
– Backups to Tivoli Storage Manager can be restored to any Exchange server in the
domain. However, backups to LOCAL can be restored only on the server where
the backup was created.
– To restore to a server hosting a passive database copy, make the copy active
before performing the restore.
– When the restore is complete, you can move the active database copy back to
the passive state