Best practices for Backup Exec 2010 Agent for Microsoft Exchange Server

Best practices are vendor recommendations and can be extended with the information available in the Backup Exec 2010 Administrator’s Guide.


Here the main general recommendations from Symantec’s KB are collected here:

  • If you want to perform Incremental and Differential Backups, you can recover information up to a point and use continuous protection from the transaction logs of the Information Store, you must first remember to disable circular logging.
  • Separate the transaction logs from the database. If they share the same physical or logical disk Otherwise if the disk that contains the data is damaged your chances for recovery may disappear as well.
  • If you use DAG (Exchange 2010) have at least one passive database for every database you wish to protect.
  • Bear in mind retention periods for the elements and deleted mailboxes when sizing the storage. The longer the retention period, the more space you will need. Remember however to configure Exchange so elements are not fully deleted until a valid backup has been performed.
  • Disable Cache writing on the SCSI controller because it can corrupt the information in case of a hardware failure before writing the information to disk.
  • Of course bear in mind all considerations Microsoft includes in their documentation.
  • Document you Exchange server configuration in detail.


To plan for recovery in the event of an Exchange Server disaster:

  • Test your environment frequently to check that your environment is behaving as expected.
  • Study in detail the information Microsoft provides to prevent disasters and recover from them.
  • Document the Exchange Server configuration in detail. Track any changes that arise. Note all hotfixes and service packs applied.


You can find more information here: 

  • Thursday, 30 May 2013