Error Message

Job Log Error:
V-79-57344-34070 - Snapshot Technology: Initialization failure on: "VRTSRV::\Hyper-V Host\Hyper-V?HA?VM\VM Name". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot technology error (0xE0008516): The database specified for the snapshot was not backed up because the database was not mounted.

Debug Logs from the Hyper-V Host will show the following:

BEREMOTE: [fsys\shared]        - Attach to VRTSRV::\\Hyper-V Host\Hyper-V?HA?VM\VM Name
BEREMOTE: [fsys\vrtsrv]        - VirtualServer::FS_FshVrtSrv::BackupPrep called BackupPrepReason 1
BEREMOTE: [fsys\vrtsrv]        - BEC_GetNumberOfDisks 0
BEREMOTE: [fsys\vrtsrv]        - BEC_GetDiskChangeId = 000000000827C6A0 ''
BEREMOTE: [fsys\vrtsrv]        - BEC_GetBackupChainDiskChangeId = 000000000827C420 ''
BEREMOTE: [fsys\vrtsrv]        - BEC_GetVMSnapShotName = 0000000000000000 ''
BEREMOTE: [fsys\vrtsrv]        - BEC_GetMSVSBackupMethod 0 some kind of Full
BEREMOTE: [fsys\vrtsrv]        - BEC_GetvmBackupFallbackOption 1
BEREMOTE: [fsys\vrtsrv]        - Attached DLE 'VRTSRV::\\Hyper-V Host\Hyper-V?HA?VM\VM Name'
BEREMOTE: [fsys\vrtsrv]        - Attached DLE type 38 subtype 9

BEREMOTE: [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: VMNAME (VMNAME)
BEREMOTE: [fsys\shadow]        - Informational: Processing root in SHADOW::AddToSnapshotSet
BEREMOTE: [besc]               - SnapshotBackupEngine::scan_file_system() : Volume List size (before prune): 0x00000000
BEREMOTE: [besc]               - SnapshotBackupEngine::scan_file_system(): Volume List size (after prune): 0x00000000
BEREMOTE: [besc]               - SnapshotBackupEngine::scan_file_system(): Volume list is empty. Nothing to snap
BEREMOTE: [besc]               - Error SnapshotBackupEngine::scan_file_system failed, aborting.
BEREMOTE: [besc]               - SnapshotBackupEngine::GetDependentVolumeList failed. No snap possible.

If the status of Microsoft Hyper-V VSS writer is not stable or the writer is missing from the list of writers on the Hyper-V host, Backup Exec fails to create snapshot of virtual machine. The virtual machine backup fails. The Hyper-V VSS writer may be unstable. Following are some of the reasons why the writer may be unstable:

Cause 1:
If the concerned virtual machine has an invalid configuration. For example, a virtual machine pointing to a non-existent virtual disk.

Cause 2:
The writer is unstable because of an earlier failed backup operation.

Cause 3:
If there is a trailing space ‘ ‘ character at the end of the name of virtual machine.
For example, “Virtual Machine 1 “

Cause 4:
If there are orphan virtual machine configuration files present at the default location for storing Hyper-V virtual machine configuration files. Generally, this happens to be %ProgramData%\Microsoft\Windows\Hyper-V\Virtual Machines
Orphan configuration files do not have any virtual machine associated with them.

Solution 1:
Identify the virtual machine with invalid configuration and take corrective action.
For example, if there is no virtual disk mentioned at the path specified in the Virtual Machine properties, update the path to the correct file or if the disk is not required, remove the drive from the Virtual Machine properties.

Solution 2:
Restart the Hyper-V Virtual Machine Management Service and ensure that the status is of the service is Stable.

Solution 3:
Remove the trailing space character from the name of virtual machine and rerun the backup job.

Solution 4:
Identify orphan virtual machine configuration files and delete them. Retry the backup job.

Solution 5:
Review the windows event logs from “Application and Service Logs->Microsoft->Windows->Hyper-V-VMMS” to check if this is an issue with Windows Hyper-V and take corrective actions, if required, in that case 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
 

When you try to backup virtual machines on a Microsoft Hyper-V host, the backup may fail with error messages.

Error Message

Job Log Error:
V-79-57344-34070 - Snapshot Technology: Initialization failure on: "VRTSRV::\Hyper-V Host\Hyper-V?HA?VM\VM Name". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot technology error (0xE0008516): The database specified for the snapshot was not backed up because the database was not mounted. Debug Logs from the Hyper-V Host will show the following:

BEREMOTE: [fsys\shared] - Attach to VRTSRV::\\Hyper-V Host\Hyper-V?HA?VM\VM Name
BEREMOTE: [fsys\vrtsrv] - VirtualServer::FS_FshVrtSrv::BackupPrep called BackupPrepReason 1
BEREMOTE: [fsys\vrtsrv] - BEC_GetNumberOfDisks 0
BEREMOTE: [fsys\vrtsrv] - BEC_GetDiskChangeId = 000000000827C6A0 ''
BEREMOTE: [fsys\vrtsrv] - BEC_GetBackupChainDiskChangeId = 000000000827C420 ''
BEREMOTE: [fsys\vrtsrv] - BEC_GetVMSnapShotName = 0000000000000000 ''
BEREMOTE: [fsys\vrtsrv] - BEC_GetMSVSBackupMethod 0 some kind of Full
BEREMOTE: [fsys\vrtsrv] - BEC_GetvmBackupFallbackOption 1
BEREMOTE: [fsys\vrtsrv] - Attached DLE 'VRTSRV::\\Hyper-V Host\Hyper-V?HA?VM\VM Name'
BEREMOTE: [fsys\vrtsrv] - Attached DLE type 38 subtype 9

BEREMOTE: [fsys\vrtsrv] - VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: VMNAME (VMNAME)
BEREMOTE: [fsys\shadow] - Informational: Processing root in SHADOW::AddToSnapshotSet
BEREMOTE: [besc] - SnapshotBackupEngine::scan_file_system() : Volume List size (before prune): 0x00000000
BEREMOTE: [besc] - SnapshotBackupEngine::scan_file_system(): Volume List size (after prune): 0x00000000
BEREMOTE: [besc] - SnapshotBackupEngine::scan_file_system(): Volume list is empty. Nothing to snap
BEREMOTE: [besc] - Error SnapshotBackupEngine::scan_file_system failed, aborting.
BEREMOTE: [besc] - SnapshotBackupEngine::GetDependentVolumeList failed. No snap possible.

ETrack: 3915262 UMI: V-79-57344-37935