none
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)) RRS feed

  • Question

  • I got this error, how to fix it?

    DPM 2010 with latest roll-up (KB2615782) | DELL Server R710 (Windows 2008 R2 SP1) RAM: 24GB PF: 36-60GB | DELL TL4000 (4 Drives) | DELL TL2000 (2 Drives) | And still struggling and monitoring... Battle continues... life never happy ever after.. :(

    Saturday, June 23, 2012 12:08 AM

All replies

  • Hi,

    What is the data source that is generating this error and does this occur when doing Disk to Disk (D2D) backups, or Disk to Disk to Tape (D2D2T)backups ? This is a very generic VSS error while attempting to create a SHADOW COPY for a volume containing the data source being protected by DPM.  Look for VSS errors in the application event log or Volsnap Errors in the System Event log on the protected server for D2D backups, or on the DPM server for D2D2T backups.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, June 23, 2012 8:33 PM
    Moderator
  • Hi,

    What is the data source that is generating this error and does this occur when doing Disk to Disk (D2D) backups, or Disk to Disk to Tape (D2D2T)backups ? This is a very generic VSS error while attempting to create a SHADOW COPY for a volume containing the data source being protected by DPM.  Look for VSS errors in the application event log or Volsnap Errors in the System Event log on the protected server for D2D backups, or on the DPM server for D2D2T backups.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    D2T, no disk backup.

    DPM 2010 with latest roll-up (KB2615782) | DELL Server R710 (Windows 2008 R2 SP1) RAM: 24GB PF: 36-60GB | DELL TL4000 (4 Drives) | DELL TL2000 (2 Drives) | D2T Backup No Disk Pool (Electric & Disk Costly) | And still struggling and monitoring... Battle continues... life never happy ever after.. :(

    Sunday, June 24, 2012 12:40 AM
  • Hi,

    What is the data source that is generating this error and does this occur when doing Disk to Disk (D2D) backups, or Disk to Disk to Tape (D2D2T)backups ? This is a very generic VSS error while attempting to create a SHADOW COPY for a volume containing the data source being protected by DPM.  Look for VSS errors in the application event log or Volsnap Errors in the System Event log on the protected server for D2D backups, or on the DPM server for D2D2T backups.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    D2T backup, no disk pool.

    DPM 2010 with latest roll-up (KB2615782) | DELL Server R710 (Windows 2008 R2 SP1) RAM: 24GB PF: 36-60GB | DELL TL4000 (4 Drives) | DELL TL2000 (2 Drives) | D2T Backup No Disk Pool (Electric & Disk Costly) | And still struggling and monitoring... Battle continues... life never happy ever after.. :(

    Sunday, June 24, 2012 12:41 AM
  • OK,

    Then the problem is on the protected server, look for VSS or Volsnap errors and correct them and the backups should then succeed.

    What is the data source (volume, SQL DB, Hyper-V guest, Exchange DB) being protected that failes due to theis error ?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by Albert miquel Monday, July 15, 2013 7:52 PM
    • Unproposed as answer by Albert miquel Monday, July 15, 2013 7:52 PM
    Sunday, June 24, 2012 3:51 PM
    Moderator
  • I have the same error, did you encountered this solution?

    "What is the data source (volume, SQL DB, Hyper-V guest, Exchange DB) being protected that failes due to theis error ?"

    In my case is Virtual Machine


    Monday, March 3, 2014 1:04 PM
  • Hi,

    Oneoa- For Disk-to-Tape (D2T) backup - Look for VSS errors in the application event log or Volsnap Errors in the System Event log on the protected server and work on solving them so DPM can perform backups.

    Luis- Look for VSS errors in the application event log or Volsnap Errors in the System Event log on the protected server for D2D and D2T backups, or on the DPM server for D2D2T backups.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, March 3, 2014 3:31 PM
    Moderator
  •   In Hyper-v, I have this errors: 

    List Writers

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {52a247b1-bd8e-499c-915d-314f9080e993}
       State: [11] Failed
       Last error: Retryable error

    Eventvwr:

    SOURCE: VSS ID: 8229

    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 

    Operation:
       PostSnapshot Event

    Context:
       Execution Context: Writer
       Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Name: Microsoft Hyper-V VSS Writer
       Writer Instance ID: {52a247b1-bd8e-499c-915d-314f9080e993}
       Command Line: C:\Windows\system32\vmms.exe
       Process ID: 2460

    SOURCE: HYPER-V-VMMS ID: 10143

    Failed to delete the shadow copy (VSS snapshot) set with id '3ED86740-3BFC-4FD5-B6B6-5ADD63E87DB0' in the running virtual machine 'MACHINENAME': This operation returned because the timeout period expired. (0x800705B4). (Virtual machine ID E130C3C7-D2BC-4234-BD2A-766054A163F9)


    Monday, March 3, 2014 7:08 PM
  • In settings of the machine, Integration Services, I unchecked "Backup (volume snapshot)" the backup working again, but it isn't the solution..

    Anyone help-me?

    Tuesday, March 4, 2014 5:21 PM
  • Hi Luis,

    It seems you are having VSS problems inside the Guest - please open a thread with the Windows support group in the Windows backup forum.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, March 4, 2014 7:00 PM
    Moderator
  • To resolve this issue I had to restart the Exchange Replication Service

    I then re-ran vssadmin list writers in the command prompt and it showed its state as stable and the backups went through.

    Monday, May 5, 2014 2:36 PM
  • To resolve this issue I had to restart the Exchange Replication Service

    I then re-ran vssadmin list writers in the command prompt and it showed its state as stable and the backups went through.

    Monday, May 5, 2014 2:36 PM
  • ok, but this error occur in different environments. :/

    Monday, May 5, 2014 4:33 PM