ISSUE: No *tmp.log found for database (MS Exchange 2010 server backup)

George Law
  • Updated
Follow
  • Product Version:
    ServosityPro: All
    OS: Windows (MS Exchange 2010) 
  • Problem Description:
    When performing a MS Exchange 2010 server backup, the following error message is received in the backup report:

 

Backup Logs
 No.  Type  Timestamp  Backup Logs
1 Info YYYY/MM/DD hh:mm Start [ Windows platform (Server), ServosityPro x.x.x.x ]
2 Info YYYY/MM/DD hh:mm Start running pre-commands
3 ... ... ...
*  Error  YYYY/MM/DD hh:mm No *tmp.log found for database 'Microsoft Exchange Server\Microsoft Information Store\SERVER\
Mailbox Database'
*  Error  YYYY/MM/DD hh:mm Errors found while validating your backup files. Please run a full backup to correct the problem.
  • Cause:
    This error can occurs if the circular logging option of the affected mailbox database was previously disabled for a previous backup job, and then enabled for the sub-sequence backup jobs.
    When circular logging is enabled, the *.tmp (temporary workspace) file is not spooled to the temporary directory, causing the error to be shown. 
  • Resolution:
    To resolve this problem, please disable circular logging for the affected mailbox database:
  1. Start Exchange Management Console
  2. Expand Microsoft Exchange On-Premises (Server), then expand Organization Configuration
  3. Select Mailbox, and right click on the affected mailbox database shown in the middle panel

    ex2010.png
    Figure 1.0 - Exchange Management Console


  4. Select Properties, and the Maintenance tab

  5. Un-check the Enable circular logging checkbox

    ex2010CL.png
    Figure 2.0 - Exchange Management Console (Mailbox Database Properties)


  6. Perform a full MS Exchange server backup manually via the ServosityPro user interface afterward

    ex2010_3.PNG
    Figure 3.0 - ServosityPro user interface (Backup Options
 


Note:  Same error will remain on the initial sub-sequence backup (initial full server backup will complete with the same error). However, the problem will be resolved on the next job, which re-upload the corresponding *tmp.log file to the Servosity Backup server.

Please do not stop the backup job when an error is flagged.


Alternatively, if the circular logging option must be enabled, please re-create a new MS Exchange Server backup set, and configure the backup schedule to perform a Full database backup everyday (with In-file Delta option enabled).
 
exch-backup-schedule.png
Figure 4.0 - ServosityProuser interface (Backup Schedule Properties)

No transaction log backup can be performed with the circular logging option enabled.
          Also See: http://msdn.microsoft.com/en-us/library/aa579094%28v=exchg.140%29.aspx