Exchange log truncation jobs are shown as successful, but logs are not being truncated (4043174)

Exchange log truncation jobs are shown as successful, but logs are not being truncated

   - 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:

SCENARIO 2:

The Microsoft Exchange Writer is missing in the output of command vssadmin list writers, 

SCENARIO 3:

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."="">

Exchange logs are not truncate, either due to Microsoft Exchange VSS writer is not enable or writer is failing to back up an unmounted Exchange database. Rapid Recovery is able to get good snapshots from Exchange server's volumes, however as the Microsoft Exchange VSS writer is missing or in failed state, MS Exchange is not aware their database are backup and ready for log truncation.

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:

1. Open Registry and locate the following Registry Key branch.
   • "HKLM\Software\Microsoft\ExchangeServer\v15\Replay\Parameters" 
2. Check if  the following registry key is there, if not there, you can create a DWORD value = EnableVSSWriter and assign value = 1
3. Restart the Exchange replication service.
4. If the Microsoft Exchange VSS writer is still not showing up, reboot the Exchange server.

 

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.

• Exchange Admin Center: 
  1. From within the Exchange Admin Center, go to Servers
  2. Databases
  3. Select your Mailbox DB
  4. Hit Edit
  5. Select Maintenance
  6. Select Enable Circular Logging
  7. And hit Save.

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.

• Exchange Shell: Please refer to the following KB article to see the steps to enable "Circular Logging" setting for a Exchange Database.
  • Exchange 2013/2016: Configure circular logging for a mailbox database - Microsoft Docs
  • Exchange 2019: Enable Circular logging on a Database - Microsoft TechNet Articles