Forum Discussion

tundrageek's avatar
tundrageek
Level 3
10 years ago

BE 2014 Hyper-V Differential backups of VMs with GRT enabled receive exceptions - no data backed up

I've just installed and configured Backup Exec 2014 on a Windows 2012 R2 Hyper-V server and I'm receiving the following exception when I attempt to run a differential backup of my VMs with GRT enabled:

 

During Granular Recovery Technology (GRT) operations, the necessary boot configuration files could not be loaded. Backups that were enabled for GRT may not be available for restore.

 

No data is available for restore for these differential backups.  Full backups succeed without issue.  This exact error happens on both environments that I've installed BE 2014.  Guest VMs are all Gen 2 VMs and both have 2012 and 2012 R2 guest VMs.

12 Replies

  • I have been having the same problem and I believe I have the Answer.

    When you use EFI instead of BIOS windows creates GPT disks. This is not support by the backupexec Vmware agent (see the link below). To check that you have open an administrative cmd windows. Type diskpart. Then type list disk. You should see a star under the GPT section.

    I had a case open with symantec and the support representative told me there will be a hotfix "within one or two months".

    http://www.symantec.com/business/support/library/BUSINESS/xCL/TECH217478/be_2014_scl.html

  • I can confirm that I have the same problem with a server having an efi partition. The efi and the system partition are gpt. I just retried to use the GRT- option for this server again, hoping Symantec solved the problem in sp1 but getting error V-79-40960-38531.

    It is so bad, that there are so much limitations in using the gpt option. Extra backup jobs for nearly every server neccesary due to that.

    If someday GRT is working like suggested in the high color advertisements, it would be great step for BE.

    I also know the really long process of the symantec support, when trying detect a problem reported to the forum. They try a lot of steps, already done by the user again. Than they collect tons of megabytes  debugging and logging information. When the problem is detected it needs a lot  of time to fix them and release a bugfix. Sometimes a had alredy forgot that I reported this problem, when they told me it was fixed, I just was livinig with the workarround.