Exchange Full backup does not Truncate logs and Exchange event shows No log files can be truncated

book

Article ID: 100003000

calendar_today

Updated On:

Description

Error Message

Successful Backup.

Exchange ESE reports "No log files can be truncated."

Cause

Exchange database logs of a Storage Group are shared for all databases of that Storage Group. In order for Exchange to commit / flush / truncate the logs, all of the Databases of the Storage Group must be backed up together.

 

A. The Application log of the Exchange server will show ESE events for the successful backup and then an ESE event for "No log files can be truncated."

B. The Application Log of the Exchange server shows an ESE event that the Purge failed as the database is offline.

Resolution

  • Check the Backup Selections and add the other database (s) to the backup job.
  • Set the offline DB to online or remove the offline DB to allow the purge.

Issue/Introduction

Exchange Full backup does not Truncate logs and Exchange event shows "No log files can be truncated".