Exchange logs not being truncated

KB ID: 1878
Product: Veeam Backup & Replication | 10 | 11
Published: 2014-04-21
Last Modified: 2022-01-14
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

This KB provides troubleshooting advice for investigating an apparent Exchange log truncation issue.

Cause

Exchange truncation may not occur for the following reasons:

  • The Veeam Backup & Replication job is not configured trigger truncation.
  • The VSS operation occurring during the job is not notifying the Exchange VSS writer that a backup has occurred.
  • The Exchange VSS writer is receiving notification that a backup has occurred, but an issue within the Exchange software prevents truncation.

Solution

Make sure truncation is enabled within Backup Job

VMs processed by Veeam Backup & Replication must have Application-Aware Processing enabled to perform truncation.

Confirm this by editing the job, going to the Guest Processing tab, and ensuring the Enable application-aware processing is checked. 

In addition to making sure Application-Aware Processing is enabled, check that truncation is enabled at the granular per VM level. Click the [ Applications... ], then in the window that opens, highlight the Exchange server and select [ Edit ]. Within the processing setting window, make sure that the job is set to either "Require successful processing (recommended)" or "Try application processing, but ignore failures," then make certain "Process transaction logs with this job (recommended)" is selected.

Truncation Enabled

Make sure the job is Notifying the Exchange VSS Writer

On the Exchange server that was backed up, navigate to C:\ProgramData\Veeam\Backup and open the most recent VeeamGuestHelper log file.

Within the VeeamGuestHelper log file, search for: "Notifying writers about the 'BACKUP FINISH' event."

After that line will be a list of each VSS writer notified of the 'BACKUP FINISH' event. When the Exchange VSS writer is notified that it has been backed up, it handles the truncation process. There may be multiple lines regarding the Microsoft Exchange VSS Writer, the most important of which is the one that will end in "Ok." which signifies that notification was successful. 

Example:

Notifying writers about the 'BACKUP FINISH' event.
  Truncate logs: [true].
    Notifying a VSS writer about the successfully backed up components. Writer name: [Microsoft Exchange Writer]. Class ID: [{guid}]. Instance ID: [{guid}].
      Writer was notified about the successfully backed up component. Component's logical path: [Microsoft Exchange Server\Microsoft Information Store\EXCH-MBX]. Component name: [guid].
      Writer was notified about the successfully backed up component. Component's logical path: [Microsoft Exchange Server\Microsoft Information Store\EXCH-MBX]. Component name: [guid].
    Notifying a VSS writer about the successfully backed up components. Writer name: [Microsoft Exchange Writer]. Class ID: [{guid}]. Instance ID: [{guid}].. Ok.

Entries about other writers were removed from this example for conciseness.

 

  • If the Microsoft Exchange VSS Writer is being notified of the BACKUP FINISH event, the investigation should shift to reviewing the Windows Events for entries from the Exchange application regarding truncation and backup events.
  • If the Exchange VSS writer is missing from the log or failed during the VSS operations, investigate the VSS writer's current state. Run the following in an Administrative Command Prompt on the Exchange server:
    vssadmin list writers
    
    If the writer is not listed or is in a failed state, the Exchange server should be rebooted, then it should be verified that the writer returns and shows as Stable/No Error. Once this has been done, retry the Veeam job and verify log truncation.

Review Event Viewer on the Exchange Server

Within Event Viewer on the Exchange server, look for any Exchange related errors. If the Exchange configuration utilizes Distributed Availability Groups (DAG), the replication process between the different nodes can prevent log truncation if there are any errors. These will show with the event source MSExchangeRepl. Generally, if there are errors, these are not caused by Veeam Backup & Replication processes and should be addressed in the Exchange and/or Windows configuration. To isolate whether the issue is caused by a Veeam Backup & Replication process or within VSS itself, enable the Windows Backup role on the Exchange server and run a native Windows Backup (system state). Alternatively, test manual shadow copy creation and truncation as documented here: KB1980: Using the Diskshadow Utility to manually test VSS operations

More information

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.