Exchange logs are not being purged after a FastBack backup
If the Exchange Server transaction logs are not truncated after the backup, the volume that contains the logs can reach max capacity. This can cause the Exchange Server to crash.
Resolving the problem
When the Exchange logs are not purged after the FastBack backup, this is usually a result of an incorrect configuration. In order for the FastBack backup to correctly truncate the Exchange logs, the following configuration should exist:
The logs will only be truncated if the backup is performed at an application level. To perform an application level backup, select the Exchange Server databases when configuring the Client Group. If only the volumes containing the Exchange Server data are selected (and not the actual databases), the purge processing will not be able to interact with the ESE API and the purge will fail.
Under the Application Aware menu for the Job Schedule, ensure the "Purge Exchange server log files" selection box is checked.
For an environment that has Exchange 2007 or greater, enabling VSS should be checked within the policy. When the FastBack backup is complete, the VSS interface will notify the Exchange server that the logs can be purged. The actual purging of the logs will be performed by the Exchange Server.
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.