Video Screencast Help

Strange Backup behaviour

Created: 15 May 2014 | 6 comments

Backup of a w2102-host with 2 hyper-guest (also on 2012) present a success or a failure. since this happens we don't change something on the 3 machines and 1 day it works, one day it fails. Latest error V-79-57344-34108, the day before on guest-a, yesterday on guest-b. Other error-codes are: V-79-40960-38467, V-79-57344-33967, V-57344-65033, V-79-57344-38726. Both guests are production-server and in daily use. After a reboot of the host, the backup may work or not.

BE2012 , SP3, HF213186

OS on all 3 machines are actually patched

What i found was fingerprintdiskmap.txt in c:\program files\symantec\BackuExec\RAWS\DATA\Hyper-V\Temp\5724f93a-..-..-...-..\9999....-..-..-..-\ with the following content:


M:\Hyper-V_Machines\xxxx\xxxx_c.vhd fingerprint0000.db

M:\Hyper-V_Machines\xxxx\xxxx_d.vhd fingerprint0001.db

fingerprint0000.db is 41024kb

fingerprint0001.db is missing

The guest with the error, does not appear on the hyper-v-manager, if you connect remotely to the host. on the hyper-v-manager on the host, the failing guest is still backing-up in his state, but the guest is online and the app is working fine and can be remotely connected.

Operating Systems:

Comments 6 CommentsJump to latest comment

CraigV's picture


Where is BE 2012 installed on? If 1 of those Hyper-V hosts (or any other server running Server 2012) then you're running an unsupported configuration. BE 2012 only supports Windows 2012 as a RAWS-based agent installation currently.

BE 2014 which gets released next month will support this functionality.


Alternative ways to access Backup Exec Technical Support:

bandit61's picture

Sorry, missed to say on the w2012 host/guest only the agents are running. have more of these and all work fine, except one. MediaServer running on 2008R2.

bandit61's picture

Last night backup-to-tape failed, after reboot this morning :

backup to tape successful

backup to disk: successful with exceptions (see below)

backup to tape successful

backup to disk: successful with exceptions (see below)

Errors of B2D:

Backup- Sxxx
V-79-10000-13305 - Backup Exec cannot back up recovery partitions that do 
not use drive letters. To back up the recovery partition and ensure the 
use of Windows Server 2012 features after a disaster recovery, assign a 
drive letter to it.

Backup- VRTSRV::\\Sxxx\Hyper-V?Virtual?Machine\Sxx
V-79-57344-38726 - Backup Exec failed to connect to virtual machine 
'Sxx' 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. You must install the Agent 
for Windows and the virtual machine tools provided by your host 
software on the virtual machine.

V-79-57344-38758 - Failed to mount one or more virtual disk 
images.  Restart the Backup Exec Server to address this issue.

Backup- VRTSRV::\\Sxxx\Hyper-V?Virtual?Machine\Sxxx
V-79-57344-38758 - Failed to mount one or more virtual disk 
images.  Restart the Backup Exec Server to address this issue.

Backup- \\Sxxx\System?State
V-79-10000-13307 - You have backed up a Windows Server 
2012 computer. You cannot use the Simplified Disaster 
Recovery disk to restore Windows Server 2012 computers. 
However, you can run a manual complete online restore 
for disaster recovery or a physical to virtual conversion.

bandit61's picture

thanks, took a deep view in your technotes:

this solution is not applicable to our system.

we backup the host as one whole set, no grt enabled on any hyper-v with guests

virtual disk are setup as dynamic, but as mentioned above not grt enabled

no sdr in use

bandit61's picture

2 days in a row okay, last night failed again with V-79-57344-5894 and V-79-57344-34108. Looking at the Hyper-V-Manager from a workstation, you just see 1 guest. Looking at the hyper-v-manager on the host,both guest are visible, the missing guest on the workstation is in backing up state with 00:00:00 uptime, although the backup-job is finished. after booting this guest the state is okay and uptime is counting again.