I have seen similar posts about this issue but none of which that I have seen address this issue on the Win Server 2012 DC/Exchange 2013 RTM platforms.
I am attempting to get my backup software to perform an appropriate backup of my Exchange 2013 server. I am currently using Symantec Backup Exec 2015 (Version 14.2).
Each back up I run consistently fails as soon as it attempts to back up my Exchange Mailbox Database files. The errors for BE 14.2 is also consistent over the 30 backups that I have ran and failed to complete.
"V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\[Server_Name.local]\Microsoft Information Store\Mailbox Database 0936435715". Snapshot technology used: Microsoft Volume Shadow
Copy Service (VSS).
Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error.
Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1)."
I have worked extensively with Symantec's tech support and we have moved to the issue being with the server itself and not Backup Exec, especially since all of my other servers are backing up properly. After reading up on Writers I logged in to our mail server and ran a Admin CMD and ran the command VSSADMIN LIST WRITERS.
The all of my writers except the following showed as stable.
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {55b98a96-98f3-48e1-b2e8-4b94dc769ef0}
State: [7] Failed
Last error: Retryable error
Symantec informs me that with this writer being unstable, all of my backups will continue to fail and that they cannot assist me any more unless this issue is resolved.
At the current time our ability to apply the Cumulative updates and service packs to Exchange 2013 is not possible. We don't have any one on hand that has enough knowledge in Exchange to do this work and we are a bit stuck.
Any help with a hotfix that has been released or some kind of work around would be amazing. I just wish I had the knowledge to figure this out on my own, but after 9 days of trying to fix this and being told by Symantec that it is a Windows/Exchange problem.
Other recent topics
