Exchange 2013 - VSS Full Backup issues

Chris Molloy
Chris Molloy used Ask the Experts™
on
Good day,

We are running into some issues when attempting to complete a full VSS backup of one of our Exchange Servers.

The job will complete with warnings, but then we cannot truncate our logs.

Included is a list of the failed files:

Writer Failures
Writer Id: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}
Instance Id: {C67B8D76-4D07-427C-9086-3859A787CA7A}
Writer Name: Microsoft Exchange Writer
Writer State: 5
Failure Result: 800423F3
Application Result: 1
Application Message: (null)
   Component: 8f3d2a54-966f-4cb1-8d9e-f948b532ee51
   Logical Path: Microsoft Exchange Server\Microsoft Information Store\BKEXG01
   Component Result: 800423F3
   Component Message: (null)
       File Spec: E:\EXGDB\BKEXGDB01.edb Recursive: 0
       File Spec: D:\Logs\\E01*.log Recursive: 0
       File Spec: D:\Logs\E01.chk Recursive: 0
   Component: 011c955a-a0c9-4572-86dd-e5bf6d8389b1
   Logical Path: Microsoft Exchange Server\Microsoft Information Store\BKEXG01
   Component Result: 800423F3
   Component Message: (null)
       File Spec: E:\BKPUBDB\IQPUBDB.edb Recursive: 0
       File Spec: D:\BKPUBDB Logs\\E00*.log Recursive: 0
       File Spec: D:\BKPUBDB Logs\E00.chk Recursive: 0

Did some basic trouble shooting for Exchange 2013 VSS backups and ran the following command on the Exchange Server:

VSSadmin list writers

This provided the following result:

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {c67b8d76-4d07-427c-9086-3859a787ca7a}
   State: [1] Stable
   Last error: Retryable error

I restarted the information store service on the exchange server but the error is still showing as retryable error.

Any suggestions or help would greatly be appreciated.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
NoahHardware Tester and Debugger

Commented:
Hi there! :)

I think this issue could be because the DS-Client can only restore an Microsoft Exchange Mailbox Database if the destination database for the restore is in a ‘mounted’ state. You will need to restore to an alternate location: Restore logs to a "restoredlogs" folder, then restore the Exchange DB files to the physical location.
Saif ShaikhServer engineer

Commented:
Try to create a new database and create 2-3 mailboxes in IT. Then send some test emails to the test users in the new database. Add the database copy of the new database in dag. Then take a full backup and then check if incremental is successful.

This will isolate issue with database OR backup.

Then only option is to move the mailboxes from affected database to new database.
Senior Administrator
Commented:
Edit mentioned registry path and set it to 1 and restart the "Microsoft Exchange Replication" service will bring back the Microsoft Exchange VSSWriter to normal.

You can verify after restarting the service in cmd "vssadmin list writers"

"HKLM\Software\Microsoft\ExchangeServer\v15\Replay\Parameters\EnableVSSWriter"
Chris MolloyNetwork Administrator

Author

Commented:
Thank you for all your replies, much appreciated.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial