none
Windows Server2008r2 System State backup problem

    Question

  • Hi.

    We have a windows 2008r2sp1 server and have a problem with system state backup.

    For backup we use Symantec backup exec 2010r3Sp2.

    Sometimes system state backup completed without errors,but sometimes failed.

    After backup failed - i can see only this errors, no other errors in log:

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {d1dff694-2a28-48fa-a412-6ae66d3bd00b}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {776c37ec-8988-4d77-a5ed-ecd103fd1d4f}
       State: [9] Failed
       Last error: Timed out

    other writers are stable and without errors.

    We've opened a case in symantec, but they told us that it is a microsoft problem - they tried to make a system state backup with wbadmin and it failed with error:

    The backup operation that started at '‎2012‎-‎04‎-‎10T07:18:10.443112200Z' has failed with following error code '2155347997'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    After the third attemp it completed without errors.

    I read a lot of forums, tried to reregister writers, but can't find a solution.

    by the way we don't have the system reserved partition, according to this threat - http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/887451be-0e3f-4697-b807-131b3941817d

    Any ideas?

    Monday, April 23, 2012 8:37 AM

Answers

  • Suggestion 1: Run chkdsk /f C: and then restart the server and repeat the execution of the vssadmin list writers command.

    Suggestion 2: Run Disk Defragmenter on the C: drive and then repeat the execution of the vssadmin list writers command.

    Follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following key in the registry:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnap
    3. On the Edit menu, point to New, and then click DWORD value.
    4. Type MinDiffAreaFileSize, and then press ENTER.
    5. On the Edit menu, click Modify.
    6. Type 900, and then click OK

    For more information refer to the following article:

    http://support.microsoft.com/kb/826936

    Please feel free to let us know if you have any question or concern.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by PEgorov Wednesday, May 02, 2012 5:28 AM
    Monday, April 23, 2012 1:53 PM
  • Hi,

    Oh, according to your description, your server had installed Symantec backup software, this is a known issue, this problem is likely related to third-party backup software.

    Based on previous experience, I suggest you uninstall the other backup software and retry operation, as the windows  server backup is not compatible with Symantec.

    You could do a testing, try to uninstall Symantec and then retry to back up system state.


    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

    Thursday, April 26, 2012 3:44 AM
    Moderator

All replies

  • Suggestion 1: Run chkdsk /f C: and then restart the server and repeat the execution of the vssadmin list writers command.

    Suggestion 2: Run Disk Defragmenter on the C: drive and then repeat the execution of the vssadmin list writers command.

    Follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following key in the registry:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnap
    3. On the Edit menu, point to New, and then click DWORD value.
    4. Type MinDiffAreaFileSize, and then press ENTER.
    5. On the Edit menu, click Modify.
    6. Type 900, and then click OK

    For more information refer to the following article:

    http://support.microsoft.com/kb/826936

    Please feel free to let us know if you have any question or concern.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by PEgorov Wednesday, May 02, 2012 5:28 AM
    Monday, April 23, 2012 1:53 PM
  • Thanks for replay

    I'll trie your solution and come back later with an answer, was it helpfull or not.

    Tuesday, April 24, 2012 5:49 AM
  • Hi,

     

    Additionally, please refer to the following KB:

    http://support.microsoft.com/kb/980794

     

    BTW, please ensure that the path length of the selected files are no longer than 260 characters.

    1. Check that the followings are true:

     

    • Make sure that the target volume has no shadow copy before the backup starts. 
    •  If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups. 
    • Periodically check that no other user or program maintains a shadow copy on the target volume. 
    •  Do not keep volume level backups and system state backups in the same location. 
    • The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes

     

    2.Try to add the following value in registry:

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\

    Name: AllowSSBToAnyVolume

    Data type: DWORD

    Value data: 1

     

    If the issue persists, please help collect the following information:

     

     

    Vssadmin list writers

    Vssadmin list providers


    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

    Tuesday, April 24, 2012 6:28 AM
    Moderator
  • I applied all your recommendations, but it didn't help. The errors still persist. Sometimes System State backup completed,sometimes not . For tests I used Windows backup. With Symantec backup exec -the same problem.

    The backup operation that started at '‎2012‎-‎04‎-‎25T08:39:42.195948200Z' has failed with following error code '2155347997'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. - no other Logs

    List writers >>

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

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {555a077b-7e73-4fee-a398-b3a47ac681ad}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {595804fe-eff1-41c6-ba4e-10226da831d9}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {fd4e76b4-29b0-44e6-bb65-89aa7e1d54fd}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {4bb67c47-1d2f-4144-ad8a-0298fa5b16f8}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {27f82b0f-4f1d-493d-9201-3394163feeb6}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {39bc2ebd-66ae-4a4d-982a-1de84367f87c}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {dc4c9c17-c8c5-4d71-a497-33713a3ffd90}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {6c310602-07d6-4c23-bc59-0d4098e6ddeb}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {2475a9cf-8c51-442a-801b-ad2af1268e9f}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {22bdd491-042f-4529-8601-253880cea444}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {c6bd9e7c-f814-4272-8061-4f439447c601}
       State: [9] Failed
       Last error: Timed out

    List providers >>

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7

     Run again and get this writers error:

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

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {db362f95-879d-416c-b4f7-abddd8f2e307}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {86e87936-5531-45b4-a3b4-42241d7a9567}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {ab850c5b-e636-4da3-a2b7-f3db652d0834}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {692bbe5f-3727-4435-96ff-e39917f777fe}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {b3df0782-4eb0-4a52-bcb1-0d55638a5223}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {010e3aba-0236-4875-99ab-6d936148fe47}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {5ad98e84-2a59-446f-9584-65f1edd31123}
       State: [1] Stable
       Last error: No error

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {2238d9f6-087b-4af9-85d8-a48f5064bc09}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {0b54ec44-7528-419e-a4ae-a64d38fd0288}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {1cf0faf9-51ae-461c-ab38-f00f64f53e02}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {a68bd3e5-4b00-4425-bcd9-6fa652518ac7}
       State: [9] Failed
       Last error: Timed out

     

    Wednesday, April 25, 2012 9:11 AM
  • Please disable SQL Server VSS Writer in Services.msc console, restart the server and then rerun the vssadmin list writers command and report back the result...

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 25, 2012 9:25 AM
  • before backup:

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

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {b606b8e2-7088-4a19-9667-c71f648373b2}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {522e2ac8-b4d6-49f1-b78a-d16f265cb721}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {f3acbef8-f187-423b-909b-b3b274e5ae16}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {68df114b-f304-41b7-8863-609a2296d584}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {e9eb0544-272d-4218-8b9b-c4353075a36e}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {6fcb0e2f-f26d-47fb-abbc-f4f1418b3225}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {a072ab48-0535-4431-9d03-4d7eeee63e43}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {bc1d747c-1baa-4c54-bf07-df1cc89ba4a9}
       State: [1] Stable
       Last error: No error

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {b4c0001c-453c-4401-8817-f92996847872}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {f7281ad9-d123-49cc-bb74-215ce1a9eb78}
       State: [1] Stable
       Last error: No error

     After backup failed:

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

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {b606b8e2-7088-4a19-9667-c71f648373b2}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {522e2ac8-b4d6-49f1-b78a-d16f265cb721}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {68df114b-f304-41b7-8863-609a2296d584}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {f3acbef8-f187-423b-909b-b3b274e5ae16}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {e9eb0544-272d-4218-8b9b-c4353075a36e}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {a072ab48-0535-4431-9d03-4d7eeee63e43}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {6fcb0e2f-f26d-47fb-abbc-f4f1418b3225}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {bc1d747c-1baa-4c54-bf07-df1cc89ba4a9}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {b4c0001c-453c-4401-8817-f92996847872}
       State: [9] Failed
       Last error: Timed out

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {f7281ad9-d123-49cc-bb74-215ce1a9eb78}
       State: [9] Failed
       Last error: Timed out

    Error in logs

    The backup operation that started at '‎2012‎-‎04‎-‎25T10:03:29.841000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Wednesday, April 25, 2012 10:26 AM
  • Did you disabled SQL Server VSS Writer service before the latest your backup operation?


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 25, 2012 10:30 AM
  • yes, i did
    Wednesday, April 25, 2012 10:41 AM
  • Please do the following actions:

    1. Clear events in backup section of the Event Viewer.

    2. Go to C:\Windows\Logs\WindowsServerBackup and delete everything from there.

    3. Please download the Wbdiag diagnostic tool from the following link.

    https://skydrive.live.com/?cid=26139043773c1011&id=26139043773C1011!214

    4. Execute the version that best matches the architecture of your server's operating system.

    5. To begin collecting the required log files, execute %SystemDrive%\wbdiag\StartWbdiag.cmd from an elevated Command Prompt.

    6. Reproduce your scenario.

    7. After the problem appeared, press <Enter> in the Command prompt to stop the tracing.

    8. The data collected is saved in the WBDiag-yyyy-mm-dd-hh-mm-ss directory. Zip this folder and upload it somewhere and then provide us the link of the upoloaded zip file to analyze your problem thoroughly.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 25, 2012 1:10 PM
  • Hi,

    Oh, according to your description, your server had installed Symantec backup software, this is a known issue, this problem is likely related to third-party backup software.

    Based on previous experience, I suggest you uninstall the other backup software and retry operation, as the windows  server backup is not compatible with Symantec.

    You could do a testing, try to uninstall Symantec and then retry to back up system state.


    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

    Thursday, April 26, 2012 3:44 AM
    Moderator
  • I'll test for while and come back with an answer
    Thursday, April 26, 2012 11:47 AM
  • any updates?

    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

    Monday, April 30, 2012 2:12 AM
    Moderator
  • Hi, again.

    I've uninstalled the symantec backup exec agent and windows backup completed succesful, i tested it for week and system state completed with no errors.

    it is look like symantec problem.

    Wednesday, May 02, 2012 5:27 AM