none
DPM 2010 VSS Writer Error 12289 RRS feed

  • Question

  • Dear folks,


    I recently started having a problem with a protected data source.

    It cannot create recovery points and reports this error:

    "Cannot create a recovery point because of a transient problem. (ID 215 Details: VssError:The shadow copy provider had an error. Check the System and Application event logs for more information.
     (0x80042306))"

    I checked the Application log, and it is spammed full of VSS Writer Events 12289:

    -------------------------

    Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3377\,0x80000000,0x00000003,...).  hr = 0x80070570, The file or directory is corrupted and unreadable.
    .

    Operation:
       Processing PreFinalCommitSnapshots

    Context:
       Execution Context: System Provider

    -------------------------

    The HarddiskVolumeShadowCopy3377 changes on every log, e.g. HarddiskVolumeShadowCopy3377, HarddiskVolumeShadowCopy3378, 3379, 3380, etc hundreds of times.

    The event details are:

    ----------------------------

    + System
    - Provider
    [ Name] VSS
    - EventID 12289
    [ Qualifiers] 0
    Level 2
    Task 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2012-04-27T09:28:31.000000000Z
    EventRecordID 14272
    Channel Application
    Computer flidaprep.erko-holdings.net
    Security
    + EventData
    CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3368\,0x80000000,0x00000003,...)
    0x80070570, The file or directory is corrupted and unreadable.
    Operation: Processing PreFinalCommitSnapshots Context: Execution Context: System Provider
    2D20436F64653A20494E434943484C4830303030303237302D2043616C6C3A2053505251534E504330303030303331312D205049443A202030303030363336382D205449443A202030303030393932302D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820

    Binary data:

    In Words

    0000: 6F43202D 203A6564 49434E49 484C4843
    0008: 30303030 30373230 6143202D 203A6C6C
    0010: 51525053 43504E53 30303030 31313330
    0018: 4950202D 20203A44 30303030 38363336
    0020: 4954202D 20203A44 30303030 30323939
    0028: 4D43202D 20203A44 575C3A43 6F646E69
    0030: 535C7377 65747379 5C32336D 68637673
    0038: 2E74736F 20657865 73206B2D 76727077
    0040: 7355202D 203A7265 656D614E 544E203A
    0048: 54554120 49524F48 535C5954 45545359
    0050: 53202C4D 533A4449 352D312D 2038312D

    In Bytes

    0000: 2D 20 43 6F 64 65 3A 20 - Code:
    0008: 49 4E 43 49 43 48 4C 48 INCICHLH
    0010: 30 30 30 30 30 32 37 30 00000270
    0018: 2D 20 43 61 6C 6C 3A 20 - Call:
    0020: 53 50 52 51 53 4E 50 43 SPRQSNPC
    0028: 30 30 30 30 30 33 31 31 00000311
    0030: 2D 20 50 49 44 3A 20 20 - PID:
    0038: 30 30 30 30 36 33 36 38 00006368
    0040: 2D 20 54 49 44 3A 20 20 - TID:
    0048: 30 30 30 30 39 39 32 30 00009920
    0050: 2D 20 43 4D 44 3A 20 20 - CMD:
    0058: 43 3A 5C 57 69 6E 64 6F C:\Windo
    0060: 77 73 5C 53 79 73 74 65 ws\Syste
    0068: 6D 33 32 5C 73 76 63 68 m32\svch
    0070: 6F 73 74 2E 65 78 65 20 ost.exe
    0078: 2D 6B 20 73 77 70 72 76 -k swprv
    0080: 2D 20 55 73 65 72 3A 20 - User:
    0088: 4E 61 6D 65 3A 20 4E 54 Name: NT
    0090: 20 41 55 54 48 4F 52 49 AUTHORI
    0098: 54 59 5C 53 59 53 54 45 TY\SYSTE
    00a0: 4D 2C 20 53 49 44 3A 53 M, SID:S
    00a8: 2D 31 2D 35 2D 31 38 20 -1-5-18

    ----------------------------

    I have tried creating manual recovery points, removing the protection and re-adding it, and many other things, but I can't get this error to disappear.

    I would like to run chkdsk or other diagnostics, because it says that the file is corrupted, but I can't figure out how to run that on a volume without drive letter.

    Does anyone have any idea on how to solve this issue?

    Friday, April 27, 2012 9:36 AM

Answers

  • Thank you. None of this worked.

    I ran a chkdsk against the volume (got it out of the DPM database) and that showed a corrupt NTFS filesystem (no idea why).

    Ran with /f, and it said all NTFS sectors are corrupt and then the file system was RAW!!!

    I then ran a consistency check and it re-created the file system and did a full sync.

    Seems to be working now...

    Wednesday, May 2, 2012 10:28 AM

All replies

  • Nobody has any idea?

    I have found other posts with this issue, but no solution.

    Monday, April 30, 2012 10:36 AM
  • Hi there,

    Open a command prompt on the server in question and run the following:

    vssadmin /listwriters

    This should give you an output of the different VSS writers that are applicable to your server. If you see one in a failed state, then thats the one that you need to start troubleshooting. On a more simplistic note, have you tried rebooting the flidaprep.erko-holdings.net server? This can sometimes resolve VSS writer issues.

    If neither of those suggestions help, delete the protection group again and re-add it but this time add components to the protection group in small sections and try the backup each time. For example, if you are performing a brick-level backup of a number of volumes on a computer, then start by adding in each volume one at a time and running the backup after each one has been added. You might find that it is a particular corrupted file on a volume that is causing the VSS snapshot problems.

    If you protection group is backing up a Hyper-V machine in it's entirety, then you might be looking at some issues with the Integration Components that are installed inside of the actual virtual machine and it would be a good idea to update these to the latest revisions, recreate your protection group and then try again.

    Hope this helps,

    Kevin.

    Tuesday, May 1, 2012 11:00 AM
  • Thank you. None of this worked.

    I ran a chkdsk against the volume (got it out of the DPM database) and that showed a corrupt NTFS filesystem (no idea why).

    Ran with /f, and it said all NTFS sectors are corrupt and then the file system was RAW!!!

    I then ran a consistency check and it re-created the file system and did a full sync.

    Seems to be working now...

    Wednesday, May 2, 2012 10:28 AM