+6Greetings!
We’re performing a new backup of an Exchange 2019 database. Before running the backup, we had ~ 4000 log files. After, ~400. This sounds good. But we note that the log files remaining are indeed from the last 2 weeks (beginning of the month). Any clue why some files would remain.. ?
Thank you for your time!
Best answer by Chris Hollis
You’d have to ask that question on the MSFT community site as the actual truncation process is carried out by the exchange application.
Commvault simply sends the request to truncate the logs at the conclusion of the backup operation.
I’d say, it’s likely something to do with replication (assuming this is a DAG environment) and perhaps one of the replicas isn’t updated yet so truncation hasn’t fully completed… I’m not an exchange admin however so cannot say for sure!
If you manage to get thru to MSFT and they give you an answer, we’d appreciate if you could share the findings here to help out others!
Any questions please let me know.
Regards,
Chris
+14
You’d have to ask that question on the MSFT community site as the actual truncation process is carried out by the exchange application.
Commvault simply sends the request to truncate the logs at the conclusion of the backup operation.
I’d say, it’s likely something to do with replication (assuming this is a DAG environment) and perhaps one of the replicas isn’t updated yet so truncation hasn’t fully completed… I’m not an exchange admin however so cannot say for sure!
If you manage to get thru to MSFT and they give you an answer, we’d appreciate if you could share the findings here to help out others!
Any questions please let me know.
Regards,
Chris
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
