The Exchange log truncation job shows that it has completed successfully in the Core's event log, but the Exchange logs are not being truncated on the Exchange server.
In the AppRecoveryPM.log, the MS Exchange Writer appears with the following status:
- Writer 'Microsoft Exchange Writer' State=Stable Failure=WriterErrorRetryable (Ignoring status of ignored writer)
"Windows Event Viewer - Application" is showing the following error when snapshot is running:
The Microsoft Exchange Writer is missing in the output of command vssadmin list writers,
Core show the Exchange Logs truncation successful but the Exchange logs weren't truncated. Windows Application Events show the following event:
EVENT ID 2047 -- "No log files were truncated for this database because the backup type was a copy backup or a differential backup."
<img data-cke-saved-src="https://prod-support-images-cfm.s3.amazonaws.com/KB_1-80ECZYQ_Windows%20Event%20Log%20Truncation.png " src="https://prod-support-images-cfm.s3.amazonaws.com/KB_1-80ECZYQ_Windows%20Event%20Log%20Truncation.png " alt="" no="" log="" files="" were="" truncated="" for="" this="" database="" because="" the="" backup="" type="" was="" a="" copy="" or="" differential="" backup."="">
SOLUTION SCENARIO 1:
In order to allow Rapid Recovery to successfully truncate the Exchange logs, the database need to be removed or remounted.
Please contact Microsoft Support if the Exchange logs are not yet being truncated after removing or remounting the offending Exchange Database and the Exchange VSS Writer is still showing error "WriterErrorRetryable".
SOLUTION SCENARIO 2:
Enable the MS Exchange VSS Writer:
SOLUTION SCENARIO 3:
"Circular Logging" for the Exchange Database can be enabled from Exchange Admin Center or Exchange Shell. Below are the steps to enable "Circular Logging" for Exchange 2013/2016/2019.
NOTE: The Exchange Database needs to be dismounted and remounted in order to apply the change on the Exchange database, it is prefer to do dismount the DB afterhours.