none
DPM encountered a retryable VSS error (ID:30112 Details:VssError) 0x800423F3 RRS feed

  • Question

  • Hello.

    I'm getting an error on one of the protected server in DPM 2010.

    Created one protected group and this group contains 4 servers and one of the server is getting an error.

    Error:
    The replica of Microsoft virtual server 2005 online backup\******001 on Server*** is inconsistent with the protected data source.All protection activitites for data source will fail until the replica is synchronized with consistency check.You can recover data from existing recovery points,but new recovery points cannot be created until the replica is consistent.

    For sharedpoint farm, recovery points will continue getting created with the databases that are consistent.To backup inconsistent databases run a consistency check on the farm (ID 3106)

    DPM encountered a retryable VSS error.(ID:30112 Details:VssError: The writer experienced a transient error.If the backup process is retried, the error may not reoccur.(0x800423F3)

    Guest server details:

    Operating system: Windows 2003 with SP2
    Application: Exchange server 2003

    My Virtual Host server setup is as followed.
    Windows 2003 R2 SP2 and KB940349
    VS2005 R2 SP1 with all latest MS-updates
    VM Additions 13.820 installed on the guests

    And i have run the VSSadmin list writers commond on the virtual Host server and result follows

    Writer Name:'Microsoft virtual Server 2005 Writer'
    Writer ID:{76afb926-87ad-4a20-cdc69412ddfc}
    Writer Instanace Id:{b06a18ac-7ff8-4058-863d-59e1109e114804}
    State:[8] Failed
    last error:Retryable error

    Also i have run the vssadmin list writers commond on guest virtual machine (i.e. issue server)

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {bdd43fdf-ec14-4fa7-bb15-bdd1159382d4}
       State: [7] Failed
       Last error: No error

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {76652728-884c-4228-a228-92796f665116}
       State: [7] Failed
       Last error: Retryable error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {30d4a78b-f937-4acf-9c86-f1e3365d93ba}
       State: [1] Stable
       Last error: No error

    Writer name: 'Event Log Writer'
       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
       Writer Instance Id: {8aead84f-70b9-4224-acd5-ef569c232ae9}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {f7d0b39c-90e4-49b0-9b28-5c57fbba286c}
       State: [7] Failed
       Last error: No error

    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {531f50d2-558c-4a81-905e-9f04544da7a4}
       State: [7] Failed
       Last error: No error

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {7b47775b-fdc4-4ae6-b531-c617e1c73c38}
       State: [7] Failed
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {7d144325-4980-431c-979c-364b36e4afbf}
       State: [7] Failed
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {ac6f2515-eea0-4e2b-9c05-9f66264ca541}
       State: [1] Stable
       Last error: No error

    Writer name: 'MSDEWriter'
       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
       Writer Instance Id: {3b623bd2-da87-48a3-a4ef-9c8c8b69ac39}
       State: [1] Stable
       Last error: No error

    Please help me and how i can fix this issue?

    Thanks,
    Sri

    • Moved by Praveen D [MSFT] Saturday, July 24, 2010 12:05 PM Moving to DPM Hyper-V protection forum as VS is similar to HyperV protection (From:Data Protection Manager)
    Monday, June 14, 2010 11:44 AM

Answers

  • Can you also retry the operation after installing the latest VMAdditions?


    Thanks Shyama Hembram[MSFT] This posting is provided AS IS, with no warranties, and confers no rights.
    Saturday, July 24, 2010 11:36 PM
    Moderator

All replies

  • Does event viewer on hyper-v server has entries corresponding to this time ?

    I hope you tried consistency check.

    Also try restarting vmms service.

     

    Monday, June 14, 2010 11:58 AM
  • Not on Hyper-v, Those virtual machines are running virtual server 2005 sp2

    yes i have tried couple of times consistency check.

    On the same protection group (4 VM's) other three VM's are without any issue/error i am able to taking the backup using DPM 2010.

    On the host server and following event error i found

    Event Type: Error
    Event Source: Virtual Server
    Event Category: Vss Writer
    Event ID: 1026
    Date:  6/14/2010
    Time:  5:20:23 AM
    User:  NT AUTHORITY\SYSTEM
    Computer: VSH101
    Description:
    The VSS writer for Virtual Server failed during the PrepareBackup phase, since the backup of virtual machine SRV001 failed. Retry the operation

    Event Type: Error
    Event Source: VSS
    Event Category: None
    Event ID: 8193
    Date:  6/14/2010
    Time:  5:20:13 AM
    User:  N/A
    Computer: VSH101
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine IVssBackupComponents::SetContextInternal.  hr = 0x800706bf.

    Event Type: Warning
    Event Source: MSiSCSI
    Event Category: None
    Event ID: 108
    Date:  6/11/2010
    Time:  6:01:13 AM
    User:  N/A
    Computer: VSH101
    Description:
    Status 0x00001069 determining that device interface \\?\{0A8BA9F6-C0BA-432f-982E-54317F7D4A1B}#VDisk#1&2d12bed1&0&06#{2accfe60-c130-11d2-b082-00a0c91efb8b} does not support iSCSI WMI interfaces. If this device is not an iSCSI HBA then this error can be ignored.

    Event Type: Error
    Event Source: VolSnap
    Event Category: None
    Event ID: 13
    Date:  6/11/2010
    Time:  5:25:17 AM
    User:  N/A
    Computer: VSH101
    Description:
    The shadow copy of volume C:\...751b-11df-8c1b-0017a43b8e1d} could not grow its shadow copy storage on volume C:\...751b-11df-8c1b-0017a43b8e1d}.

    Thanks,
    Sri

    Monday, June 14, 2010 12:06 PM
  • Since the Exchange VSS writer is in a retryable state you need to look application event logs inside the VM for errors. Lots of other VSS writers inside the guest are also in failed state.
    Thanks Shyama Hembram[MSFT] This posting is provided AS IS, with no warranties, and confers no rights.
    Saturday, July 24, 2010 11:35 PM
    Moderator
  • Can you also retry the operation after installing the latest VMAdditions?


    Thanks Shyama Hembram[MSFT] This posting is provided AS IS, with no warranties, and confers no rights.
    Saturday, July 24, 2010 11:36 PM
    Moderator