-
Title
Exchange log truncation jobs are shown as successful, but logs are not being truncated -
Description
Snapshot transfer with log truncation job appears to run successfully, but Exchange logs are not truncating either as part of the nightly jobs or when forced manually from the Rapid Recovery Core console. Rapid Recovery and Exchange are both patched up to appropriate levels.
SCENARIO 1:
The command "vssadmin list writers" show the Microsoft Exchange writer as 'Stable' but line shows the following error 'WriterErrorRetryable'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:
Log Name: ApplicationSource: MSExchangeReplEvent ID: 2034Task Category: Exchange VSS WriterLevel: ErrorDescription:The Microsoft Exchange Replication service VSS Writer (Instance 00000000-0000-0000-0000-000000000000)failed with error 8007064A when processing the backup completion event.Log Name: ApplicationSource: MSExchangeReplEvent ID: 2112Task Category: Exchange VSS WriterLevel: ErrorDescription:The Microsoft Exchange Replication service VSS Writer instance 5c5213f6-be43-4da3-92b6-773e623c2dbffailed with error code 80070015 when preparing for a backup of database 'DB_NAME'.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:
Source: MSExchangeRepl
ID: 2047
Date: MM/DD/YYYY HH:MM:SS
Description: The Microsoft Exchange Replication service VSS Writer instance <UID> has successfully completed a backup of database '<database name>'. No log files were truncated for this database because the backup type was a copy backup or a differential backup.SCENARIO 4:
A third-party application that also uses VSS writers is scheduled to run at a similar time to the AppAssure schedule. Running the command "vssadmin list writers" may list the 'Microsoft Exchange Writer' as being Failed or Waiting for completion. A Windows application error event could be logged such as the following:
Source: ESE
ID: 2007
Date: MM/DD/YYYY HH:MM:SS
Description: "Information Store (XXXX) Shadow copy instance Y aborted" -
Cause
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, the Exchange databases do not freeze successfully and consequently logs will not truncate.
-
Resolution
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:
- Open Registry and locate the following Registry Key branch.
- "HKLM\Software\Microsoft\ExchangeServer\v15\Replay\Parameters"
- Check if the following registry key is there, if not there, you can create a DWORD value = EnableVSSWriter and assign value = 1
- Restart the Exchange replication service.
- 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:
- From within the Exchange Admin Center, go to Servers
- Databases
- Select your Mailbox DB
- Hit Edit
- Select Maintenance
- Select Enable Circular Logging
- 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
SOLUTION SCENARIO 4:
Disable or re-schedule the third-party application snapshot, so it won't run while Rapid Recovery job are expected to run.
- Open Registry and locate the following Registry Key branch.
