https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMTkxIiwiaGFzaCI6Ijk5ZWE0YTZhLWQxMzYtNDhkOC04NDM1LWRmYTFkZTI2Njc1NSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Microsoft Exchange logs are not being truncated in Veeam Backup and Replication 9.5

Challenge

After upgrade to version 9.5.0.711 Microsoft Exchange logs no longer get truncated. In the Windows Application event logs you might get an error with an event ID 2034.

Cause

This is a known issue in build 9.5.0.711. If you disable Microsoft SQL logs truncation in Job properties then Microsoft Exchange logs truncation will be disabled too.
Exchange logs truncation is regulated by a single boolean when you call SetBackupSucceeded() WinAPI with Exchange VSS writer writerID.
When that boolean is set to true Exchange VSS writer goes ahead and truncates the logs, and v9.5.0.711 sets this boolean to false based on SQL configuration in Job properties.

Solution

Enable SQL log truncation in Job properties and this will allow Exchange logs to be truncated.
KB ID:
2191
Product:
Veeam Backup & Replication
Version:
9.5.0.711
Published:
2016-11-16
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.