Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

Castromotorbox

2 Intern

 • 

217 Posts

2071

April 21st, 2015 23:00

Hyper-V and VSS error (0x8004230e)

Hi,

we are trying to run some Hyper-V Backup (Cluster with 4 Node, Windows 2012 R2, Networker 8.1.2.5, NMM 3.0.1)

In the NMM.raw, we are seeing the following error during creation of VSS Snapshot:

  • 027288 ERROR:A VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER error occurred while adding volumes to the VSS snapshot set. The error code is: 0x8004230e.

No idea what it is and how to solve it. In the NMM. raw, we have another error before that one:

  • 65208 1429629650 5 0 0 6992 7960 0 [Node Name] nsrsnap_vss_save NSR critical 111 %s(%d): Error initializing the job. \n    %s\n    NetWorker Server %s is unavailable or does not support Jobs Daemon. 4 23 62 d:\views\nw\8.1.1\nsr\vssclient\snapvsssave\nsrsnap_vss_save.h 1 3 221 24 13 Unknown error 0 24 [Networker Server Name]

Is the second error related to the first one? We are able to backup the Host Component of our Hyper-V nodes but not the Vm.

Any help on Hyper-V Backup Configuration is welcome.

Thanks

Greg

Castromotorbox

2 Intern

 • 

217 Posts

June 1st, 2015 01:00

Hi,

at the end we found the way to make our hyper-V Backup running. As our VM are running on a separate Scale Out File Cluster (SMB), we need to activate the following roles on the cluster that hosted the VM file (not the host that hosted the VM them self):

File Server VSS Agent Service roles.

Here is a useful blog about VSS Backup:


http://blogs.technet.com/b/clausjor/archive/2012/06/14/vss-for-smb-file-shares.aspx


Hope it will help.


Greg

CarlosRojas

1.7K Posts

April 22nd, 2015 01:00

Hi Greg,

Check in the Hyper-V nodes if you have any HW provider installed, and either disable it or use the following variable:

NSR_VSS_FORCE_SYSTEM_PROVIDER=yes

Check the providers by running:

vssadmin list providers.

Thank you,

Carlos

Castromotorbox

2 Intern

 • 

217 Posts

April 22nd, 2015 02:00

Hi Carlos,

With  NSR_VSS_FORCE_SYSTEM_PROVIDER=yes, nothing change in the log.

With NSR_VSS_FORCE_SYSTEM_PROVIDER=no, i see the following line in NMM:

  • info NMM... Info : 'NSR_VSS_FORCE_SYSTEM_PROVIDER' is set to 'no'. Snapshots will be attempted with VSS auto select provider option.

But afterward, i get the same VSS Error. And I don't see any HW provider installed.

can you help me further?

Many thanks

Greg

1 Attachment

Was this post helpful?

View All

No Events found!

Top