Exchange logs not being truncated

Challenge

Cause

There are various causes for failure of truncation operations, both in the Veeam Backup & Replication application, and within the Exchange Windows guest itself.

Solution

Make sure that the job is set to use Application-Aware Image Processing and proper credentials are being used:



You will then want to check to make sure that transaction logs are set to be truncated on successful backup:



If this is set correctly, make sure that the command is being sent to the Exchange server. You can verify this by analyzing the VeeamVSSSupport.log (VeeamGuestHelper.log in VBR v8+) file that can be found in the following location:

• Windows 7/8 Generations: C:\ProgramData\Veeam\Backup
• Windows XP/2k3: %allusersprofile%\Application Data\Veeam\Backup

 
If the command is being sent, you should see the following in the log file:
INFO                Processing external FinishSnapshot command.
                         Notifying writers about the 'BACKUP FINISH' event.
                         Truncate logs: [true].
                         Processing external FinishSnapshotEX command, job id ‘{job ID}’, is logs truncation enabled yes.. ok.
 
If this is being sent, we will want to look at Windows event logs for any possible errors as well as the VSS writers.
 
Run the following in an elevated CMD prompt and verify the Exchange writer is present:
   
If the writer is not being 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.
 
Within the event logs, look for any Exchange based errors. If the Exchange configuration is utilizing 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. If there are errors here, generally these are not affected by Veeam Backup & Replication processes and should be addressed in the Exchange and/or Windows configuration. To isolate whether the issue is caused within Veeam Backup & Replication processes or within VSS itself, enabling the Windows Backup role on the server and running a native Windows Backup (system state) will generally isolate the issue to the operating system.

More Information