GRT not available when I backup Virtual Machines
Hello,
We've been using Backup Exec for a couple of years now and we've always enjoyed it. We're testing the 2012 version and while it's a nice product overall, there are a few bugs we're trying to fix, like this one:
The exact error message is given after the backup and says:
work was successful. However, the following conditions were met:
Backup Exec failed to authenticate with one or more virtual machines and failed during the collection of necessary metadata to restore individual application items. It is impossible to perform restores of application data compatible GRT for a virtual machine that has failed to authenticate. You must change the credentials for the backup job from the host computer and then select the appropriate credentials for the virtual machine.
Our test setup is simple:
We have an ESX host, where both the BackupExec2012 VM (backup server) and the TestSystem VM (server that is backed up) are hosted on.
The procedure I'm following is this one:
1) add the ESX host to the BackupExec2012 server
2) create a backup job selecting the ESX server
3) add the TestSystem VM within the ESX host list of VMs and uncheck the other ones
4) backup
As for the required settings, it looks like this:
- VMware tools are installed on TestSystem
- Backup Exec agent for Windows is installed on TestSystem (after VMware tools)
- Authentication is showing as "Success" for the ESX server, the Datastore and the TestSystem VM (in the backup job settings)
- GRT is enabled in the backup job settings (and all its different options)
- C:\TEMP is defined in both fields in the general GRT preferences (it's the local NTFS disk)
How do I enable GRT on Virtual Machines?
Thanks,
Unfortunately GPT is not
Unfortunately GPT is not supported for GRT backups using AVVI. Please look at the SCL http://www.symantec.com/docs/TECH175581 under the VMware Storage Configuration Compatibility
You could try to test the GRT feature on a Virtual machine that meets those guidelines for storage.
Comments
have a look at the document
have a look at the document below...
http://www.symantec.com/business/support/index?page=content&id=TECH155831
I hope this posting was helpful
Hi Donald, the provided link
Hi Donald,
the provided link does not apply to our situation since the Backup Exec server is a VM under the ESX host and cannot be zoned to see the different LUNs.
What are you trying to tell me?
Thanks!
Are you using Hot-add as a
Are you using Hot-add as a transport method or nbd. Also could you please post the job log for more details.
All four transport options
All four transport options are checked.. How do I figure out which one is being used?
Here's the log. The text is in french, but you'll figure out the meaning easily..
Journal du travail pour 10.75.5.9 Sauvegarde 00016-Complète
Informations sur le lecteur et le support à partir du montage du support : 2012-10-02 13:51:17 Nom du lecteur : Stockage sur disque 0001 Label du support : B2D000008 GUID du support : {20f943a1-db63-48f9-a436-bcc67c7b8e82} Tous les supports utilisés B2D000008 IMG000004Label du support : IMG000004 Dossier du jeu de sauvegarde GRT : Z:\BEData\IMG000004 Le mode de transport 'hotadd' a été utilisé pour le disque 'SCOrchestrator2012.vmdk' Backup Exec a découvert et protégé 'C:' sur la machine virtuelle 'ORCHESTRATOR01.labo.dmr'. Backup Exec a découvert et protégé 'Volume{a8a351c4-754e-11e1-8b89-806e6f6e6963}' sur la machine virtuelle 'ORCHESTRATOR01.labo.dmr'.Sauvegarde -- VMVCB::\\10.75.5.9\VCGuestVm\(DC)ha-datacenter(DC)\vm\SCOrchestrator2012
V-79-57344-38730 - Backup Exec n'a pas réussi à s'authentifier auprès de la machine virtuelle "\(DC)ha-datacenter(DC)\vm\SCOrchestrator2012" et a échoué lors de la collecte des métadonnées nécessaires pour la restauration d'éléments d'application individuels. Vous ne pouvez pas effectuer des restaurations de données d'application compatibles GRT à partir de cette sauvegarde. Vous devez modifier les informations d'authentification relatives au travail de sauvegarde de l'ordinateur hôte et sélectionner ensuite les informations d'authentification appropriées pour la machine virtuelle.
As per the job log seems like
As per the job log seems like HotAdd is getting used as the transport method.
Does the account used on the backup job have permissions on VM 'SCOrchestrator2012' and all the applications installed on the server, perticularly - SQL, SharePoint, Exchange and Active Directory (not sure which applications are installed hence listed all)
What is the Operating System on the VM 'SCOrchestrator2012'
Do you have the license for Application and Databases (2012) as to perform an Application GRT you would need this license.
Now for the disks configured on the VM 'SCOrchestrator2012', are they Basic, MBR or some thing else like GPT, Dynamic, RDM.
Right after pasting the log
Right after pasting the log yesterday I've noticed that hotadd was being used. I did a test after that where I disabled hotadd. It reverted to NBD and everything backed up correctly.
Back to the hotadd problem, to answer your questions:
The account has permission on the VM 'SCOrchestrator2012'. There are no SQL, Sharepoint, Exchange or Active Directory installed: it's basically a clean VM.
the OS is Windows 2008 R2
I am running the Trial version of Backup Exec 2012 and the installation log shows that "Agent for Applications and Databases" was installed.
The disk on the VM 'SCOrchestrator2012' is a virtual SCSI disk with 2 partitions (GPT)
Unfortunately GPT is not
Unfortunately GPT is not supported for GRT backups using AVVI. Please look at the SCL http://www.symantec.com/docs/TECH175581 under the VMware Storage Configuration Compatibility
You could try to test the GRT feature on a Virtual machine that meets those guidelines for storage.
Would you like to reply?
Login or Register to post your comment.