1. The importance of backing up exchange server.
As the exchange product updates, there are many improvements. DAG is one of new features. In exchange 2010/2013, DAGthat provides a simplified, unified framework for high availability and site resilience. But even the most extreme forms of redundancy and fault tolerance can't protect you against every possible failure or disaster. It is essential that effective
protective measures are taken for the critical data in your Exchange organization. Thus we need backup software to make backups of Exchange data.
2. Tips (Windows Server Backup)
1). Expecting the log files are truncated after backing up database, the full backup should be used.
![]()
2). When using Windows Server Backup, there is an exchange consistency check.
![]()
a. If the consistency check fails, the backup may fail. Using eseutil utility to check the consistency of the logs and the databases. (Note: Before using the eseutil utility, please dismount database which is checked. Otherwise, the error
will occurs.)
![]()
b. Dismount Database
![]()
c. Dismount the database checked, using eseutil/mh to check database status.
![]()
d. Use eseutil /ml to check whether the required log files are available in a clean state.
![]()
e. Additional information:If the database status is dirty shutdown, checking whether the required log files are available. If the log files are available, using eseutil/r
to repair database.
![]()
If the required log files are missing, we can recover database from a valid backup, if there is not a valid backup, running hard repair (eseutil /p) to repair database. (Note: Using eseutil /p may cause information loss, thus it is recommended
that recovering database from a valid backup.)
![]()
Note: It is recommended that immediately performing a full backup of this database and offline defragment the database.
![]()
More Reference: http://technet.microsoft.com/en-us/library/aa996953(v=exchg.65).aspx
3). Use these methods to check backup information after back up database.
a. Check database backup time.
![]()
b. View list of all backed up files.
![]()
c. Check event logs (such as :)
![]()
![]()
![]()
4). DAG backup
Back up a server hosting the data (active and passive database copies) that is a member of a DAG, when using Windows Server Backup to back up the server, a warning information will occur:
![]()
![]()
In order to avoid this warning, we must disable the Microsoft Exchange Replication service VSS writer as the following steps:
=====================================================================
a. Open Registry Editor. (Note: Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved.
Before editing the registry, back up any valuable data.)
b. Add a registry key to disable the Exchange Replica Writer.
HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters. Add a new DWORD value namedEnableVSSWriter with a value of 0.
![]()
c. Restart the Microsoft Exchange Replication service
![]()
After do that, back up exchange server again.
![]()
![]()
3. After back up database successfully, log files are not truncated. How to release disk space. Following steps:
===================================================
a. Check backup type: whether there is a valid full backup.
b. If doing a full backup successfully, please restart
Microsoft exchange server extension for windows server backup service.
c. If committed log still be there, please enable circle logging. But after enabling circle logging, there are noa complete set of transaction log files, we cannot recover any data more recent than the last full backup. (Note: If the environment is DAG, it will influence replication between databases)
d. It is not recommended that moving log files manually. But if we really want to move log files manually, please dismount the DB, use eseutil/mh to check DB header, move the logs which are already committed, mount the store, and take a full
backup.
More Reference.
http://technet.microsoft.com/en-us/library/dd876874(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/dd876854(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/dd876864(v=exchg.141).aspx
http://technet.microsoft.com/en-us/magazine/jj906377.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.