Announcement

Collapse
No announcement yet.

VSS snapshot files skipped error during backup

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • VSS snapshot files skipped error during backup

    Dear All,

    Warm hello to you. We have windows 2008 R2 with latest patches/service pack installed. One of its volume E: is a spanned volume which is spread across 3 LUNs (total around 3TB and free space around 600GB). We used to take its file backup though HP data protector (DP). It used to work fine but from few weeks we are facing an issue. During backup we have below error logged in eventviewer and DP skips the file saying not able to find and an event during same time is logged as per below info:
    -----------------------------------------------------------------
    "ERROR in EVENT VIEWER"
    The shadow copies of volume E: were aborted because volume E:, which contains shadow copy storage for this shadow copy, was force dismounted.
    Source: Volsnap, Event ID :16
    -----------------------------------------------------------------
    "ERROR in HP DATA PROTECTOR BACKUP SOFTWARE"
    [Major] From: [email protected] "ovl-fs.ovl.com [/E]" Time: 5/7/2012 12:01:18 AM
    [81:78] GLOBALROOT\Device\HarddiskVolumeShadowCopy8\Share Folders\1st SetDATA\Blk_7\SEISMIC\SEGY\FIELD\SE\SE_21
    Cannot read 65224 bytes at offset 216042200(:1): ([2] The system cannot find the file specified. ).
    [Major] From: [email protected] "ovl-fs.ovl.com [/E]" Time: 5/7/2012 12:01:18 AM
    [81:78] GLOBALROOT\Device\HarddiskVolumeShadowCopy8\Share Folders\1st SetDATA\Blk_7\SEISMIC\SEGY\FIELD\SE\SE_22
    Cannot read 63552 bytes at offset 0(:1): ([2] The system cannot find the file specified. ).
    -----------------------------------------------------------------------
    We spoke with HP Data protector support and they said its OS/fil system issue and needs to be taken up with MS. They also give link to us which says running chkdsk will fix and as per that we ran chkdsk /r on said volume but still the problem is same. On digging further, we noticed that few of VSS Writers were in waiting state (Also given below for everyone to see). So we again searched on and found that restarting some services (e.g. WMI, Windows search etc) will fix it. We did all that and all writers except "system writer" is in stable state now but i beleave this is the main which is used for file system backup. ----------------------------------------------------------------------------------------------------------------------
    vssadmin 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: {43ba5b36-5427-48f6-9bab-288973de8b81}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {776f303d-cf20-496a-b4a8-b24f503494b6}
    State: [1] Stable
    Last error: No error

    Writer name: 'FSRM Writer'
    Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
    Writer Instance Id: {db090f15-3a76-455a-a654-9c86a605108e}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'MSSearch Service Writer'
    Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
    Writer Instance Id: {f924f290-9ef6-4c96-a208-3b97ac7e6646}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {3cf5e5ab-725c-4179-9f97-d2dffbdf7f4a}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {77ce09ed-575f-40f6-a9e7-4f0e2e70debb}
    State: [1] Stable
    Last error: No error

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {273ad309-9646-44f3-9d83-52efc2db91f1}
    State: [5] Waiting for completion
    Last error: No error
    ------------------------------------------------------------------------------------
    vssadmin list providers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
    Provider type: System
    Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
    Version: 1.0.0.7
    -------------------------------------------------------------------------------------------
    So can anyone suggest what can be done to fix this? Or any other area to lokk into to find a solution. Really appreciate the support... Thanks..

  • #2
    Re: VSS snapshot files skipped error during backup

    I don't use this technology so am not familiar with it. But, one thing that occurs to me is: Does the system have enough free space to complete the backup? I know you have 600GB, but is there a minimum percentage of free space that needs to be available?
    A recent poll suggests that 6 out of 7 dwarfs are not happy

    Comment


    • #3
      Re: VSS snapshot files skipped error during backup

      Hi,

      Thanks for your feedback. As per MS, max space a VSS snapshot can take is 10%, so we have more than that free available. Also it never complaints about space in any log we could find. Any thought on how we can get the VSS "System Write" Stable?

      Regs,

      Comment


      • #4
        Re: VSS snapshot files skipped error during backup

        Dear Friends,

        By doing a few service restart, the VSS writers are stable, now the issue is that "Shadow Copy Optimization Writer" is missing from the list. Anyone have any idea how to add the same.

        Thanks..

        Comment

        Working...
        X