2012 Hyper-v host error from removed usb drives

I have a 2012 server with the hyper-v role hosting 3 VM's.  I keep receiving errors from what I believe was a USB drive that was temporarily attached to transfer som files over originally.  These errors usually occur during the backup process (using veeam for now).

Error 27  volsnap  system  The shadow copies of volume \\?\Volume{2abab8d0-891d-11e3-93f1-842b2b007d02} were aborted during detection because a critical control file could not be opened.

Error 153  disk  system  The IO operation at logical block address 2f8c38 for Disk 3 was retried.

There is no volume guid attached as listed in the error nor is there a Disk 3 attached.  Only disk 0,1, and 2.

These files are not selected for backup nor are shadow copies enabled on the host.  This drive is not listed under disk management nor is it listed when I do a vssadmin List Volumes.

Basically, what can I do to get rid of the errors???

Steve
wrfdchiefAsked:
Who is Participating?
Advertise Here
 
Philip ElderConnect With a Mentor Technical Architect - HA/Compute/StorageCommented:
If Veeam backups trigger the error then re-run the backup scheduler and remove the USB drive as it may be one of the sources for backup.

In Hyper-V Management bring up the settings for the VM and make sure that the USB drive is no longer mounted in the VM via IDE or SCSI bus. If it is the VM will not start on reboot without the drive being connected.

Philip
0
 
wrfdchiefAuthor Commented:
I am running Server 2012 (Not R2) with hyper-v as a role.  The are no pass thru's.  I just tried running a backup to a USB drive with WSB and it completed with errors but 2 of the VM's didn't back up.  I had the following in the backup error log:

Error in backup of D:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Error in backup of D:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Error in backup of D:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 6BB15016-8981-4C64-B00C-3B05823E64D0
   Caption     : Backup Using Child Partition Snapshot\Essentials R2
   Logical Path:
   Error           : 8078010D
   Error Message   : Enumeration of the files failed.

   Detailed Error  : 80070003
   Detailed Error Message : (null)


Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 8457E4AA-B8F5-4C47-89FD-B9B61C5F2B72
   Caption     : Backup Using Child Partition Snapshot\Exchange Server2
   Logical Path:
   Error           : 8078010D
   Error Message   : Enumeration of the files failed.

   Detailed Error  : 80070003
   Detailed Error Message : (null)


*-----------------------------*
0
 
wrfdchiefAuthor Commented:
As an added note when I list the writers on the hyper-v I got the following:


Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {a6c88fa8-d240-4b45-97c5-feb1776635f2}
   State: [8] Failed
   Last error: Retryable error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {f215ff76-37ac-44ac-a96b-f86586dbecad}
   State: [8] Failed
   Last error: Inconsistent shadow copy
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Are the VM's Integration Services up to date? Update IS in all VMs and reboot them then try again.

Are there snapshots happening in the VMs at the same time the host is trying to back up? Make sure VSS activities on the guests do NOT happen at the same time as the host.

FYI: We do not back up the host we back up the guests.

Disable WSB on the host. Connect a new USB drive for backup. Enable WSB and set up to back up to the new destination. Run a backup. Does it complete successfully?

Philip
0
 
wrfdchiefAuthor Commented:
Yes the IS is up to date on all of the VM's.  I have no snapshots.  I will have to get a new USB drive and try it.  What about backing up to a network share in the meantime??  Also what about completely disabling shadow copies on the guests (already disabled on the host) until I get this resolved??
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Previous Versions is tied to VSS on the guests (Volume Shadow Copy). If any VM is providing file services then disabling VSS on that guest is a bad move.

Perhaps setting Backup on the host to run once at night while the guests are using VSS during the day would be best.

We experimented with host backup but ended up sticking with guest based backup as VSS/VSC was too painful to work with and not reliable in the least. Especially if the guest OS is a version or more back from the host.

We use ShadowProtect on the guests. Others use Veeam or Acronis.

Philip
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.