We help IT Professionals succeed at work.

Constant VSS Exchange Writer Failures in Backup on SBS 2011

PaulD77
PaulD77 asked
on
Hey All,

I have an SBS 2011 machine, Exchange 2010 which I'm backing up with Symantec Exec 2010 R3.  I am constantly getting a failure with my exchange backup, specifically the VSS writer is failing.  I have followed both Symantecs advice of rebooting the server and Microsofts advice of dimounting and remounting my exchange data base, stopping the info store service and restarting.  Nothing Works!  Below is my error, any advice is appreciated.

0XE0001904 - A failure occurred querying the Writer status.  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: Failed during prepare snapshot operation (8).
Final error category: Security Errors

A review of the event logs on the Exchange server at the time of the failure reports


Event ID : 9840
Source : MSExchangeIS
Type : Error
Message : An attempt to prepare the storage group '<name>' for backup failed because the storage group is already in the process of being backed up. The error code is -2403. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.)

Event Type: Error
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9814
Description:
Exchange VSS Writer (instance f21a24d6-edc6-4c58-ac4e-e3c7bf2dee2b:26) failed with error code -2403    when  preparing the database engine for backup of storage group 'First Storage Group'.

Event Type: Error
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9609
Description:
Exchange VSS Writer (instance f21a24d6-edc6-4c58-ac4e-e3c7bf2dee2b:26) failed with error code -2403 when preparing for Snapshot.

Comment
Watch Question

Network Administrator, Network Consultant
Top Expert 2011
Commented:
Method 1: Dismount all databases in the storage group
Use this method if the event ID 9840 that was logged on the Exchange 2007 server contained error code 2403.

To dismount all databases in the storage group, follow these steps:

Click Start, point to All Programs, point to Exchange Server 2007, and then click Exchange Management Console.

Expand Server Configuration, and then expand the storage group that is listed in the event ID 9840 message that was logged on the Exchange 2007 server.

Right-click each database in that storage group, and then click Dismount Database.

Click Yes to confirm the operation.

After the dismount operation is complete, right-click the database again, and then click Mount Database.

Try to perform the backup operation that resulted in event ID 9840.

If this method does not resolve the problem, try method 2.


Method 2: Restart the Microsoft Exchange Information Store service

Use this method if the event ID 9840 that was logged on the Exchange 2007 server contained error code 1293. Use this method if Event ID 9607 was logged on Exchange 2003. Additionally, use this method if method 1 did not resolve the problem.

To restart the Microsoft Exchange Information Store service, follow these steps:
Click Start, point to All Programs, point to Administrative Tools, and then click Services.
Right-click Microsoft Exchange Information Store, and then click Restart.
Try to perform the backup operation that resulted in event ID 9840.

Author

Commented:
Yes, I've tried both of these steps as according to Microsoft, but The VSS writer continues to fail.
Maen Abu-TabanjehNetwork Administrator, Network Consultant
Top Expert 2011

Commented:
restart your exchange server as try .. just do it and let me know , we want to work around just no more

Author

Commented:
I've rebooted this machine many times after follwoing the directions.  Eventually the VSS again fails, and I don't know whats causing the failure.  Could any 3rd party software like AV stop the VSS writer?
Maen Abu-TabanjehNetwork Administrator, Network Consultant
Top Expert 2011

Commented:
its possible this problem with microsoft you need to workaround everything , try to stop the anti virus , and tell me what will happened , from my side am still trying to help you .. good luck :)

Author

Commented:
I will give it a shot, unfortunatly, can't restart this machine until later in the day.  Thanks
Maen Abu-TabanjehNetwork Administrator, Network Consultant
Top Expert 2011

Commented:
there is 2 tries :

first try :
follow this registry key :
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Shadow Copy Components\
right click on the key then create new key call it :
Additional Not Authorized Writers key
on this key on right pane create new registry value string value , call it :
FSRM
and set the value :

{12ce4370-5bb7-4c58-a76a-e5d5097e3674}

then restart vertas service and try again .

second try :

1- first one :


1) Remove all Backup jobs, Policies and selection list.
2) Restart Information Store Services
3) Re-create all backup Jobs ,Policies and Selection list.
4) Then try backing up and let us know whether its work
Shivkumar SharmaOperations Delivery Manager
Commented:
Apply all windows updates/patches and all Backup Exec updates/patches.

Make sure no other backup jobs are running

Hope this helps some.

Author

Commented:
Thanks havent tried to edit registry yet or remove backup jobs.  Server and Exec are fully up to date.  Thanks!  I will give it a shot and let you know tomorrow.
Maen Abu-TabanjehNetwork Administrator, Network Consultant
Top Expert 2011

Commented:
just workaround registry key that i told you before its should solve the problem , because its known bug for symantec
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates ?

Cleanup Volunteers please look at this question and do the needful so that it does not remain unattended
Shivkumar SharmaOperations Delivery Manager

Commented:

Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question. Thank you sir
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question. Thank you sir

Kind Regards and Happy New Year in Advance
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question. Thank you sir

Kind Regards and Happy New Year in Advance
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question.

Thank you sir

Happy New Year 2012
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question.

Thank you sir
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question.

Thank you sir
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question.

Thank you sir
Shivkumar SharmaOperations Delivery Manager

Commented:
Any Updates Please, Since the Question is going unattended, dont let it go unattended and please do the needfull. if we have not come up to your satisfaction then please ask for help from all the experts or if need be please accept the answers or delete the question.

Thank you sir

Author

Commented:
Sorry about the delay but no solutions worked..this was only happening on incrmental backups...Symantec claimed it was a microsoft issue, microsofts solutions to this didn't work, changing the registry didn't work.


After a server reboot, the incrmental would run ok once or twice before it started failing again.

I just worked around it by getting rid of incrmental in symantec and only running full backups locally...my off site backup runs both full and incrmental.

I will award points for your patience and help though