Hi Paul,
The Backup Process is completed successfully without any Event ID 2137. But the transaction logs are still not truncated if the MBX Server on which we run the wbadmin script host the Healthy Database Copy (Although i edited the registry as your guide).
So what is the problem here ? The case is:
– If we edit the registry: We can backup successfully without error but the LOG is still not truncated !!
– If we doesn’t edit the registry: We can’t backup successfully with event ID 2137 !

Do you see that event ID in your event log?

I am waiting your reply or comment.

Thanks again for this nice explanation. I have these errors as well, event id 2137:
RPC request to the Microsoft Exchange Information Store service for log truncation failed for database YEF-NL1-2010AM1S162. Error: 4294965485.
They are filling up the event viewer of my mbx servers but that is the whole day and not (only) during the backup. We use Commvault for backup and when I look at one of the databases that is backed up, the logfiles are cleaned.
What can this be? Do I need to apply the fix as well?
Thnx!

1-i use Windows server 2008R2 (windows backup) for doing full backup
2-yes everytime i took fullbackup , timestamp updates on the database
3-there is no error but information event id 9827 ,event id 2006

i have been three weeks doing research on this issue , Logs are filling up our drives , i cound’t find solution on this !!!!!!

thanks

Which backup product?

Did the lastfullbackup timestamp update on the databases?

Were there any event log errors or warnings?

You’ll need to check that with EMC Networker’s documentation.