locked
WHS Backup fails with VSS problem - Win 7 pro 64bit RRS feed

  • Question

  • Hi all

    I have just added a new computer to my WHS network and can't get it to back up properly. The problem is VSS related and seems to relate to the 120GB OCZ Vertex 2 SSD C drive as if I back up the D Drive only (a WD 1TB BLack HDD) it backs up fine. As above I am using Win 7 Pro 64bit on the PC. Server is original WHS on PP3

    I read about the 100MB System Reserved partition problems but this has 74MB of free space so should have plenty for the VSS to do its bit. If I set it to back up the system reserved partition and D Drive and ignore the C Drive it backs up fine. It is the C Drive that is the problem. As soon as I add it in to the eqauation the back up fails.

    I should also add that when back up starts the PC becomes incredibly sluggish and can be subject to occasional freezes for 30 seconds or more. There is nothing else running on the PC (except Avast antivirus)  and nothing else on the network other than server and PC. The VSS service is started.

    I am getting errors like below and wonder if anyone could assist. I have to admit that it is all a bit over my head.

    the error mentions excessive disk activity but there is nothing running

    Cheers

    Jonty

     

    Log Name:      Application
    Source:        VSS
    Date:          21/01/2011 19:08:09

    Description:
    Volume Shadow Copy Service error: The I/O writes cannot be flushed during the shadow copy creation period on volume \\?\Volume{578eceb7-23e3-11e0-8807-806e6f6e6963}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000, The operation completed successfully.
    ], Flush[0x80042313, The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.
    ], Release[0x00000000, The operation completed successfully.
    ], OnRun[0x00000000, The operation completed successfully.
    ].

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: DoSnapshotSet
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">12297</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-01-21T19:08:09.000000000Z" />
        <EventRecordID>2752</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Main-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\\?\Volume{578eceb7-23e3-11e0-8807-806e6f6e6963}\</Data>
        <Data>0</Data>
        <Data>0x00000000, The operation completed successfully.
    </Data>
        <Data>0x80042313, The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.
    </Data>
        <Data>0x00000000, The operation completed successfully.
    </Data>
        <Data>0x00000000, The operation completed successfully.
    </Data>
        <Data>

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: DoSnapshotSet</Data>
        <Binary>2D20436F64653A20434F524C4F564C4330303030303938322D2043616C6C3A20434F524C4F564C4330303030303738302D205049443A202030303030313034342D205449443A202030303030323730342D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
      </EventData>
    </Event>

     

    Log Name:      Application
    Source:        HomeServer
    Date:          21/01/2011 19:22:17
    Event ID:      770
    Task Category: HomeBackup
    Level:         Error

    Description:
    Backup set 5 on SERVER failed: Microsoft.HomeServer.Backup.VSS.ShadowVolumeException: VSS Operation timed out ---> System.TimeoutException: VSS Operation timed out
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.Wait(IVssAsync va)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       --- End of inner exception stack trace ---
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet..ctor(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="HomeServer" />
        <EventID Qualifiers="53247">770</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-01-21T19:22:17.000000000Z" />
        <EventRecordID>2765</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Main-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>5</Data>
        <Data>SERVER</Data>
        <Data>Microsoft.HomeServer.Backup.VSS.ShadowVolumeException: VSS Operation timed out ---&gt; System.TimeoutException: VSS Operation timed out
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.Wait(IVssAsync va)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       --- End of inner exception stack trace ---
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet..ctor(VolumeInfo[] volumes)
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()</Data>
      </EventData>
    </Event>

     


    Jon
    • Edited by Jon T James Saturday, January 22, 2011 2:53 PM
    Saturday, January 22, 2011 11:00 AM

Answers

  • run offline chkdsk on all your drives... ie: chkdsk c: /v /f

     

    should fix you right up.

    • Proposed as answer by DrX69 Saturday, January 22, 2011 3:01 PM
    • Marked as answer by Jon T James Saturday, January 22, 2011 5:21 PM
    Saturday, January 22, 2011 3:01 PM

All replies

  • run offline chkdsk on all your drives... ie: chkdsk c: /v /f

     

    should fix you right up.

    • Proposed as answer by DrX69 Saturday, January 22, 2011 3:01 PM
    • Marked as answer by Jon T James Saturday, January 22, 2011 5:21 PM
    Saturday, January 22, 2011 3:01 PM
  • That seems to have fixed it. Many thanks

     

    Surprised though as it was a fresh install on a brand new drive.


    Jon
    Saturday, January 22, 2011 5:22 PM