nabz0r Veteran Posted March 4, 2011 Veteran Share Posted March 4, 2011 Hey guys, I get the this message when backing up. I tried to solve it with this but I still get the same message. Anyone had this problem before? Any suggestion of solving it? Thank you in advanced! :) Job Completion Status: Job ended: den 4 mars 2011 at 01:56:10 Completed status: Failed Final error code: a000fec9 HEX Final error description: A failure occurred accessing the Writer metadata. Final error category: Resource Errors Errors: Backup - Shadow?Copy?Components Shadow?Copy?ComponentsA failure occurred accessing the Writer metadata. Link to comment https://www.neowin.net/forum/topic/980194-windows-server-2003-backup-problem/ Share on other sites More sharing options...
sc302 Veteran Posted March 4, 2011 Veteran Share Posted March 4, 2011 looks like it is your vss writer. The only way to reset it is to reboot the server. On the server that is having issues with the backup (not the backup server) open up a cmd prompt and type in vssadmin list writers If everything is Stable as shown here: Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {9e9e19d8-7c23-4a08-9c83-66924c6ca537} State: [1] Stable Last error: No error Then you don't have to reboot. Unfortunatly the only way to change the state back to stable is if you reboot the problem server. There is no way on any windows os to reset the writer status without a reboot (I have tried). Link to comment https://www.neowin.net/forum/topic/980194-windows-server-2003-backup-problem/#findComment-593757406 Share on other sites More sharing options...
nabz0r Veteran Posted March 4, 2011 Author Veteran Share Posted March 4, 2011 On 04/03/2011 at 14:14, sc302 said: looks like it is your vss writer. The only way to reset it is to reboot the server. On the server that is having issues with the backup (not the backup server) open up a cmd prompt and type in vssadmin list writers If everything is Stable as shown here: Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {9e9e19d8-7c23-4a08-9c83-66924c6ca537} State: [1] Stable Last error: No error Then you don't have to reboot. Unfortunatly the only way to change the state back to stable is if you reboot the problem server. There is no way on any windows os to reset the writer status without a reboot (I have tried). Yes, I figured out after searching in google for 1 hour, so I went down and rebooted the server and then I tested the "Test Run" twice and they worked, I will wait until tomorrow or monday and see if it's gonna work or not. Thanks for the replay though. :) I have NEVER had this problem before. Link to comment https://www.neowin.net/forum/topic/980194-windows-server-2003-backup-problem/#findComment-593757520 Share on other sites More sharing options...
sc302 Veteran Posted March 4, 2011 Veteran Share Posted March 4, 2011 It is more common than you know. Link to comment https://www.neowin.net/forum/topic/980194-windows-server-2003-backup-problem/#findComment-593757574 Share on other sites More sharing options...
Recommended Posts