General Discussion

SnapCenter Exchange Backup Logs not truncating

JVandermark

Hi All, just wanted to toss this to the community since support from netapp and microsoft have not been very helpful. We configured a full backup + log. Exchange shows a full backup completed but logs are not truncating as we expected. this is a new exchange 2016 environment. any gotchas or anything obvious that we could be missing? Thank you in advance.

1 REPLY 1

Re: SnapCenter Exchange Backup Logs not truncating

mrahul

Hi 

 

 Are you using SnapCenter version 4.1? 

SnapCenter 4.1 release notes call out this known issue for the release with BUG ID 1162598.

community.png

 

 

 

Please see NetApp public report - https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1162598

 

TITLE: Exchange log truncation failing though the backup is completed
DESCRIPTION:
Microsoft Exchange does not truncate the logs even after a full backup is completed by the Exchange plug-in.
WORKAROUND:
Before a full backup is triggered, check to see that all Exchange plug-in nodes are updated with the latest Microsoft Windows Server hotfixes. Additionally, VSS writers need to be in stable state. Please check the writer state using the following command: “vssadmin list writers”. If the Microsoft Exchange Writer is not in stable state, please wait for it to become stable or restart the Microsoft Exchange Information Store and Microsoft Exchange Replication services.

After a full backup has been triggered, check for the following error signature in the event logs:
"Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.(=accessed denied). This is often caused by incorrect security settings in either the writer or requestor process"

If this message appears, follow the steps given in the link “https://social.technet.microsoft.com/Forums/en-US/2ed82bbe-90f2-43e3-9205-005801dd346f/volume-shadow-copy-service-error-unexpected-error-querying-for-..." and trigger a full back up again to resolve the log truncation issue.

NOTES:
Microsoft Exchange truncates the logs only when the following conditions are met:
• All the copies are in healthy state.
• The log file is below the checkpoint.
• The other non-lagged copies of the database agree with deletion.
• The log file has been inspected by all lagged copies of the database.

 

G2 Review Banner
All Community Forums
Public