none
SBS 2008 Backup Failure - Help please

    Question

  • Hi

    I have just taken on an SBS2008 server for a new client. It doesn;t look like many of the updates have been applied in the last year. However more importantly the backups have stopped working over the last 3 weeks (hence the call to me).

    I have looked in the event log, and the Backup is failing about 6-10mins into it. It is stopping with the 8001 (i think) error which is where the Shadow Copy is timing out

    I have run a VSSAdmin list writers and all apart from 1 is failing. (This was done after a reboot)

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Waiting for responses.
    These may be delayed if a shadow copy is being prepared.

    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {629d2035-0478-48e7-8da8-af71d55d10d9}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'SharePoint Services Writer'
       Writer Id: {c2f52614-5e53-4858-a589-38eeb25c6184}
       Writer Instance Id: {38d04227-5912-4d24-a584-80d5f3ba862d}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {e8d9bc74-1f47-455b-9802-58907733e53c}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {c486327d-2470-4157-8907-14bc0e4a3479}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {4397d125-83b3-445f-9ff9-3e5e48ecbb8c}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {d132d8a8-efc1-4f3c-9440-1a697b098262}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {0f1db7f6-6d0f-4c5c-997a-23ae7cf765f1}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {4a4952d8-dd2f-4de7-a829-7d9e97e002f1}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {071300fb-a766-4e04-84bf-833581026957}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {07782005-a5f8-4492-a086-e166a5a244a5}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {9e4e5de8-6d6d-47bc-9f30-d83d4eba02fe}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {bcf0c67d-6f22-4214-a540-1c51b9c09a76}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {e250ae40-63dd-4394-b405-f530c6e1c2f8}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'SPSearch VSS Writer'
       Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
       Writer Instance Id: {f85161d3-2708-4bef-ba5e-16f9db4447e4}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {3a6b3ee7-5c78-4092-b492-18f54259b043}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {0e8817cf-6fcd-4c88-b776-dc0b128ab566}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'TS Gateway Writer'
       Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
       Writer Instance Id: {9b4a6d04-c8a4-499e-99f7-7c25f2d2707b}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {b6c4927c-e294-4a8d-9d9d-295598bbe8f8}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {e38c5ecf-2c98-4dc9-972c-7f60fc262834}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'NPS VSS Writer'
       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
       Writer Instance Id: {fc443566-28aa-40e3-a2e8-9b50d7fee546}
       State: [9] Failed
       Last error: Timed out

     

    The backups were running fun upto begining of January, and then suddenly started doing this every backup. I have tried both the automatic and manual start of the backup. (This is all through the SBS console)

    Any help how to fix this would be greatly appreciated.

    I have seen some other forums talk about re-registering DLL's, but also seen others saying don;t ever do that. I am looking to talk them into a server upgrade to SBS2011 but that wont be to April, so i need something that gets things back up and running.

    THanks

    Tris

    Sunday, February 03, 2013 11:11 PM

Answers

All replies

  • Hi Tris:

    No problems with re-registering the dlls.  Are there any other events in the logs or anything of help in the backup report?


    Larry Struckmeyer[SBS-MVP]

    Monday, February 04, 2013 12:11 AM
  • I had a problem like this with one of our clients last year.  They too had an SBS 2008 server and the backups all of a sudden started to fail just a few minutes in (although it did fluctuate occasionally).

    Definitely check the event logs as Larry suggests - when I checked this on our clients server last year there were additional errors - initially these pointed to the backup drive(s) so it's worth trying a different backup drive if you have one.  After even further scrutiny the logs picked up on some disk errors/bad sectors on the server's HDD.  I spoke to Microsoft about it who advised me to try a chkdsk/r from WinRE mode but advised that if that failed then I should replace the HDD's and restore the entire system.

    In the end the client chose to replace the server - it had been misconfigured by the original company anyway so they killed two birds with one stone.

    Keep us updated on how it goes.


    MVP wannabe. I don't work for Microsoft - I just use their products.

    Monday, February 04, 2013 12:13 PM
  • Hi Thanks Larry

    There are no other problems I see, only the VSS timing out.

    There are no disk error reports on either the backup media (they have arotation of 5 throughout a week, Mon, Tue, Wed, Thu, Fri) fails on all - There is an alert they are close to getting full, but there has been a successful backup during these alerts (I plan on getting a few clean HDD's and archive the old ones, but this doens;t seem to link to the issue???

    From what I can see about the backup logs there are no other errors being listed. As I say I only ran the VSSAdmin List Writers as I saw other people mention it.

    So Larry do you suggest that re-registereing the DLLs would be the solution? If so, what is the official thing I should do to do this? as obviously I trust here far more than any other forum.

    Thanks

    Tris

    Monday, February 04, 2013 3:27 PM
  • Hi,

    Re-register dll files may not help fixing the issue but at least it will show some errors if specific file is missing/service is corrupted. So you could have a try and see if there is any error occurs:

    http://blogs.technet.com/b/csstwplatform/archive/2012/05/03/how-to-repair-vss-in-windows-2008.aspx


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Tuesday, February 05, 2013 8:42 AM