locked
Volume shadow copies deleted RRS feed

  • Question

  • Hi

    I keep getting the following error in my WHS event logs:

    Message: The shadow copies of volume C:\fs\4 were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.


    I noitce that there is an old thread on this at:

    http://social.microsoft.com/Forums/en-US/whssoftware/thread/45c49a41-f6c4-4777-8c19-22018509567f/#page:2

    The thread points to the following fixes for Windows Server 2003 (WHS base OS).

    A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
        http://support.microsoft.com/kb/833167/

    Time-out errors occur in Volume Shadow Copy service writers, and shadow copies are lost during backup and during times when there are high levels of input/output
        http://support.microsoft.com/kb/826936/en-us

    How to obtain the latest service pack for Windows Server 2003
        http://support.microsoft.com/kb/889100/

    Does anybody know if these fixes were part of the PowerPack or if they would be applied to my WHS as part of the automatic updates?

    If not, is it OK to apply the fix to WHS?

    My WHS is:
    Windows Home Server with Power Pack 1
    Windows Home Server Console: 6.0.1800.0
    Windows Home Server Backup & Restore: 6.0.1800.0
    Windows Home Server Drive Extender: 6.0.1800.0
    Windows Home Server Remote Access: 6.0.1800.0
    Windows Home Server Storage Manager: 6.0.1800.0

    It has 9 disks of which three are old 80GB disks.
        Could someone also remind me how I relate the file system reference to a physical drive?

    Cheers
    Tim
    Vote for Froglet
    Sunday, September 21, 2008 10:29 AM

Answers

  • Froglet_ said:

    Hi

    I keep getting the following error in my WHS event logs:

    Message: The shadow copies of volume C:\fs\4 were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.


    I noitce that there is an old thread on this at:

    http://social.microsoft.com/Forums/en-US/whssoftware/thread/45c49a41-f6c4-4777-8c19-22018509567f/#page:2

    The thread points to the following fixes for Windows Server 2003 (WHS base OS).

    A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
        http://support.microsoft.com/kb/833167/

    Time-out errors occur in Volume Shadow Copy service writers, and shadow copies are lost during backup and during times when there are high levels of input/output
        http://support.microsoft.com/kb/826936/en-us

    How to obtain the latest service pack for Windows Server 2003
        http://support.microsoft.com/kb/889100/

    Does anybody know if these fixes were part of the PowerPack or if they would be applied to my WHS as part of the automatic updates?

    If not, is it OK to apply the fix to WHS?

    My WHS is:
    Windows Home Server with Power Pack 1
    Windows Home Server Console: 6.0.1800.0
    Windows Home Server Backup & Restore: 6.0.1800.0
    Windows Home Server Drive Extender: 6.0.1800.0
    Windows Home Server Remote Access: 6.0.1800.0
    Windows Home Server Storage Manager: 6.0.1800.0

    It has 9 disks of which three are old 80GB disks.
        Could someone also remind me how I relate the file system reference to a physical drive?

    Cheers
    Tim
    Vote for Froglet




    First, the problem is due to the fact that the same volume is used both for regular data and for the Previous Versions (and that can't be changed).  Mine get deleted occasionally as well (although I've noticed that it usually happens when I'm writing to the shares at midnight or noon, the time when the Shadow pass occurs).  I tried that fix as well, but it didn't do much for me.

    Also, in case you aren't aware, Shadow Copies does not function properly on Windows Home Server.  A reboot of the server will cause a "Device not connected" error when attempting to retrieve a Shadow of any file that is not stored on the primary drive.  While there is a workaround for that issue (which can be found by reading How to regain access to previous version of files in WHS shares, and I use a semi-automated variation of those steps), you may not want to completely rely on them.
    • Proposed as answer by Lara JonesModerator Sunday, September 21, 2008 3:34 PM
    • Marked as answer by Froglet_ Sunday, September 21, 2008 3:49 PM
    Sunday, September 21, 2008 12:55 PM
    Moderator

All replies

  • Froglet_ said:

    Hi

    I keep getting the following error in my WHS event logs:

    Message: The shadow copies of volume C:\fs\4 were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.


    I noitce that there is an old thread on this at:

    http://social.microsoft.com/Forums/en-US/whssoftware/thread/45c49a41-f6c4-4777-8c19-22018509567f/#page:2

    The thread points to the following fixes for Windows Server 2003 (WHS base OS).

    A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
        http://support.microsoft.com/kb/833167/

    Time-out errors occur in Volume Shadow Copy service writers, and shadow copies are lost during backup and during times when there are high levels of input/output
        http://support.microsoft.com/kb/826936/en-us

    How to obtain the latest service pack for Windows Server 2003
        http://support.microsoft.com/kb/889100/

    Does anybody know if these fixes were part of the PowerPack or if they would be applied to my WHS as part of the automatic updates?

    If not, is it OK to apply the fix to WHS?

    My WHS is:
    Windows Home Server with Power Pack 1
    Windows Home Server Console: 6.0.1800.0
    Windows Home Server Backup & Restore: 6.0.1800.0
    Windows Home Server Drive Extender: 6.0.1800.0
    Windows Home Server Remote Access: 6.0.1800.0
    Windows Home Server Storage Manager: 6.0.1800.0

    It has 9 disks of which three are old 80GB disks.
        Could someone also remind me how I relate the file system reference to a physical drive?

    Cheers
    Tim
    Vote for Froglet




    First, the problem is due to the fact that the same volume is used both for regular data and for the Previous Versions (and that can't be changed).  Mine get deleted occasionally as well (although I've noticed that it usually happens when I'm writing to the shares at midnight or noon, the time when the Shadow pass occurs).  I tried that fix as well, but it didn't do much for me.

    Also, in case you aren't aware, Shadow Copies does not function properly on Windows Home Server.  A reboot of the server will cause a "Device not connected" error when attempting to retrieve a Shadow of any file that is not stored on the primary drive.  While there is a workaround for that issue (which can be found by reading How to regain access to previous version of files in WHS shares, and I use a semi-automated variation of those steps), you may not want to completely rely on them.
    • Proposed as answer by Lara JonesModerator Sunday, September 21, 2008 3:34 PM
    • Marked as answer by Froglet_ Sunday, September 21, 2008 3:49 PM
    Sunday, September 21, 2008 12:55 PM
    Moderator
  • I had the same error mesage.

    Believe it or not, I simply ran chkdsk (the windows disk check program) choosing to have windows repair/find bad sectors  I had the following error message.  Windows took care of the corrections itself.                        

    Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.

    I also moved the amount of disk space allocated to system restore to 50 gb, so that may have been the issue too.

    I ran a defrag, rebooted, and voila.

    I can do a system restore now - where I couldn't before.  No longer have that message, etc.

    • Proposed as answer by PGrass Monday, March 5, 2012 2:20 PM
    Thursday, August 12, 2010 2:55 PM
  • after chkdsk /r all vss issues are resolved

    Monday, March 5, 2012 2:21 PM