08-31-2012 06:38 AM
Hello!
We've just upgraded from backup exec 2010 R3 to the new backup exec 2012 software.
Everything is working in order except for the GRT backup of the exchange store. We get the following error message when doing a Full Hyper-v Backup:
08-31-2012 06:55 AM
Hello Said,
Are the Exchange databases stored on GPT volume??
I just came across a technote with same error but that is for VMware backups. Check this for your referance.
http://www.symantec.com/docs/TECH154707
Thanks,
-Sush...
08-31-2012 07:04 AM
Dear Sush,
The Exchange databases are'nt stored on a speciale volume. Just a regular VHD.
Greetz, Said.
09-18-2012 11:49 AM
Hi Said.
I have been fighting with the same exact issue you are having since late June 2012. I have been working with Symantec Support but because I am using the same exact work around you are, I'm low priority and get intermittant support calls.
Hyper-V Host server is: Windows Server 2008 Standard R2 SP1, no clustering or SAN. All local SCSI Raid disks
Exchange 2003 Guest server is: Windows Server 2003 Standard R2 SP2, 80GB Fixed VHD
To date, I've gathered logs and submitted same, ran a "repair" install as twice requeste, and even a full uninstall, and NEW install using a new database. All only brings the exact same results.
Anyways, if you or anyone else has made any headway on this it would be appreciated. I'm so tired of BE2012 becoming my "NEW FULL TIME JOB!"
Cheers
Chucker
09-27-2012 08:34 AM
Hi,
We are experiencing same issue on multiple client servers. We have Hyper-v with Windows 2008 R2 and running 2 Guest servers. One in SBS 2011 and another Windows 2008 R2 w/SQL server. Below is the error that we get.
V-79-57344-38727 - Backup Exec failed to snap virtual machine 'ServerName' 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.
I have support case open with Advanced Technical Support Engineer for Backup Exec and they are not able to resolve this case. As Chucker mention above we are spending long hours behind 2012 product. Also when you talk to sales and marketing of Symantec they advertise that Hyper-v support but does not work.
I hope some one find the solution quick.
KS
09-27-2012 09:09 AM
These errors primarly point to Backup Exec not being able to make collect metadata for cataloging the GRT.
One of the main cause that I have seen is the Applications data (Exchange, SQL) in the Virtual Machine is either on a GPT disk or folder mounted. To check if it is a GPT disk, either you can go to diskpart-> 'list volume' to see it or in Disk Management right click on the disk (place where it says Disk0, Disk1) view properties and it will show in the Volumes tab. Either ways both is not supported for application GRT backups.
Other factor that can lead to these errors is mostly 3rd party VSS Provider installed in the VM. Run a vssadmin list poviders and make sure that only Microsoft Software Shadow Copy provider is listed. Look in event viewer for any messages about either BEVSS or VSS corresponding to the time of backup. Additionally, look in the RAWS\VSS Provider\logs folder for any vss provider logs for any errors corresponding to the time of backups.
09-27-2012 11:23 AM
Thanks Jaydeep,
Our disk are not GPT, they are NTFS format and Basic type. We only have Microsoft Software Shadow Copy provider. All the VSS's are stable etc. I have already worked with Symantec Expert and went over these too many times. Thanks for the try.
Regards,
KS.
09-27-2012 12:10 PM
Hi Jaydeep.
Same answer as Shamansys..... no GPT, NTFS-Basic not Dynamic, only MS VSS (no third party). Also already tried this though Symantec technical support.
Thanx for the input though.... Much appreciated.
Charlie
03-19-2013 03:26 AM
Im getting the same error aswell is there a solution available now?
Using:
BE2012, Windows serv 2008 R2, exchange 2010.
Hyper-v backup job.
Thx in advance.
03-19-2013 03:35 AM
Hello!
I don't have a real solution yet. I got around the problem by first making a backup to disk and then duplicate the job to Tape.
03-19-2013 03:39 AM
Ah thats a pitty. I think its wierd for Symantec not providing a real solution seen this problem on other places as well. Thanks for your fast responds. In our situation to make them seperate jobs isnt an option.