Share:
Twitter
LinkedIn
Facebook
Google+
Reddit
Whatsapp
Follow by Email

This is going to be a short article. At work, we have a few issues with DPM and backing up some Virtual Machines so I thought it would be best to document the fix.

If your backup has failed and you received the below error follow the steps in this guide for an easy fix.

DPM Error ID 30111

Error description: some VMs located on Hyper-V cluster won’t backup and generated this kind of error: The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. (0x800423F4)). All other VMs located on the same Hyper-V host can backup. Vssadmin command shows Hyper-V VSS provide is in failed state. Restarting vmms.exe won’t solve this issue, after running backup task VSS provide failing again.

Solution: In VMM, VM properties, Integration Services just disable and enable Backup (volume snapshot). After this run consistency check on DPM. Sometimes helping to migrate VM to other host.

There is a very easy fix for the above error. Below you will find the instructions for VMM, Failover Cluster Manager, and Hyper-V

Virtual Machine Manager (VMM)

Right click the affected VM and click on Properties. Navigate to the Hardware Configuration tab. Now under Advanced click Integration Services

Untick Backup and then click OK. The window will close. Go back in to the VM’s properties. This time tick the Backup box and click OK

Failover Cluster Manager

Right click the affected VM and click on Settings. Under Management click Integration Services

Untick Backup and then click Apply. Now tick the Backup box and click OK

Hyper-V Manager

Right click the affected VM and click on Settings. Under Management click Integration Services

Untick Backup and then click Apply. Now tick the Backup box and click OK

Now retry the backup and it should work. Sometimes if the backup has not been working for some time you may have to do a consistency first.

Share:
Twitter
LinkedIn
Facebook
Google+
Reddit
Whatsapp
Follow by Email
Categories: Backup

Pixel Robots.

I’m Richard Hooper aka Pixel Robots. I started this blog in 2016 for a couple reasons. The first reason was basically just a place for me to store my step by step guides, troubleshooting guides and just plain ideas about being a sysadmin. The second reason was to share what I have learned and found out with other people like me. Hopefully, you can find something useful on the site.

4 Comments

Russ Morse · April 24, 2018 at 10:25 pm

Thank you so much for this. We were having the same issue in our Hyper-V cluster environment and I have been battling this for a while. This simple solution is a lifesaver.

    Pixel Robots. · April 24, 2018 at 10:30 pm

    Thanks for the comment. Glad the post helped.

Pom2Ter · August 16, 2018 at 1:37 pm

Thank you so much! You save my day!

Malli · October 9, 2018 at 5:54 am

Hi Sir,

I have performed same above but still I am getting below error.

C:\>vssadmin list writers
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Error: A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.

C:\>

Leave a Reply

Your email address will not be published. Required fields are marked *

*

I agree