Hyper-V backup fails with 0xe000fe4a The operation is not complete or 0xe0008516 Resources specified for snapshot do not have any valid data on them

  • Article ID:100001557
  • Modified Date:
  • Product(s):


Unable to backup a Hyper-V Server with Backup Exec

Error Message

0xe000fe4a - The operation is not complete.

0xe0008516 - Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

Backup- VRTSRV::\\<Server>\Hyper-V?Virtual?Machine\<Hyper-V Server>
V-79-57344-38726 - Backup Exec failed to connect to virtual machine and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.
For additional information regarding this error refer to link V-79-57344-65098
Also, a non-GRT (Granular Recovery Technology) backup to disc job fails with:
V-79-57344-38721 - Failed to mount one or more virtual disk images:
Backup- VRTSRV::\\<Server>\Hyper-V?Virtual?Machine\<Hyper-V Server>
Error mounting disk(s): UNKNOWN_ERROR (0xe00084af).
Error writing file data.
AOFO enabled job fails with the error,
AOFO: Initialization failure on: "VRTSRV::\\<Server>\Hyper-V?Virtual?Machine\<Hyper V Server?". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Microsoft Hyper-V, Writer ID: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during post-snapshot operation (11).



Attempt any of the following to resolve the error:

1. Disable AOFO

2. Change the selection list resource order to back up HyperV first or in their own jobs.

3. Make sure the logon account is prefixed with the domain name (Network > Logon accounts from the Backup Exec interface).

4. If the media server is running Windows 2003, install the Microsoft Virtual Server 2005 virtual disk mounter. 
    (Note: There is no need to install the virtual disk mounter on a Windows 2008 R2 media server.)

5. Apply Microsoft Virtual Server 2005 R2 SP1:


6. Install Hotfix 348284 released for BE 2010 on the media server and upgrade the Remote Agent on the Hyper-V Server.


Further troubleshooting to isolate the issue:

  1. Copy a small valid VHD to the Backup Exec media server.  
  2. On the media server navigate the virtual server install folder. 
  3. Run vhdmount /m {TARGETVHDPATH.EN_US} to test if the VHD is mountable.
  4. After mounting the VHD, use Disk Management to bring the disk online and assign a drive letter 
  5. Unmount the VHD with vhdmount /u {TARGETVHDPATH.EN_US} OR vhdmount /u /d {TARGETVHDPATH.EN_US}.
  6. If it works, retry the backup job and enable SGMON www.veritas.com/docs/000029552




Related Articles

How to troubleshoot Hyper-V virtual machine backup that fail with 0xE000FED1 / V-79-57344-65233 - A failure occurred querying the Writer status

Was this content helpful?

Get Support