Highlighted

Snapshot technology error (0xE0008516)

Hi,

We have a the below things:-

1. BE 2012 on Win 2008 R2.

2. Hyper-V Host server on win 2008 R2.

3. 7-8 number of VMs running on each Hyper-V host server.

4. All the VMs were in the EMC VNXe 3100 storage server connected with local network of 1 Gbps. The iSCSI LUN were mounted on to the Hyper-V host server using iSCSI initiator. All these connection were in local network.

 

Below were the error:-

Backup- Datacenter.xxxx.comV-79-57344-34070 - Snapshot Technology: Initialization failure on: "VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\TALLYSERVER". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008516): Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

Check the Windows Event Viewer for details.

 - Snapshot Technology: Initialization failure on: "VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\xx21server". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.

V-79-57344-34070 - Snapshot Technology: Initialization failure on: "VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\XX1SERVER". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE0008516): Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

Check the Windows Event Viewer for details.

V-79-40960-38467 - Virtual machine "MSSQL" has been excluded from the backup because it must be put in a saved state to back up.

Backup - Snapshot Technology: Initialization failure on: "VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\TFS2010". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.

 - Snapshot Technology: Initialization failure on: "VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\XYZServer". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.

V-79-40960-38467 - Virtual machine "Oyster_Centos" has been excluded from the backup because it must be put in a saved state to back up.


 

Exceptions
Click an exception below to locate it in the job log
Resource VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\OracleDB Server2 was found in the previous instance of this job, but it is not present in this job.

The backup options or selections for this job have changed since the last time it ran.

Backup- VRTSRV::\\Datacenter.xxxx.com\Hyper-V?Virtual?Machine\TallyV-79-57344-38721 - Failed to mount one or more virtual disk images:

 Error mounting disk(s): E_IMG_FS_READING_OBJECT_FAILURE (0xe000fedf).

1 Solution

Accepted Solutions
Accepted Solution!

Hi,   If you run: vssadmin

Hi,

 

If you run: vssadmin list writers...from a command line on the affected servers, are any VSS writers in error or failed?

If so, a restart of the server should return them to normal.

THanks!

View solution in original post

5 Replies
Accepted Solution!

Hi,   If you run: vssadmin

Hi,

 

If you run: vssadmin list writers...from a command line on the affected servers, are any VSS writers in error or failed?

If so, a restart of the server should return them to normal.

THanks!

View solution in original post

Hi, Any ideas / solution

Hi,

Any ideas / solution guys....

 

Thanks.

 

Hi, Ok I will check the VSS

Hi,

Ok I will check the VSS Writers...

 

 

Hi, Yes, the Microsoft

Hi,

Yes, the Microsoft Hyper-V VSS gave the error.

 

I guess we need to restart the server.

As this required downtime, thus I will update as sson as possible.

Thanks.

You can try to troubleshoot

You can try to troubleshoot your VSS problem with this document

http://www.symantec.com/docs/TECH173983