none
Hyper-V VSS writer fails Windows Server 2008 R2

    Question

  • I have a Windows 2008 R2 64-bit setup on a server. Hyper-V role is installed and I have 6 VMs running (5 Windows and a single RHEL).

    I am also trying to run a backup software that will use the VSS framework on the Operating System. I was seeing a few issues with the back up and ran the vssadmin command for short and long durations to check the states of the writers, especially the Hyper-V VSS writer. 

    I have been running the ''vssadmin list writers" to see the status of the writers.

    1. With not much load running on the VMs and the host OS (Parent partition) there were a few instances where the VSS writer of Hyper-V failed to respond (time-outnot responding error ). This happened anywhere between 5% to 20% of the times, which is pretty high.

    For this case I am looking for the reasons for this to happen and ways to minimize or eliminate the chances of the Hyper-V VSS writer failing, perhaps by running only a given/lesser number of VMs or something.

    2. In one of the runs there was a patch of 20 to 30 minutes a lot of other VSS writers, along with Hyper-V VSS writer,  failed - Timed out. 

    For this one I am looking for reasons and this happened only once under unknown situations.

    Thank you.

    Monday, March 12, 2012 6:29 AM

Answers

  •  

    Hi,

    You can try to re-register and see if it can solve your issue.

    How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.

    http://www.symantec.com/business/support/index?page=content&id=TECH70486


    Please 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.

    Friday, March 16, 2012 8:42 AM
    Moderator

All replies

  • Can you share event logs with me?

    Regards

    Satish

    Monday, March 12, 2012 10:00 AM
  • Do you mean the events that I can see in the even viewer?

    Below is a part of the prints of the vssadmin list writers:

    This is for the case (2). For case (1) the VSS writer times out rarely but consistently.

    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: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {742813ab-6e97-436f-81fb-7582f55f2b29} State: [9] Failed Last error: Timed out Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {942611c6-31ae-46ae-a94d-9aae1323a6ba} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {1c361ac9-e0f3-4901-b28e-235887d8b671} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {6c5389b7-ca34-4350-95fd-29ae07ceead3} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {10105e4e-14bb-4e1d-93ad-9611a266f102} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {9c4fd092-7e52-485a-8858-975c110c846b} State: [9] Failed Last error: Timed out Writer name: 'Certificate Authority' Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86} Writer Instance Id: {b0625d61-669c-4876-9cb9-6df0560ebba8} State: [9] Failed Last error: Timed out Writer name: 'InMageVSSWriter' Writer Id: {296004df-49f3-4287-b33a-4d8c894bc520} Writer Instance Id: {45cc0c10-7c3d-446d-b2d8-5317ebb05ea1} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {79bc4777-2523-4f3a-a239-4e49870d5e0a} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {7056f80e-816b-4ac5-a4cd-6008a1c48dd5} State: [9] Failed Last error: Timed out Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {6a09f723-c9e3-4997-87b8-95c64b40ea39} State: [9] Failed Last error: Timed out


    NoSuchThingAsBad

    Tuesday, March 13, 2012 2:20 PM
  •  

    Hi,

    You can try to re-register and see if it can solve your issue.

    How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.

    http://www.symantec.com/business/support/index?page=content&id=TECH70486


    Please 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.

    Friday, March 16, 2012 8:42 AM
    Moderator
  • I am also seeing the same issue.Could you please let me know whether the below fix related to this issue?

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

    Monday, May 28, 2012 5:59 PM
  • You may find the following thread helpful:

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/313b46c6-5581-496f-9937-36e9dc33948d


    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.

    Monday, May 28, 2012 6:55 PM
  • Well thanks for this pointless answer - marked as answered - that does nothing for the question posed, in which he states Windows 2008 R2 and your link points to an article that in big writing has NOT FOR 2008 R2 on it - well done.

    rob

    Monday, August 06, 2012 3:43 PM