Home > Backup Exec > Backup Exec Was Unable To Collect The Necessary Metadata For Virtual Machine

Backup Exec Was Unable To Collect The Necessary Metadata For Virtual Machine

Contents

Since I had only used "su" and "sudo" from that 1000 account it never created the 0/root profile. However, the backup job may otherwise complete successfully or complete with an exception. Sorry, we couldn't post your feedback right now, please try again later. Thanks

0 0 03/08/15--15:46: How to configure email alert when BE 2012 is requiring or waiting for a tape to be inserted ? http://technologyprometheus.com/backup-exec/backup-exec-error-codes.html

We have only these one Server. Click this button By default the resulting screen will show you the VCenter or ESX host and the datacenter objects with one set to a specified account and the other Labels: Agent for Microsoft Hyper-V Backup and Recovery Backup Exec Tip-How to Virtualization 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! I must be missing something? 0 Kudos Reply Hi Simon,You can edit the AshwinApte Level 4 Employee ‎05-25-2012 07:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight

Backup Exec Was Unable To Collect The Necessary Metadata For Virtual Machine

Tentative de sauvegarde de volumes directement à partir du volume source. Thanks, Solved! I have single Hyper-V host (Windows Server 2012 R2) and these VM's are running on this host. I have configured service account (BackupExec) in domain and granted Domain Admin rights.

The actual login credentials were found to be correct, hence we reinstalled Backupexec. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Making a backup user with the same credentials on all the servers and domains makes this possible. But i don't see any option to give credentials to the virtual machines.

Contact us about this article I need a solution Hi There, We are doing backups of an exchange database with the Symantec Exchange agent. Backup Exec Cannot Connect To The Remote Agent Because A Trust Relationship Was Not Established La reprise au point de contrôle ne s'applique pas aux ressources suivantes : VMVCB::\\10.75.5.9\VCGuestVm\(DC)ha-datacenter(DC)\vm\SCOrchestrator2012 Montage de lecteurs et de médias demandé : 2012-10-02 13:51:17 Aucun support à ajouter n'a pu être There will likely be a final error of, "ConnectToVirtualMachine: returning 0xe000974a" Cause A VM backup may complete with a failed status. https://www.veritas.com/support/en_US/article.TECH155335 Article:000042195 Publish: Article URL:http://www.veritas.com/docs/000042195 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in

First of all, I need your support and advises to build good experience.    In my company we are using Symantec backup exec 2010 .We are planning to upgrade to 2014. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical You may see an error in SGMon debug logs such as, "Agent does not support SSL. http://www.symantec.com/business/support/index?page=content&id=TECH155831 0 Kudos Reply Hi Donald, the provided link Jean-Sebastien1 Level 3 ‎10-02-2012 01:02 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a

Backup Exec Cannot Connect To The Remote Agent Because A Trust Relationship Was Not Established

CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-was-unable-to-authenticate-with-one-or-more-virtual/td-p/699730 Go to Solution. Backup Exec Was Unable To Collect The Necessary Metadata For Virtual Machine Note 1: Backup Exec supports the granular recovery of individual Exchange and SQL items only in non-clustered and non-distributed configurations. V-79-10091 when trying to browse the RHEL server.

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. this content Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem The failure of gathering Application GRT during a VM backup can occur if the Backup Exec Solved! Transport mode 'nbd' was used for the read operation of the disk 'SM Warehouse_1-000002.vmdk' In addition, I have research this particular message and I have not yet found anything online that

Is there any known bug causing this error? Before doing this I tested an earlier RHEL release which didn't have this behaviour. View solution in original post 0 Kudos Reply 1 Reply Accepted Solution! http://technologyprometheus.com/backup-exec/backup-exec-database-location.html Email Address (Optional) Your feedback has been submitted successfully!

Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may So when i create the backup job with GRT-enabled i give the hyper-v hosts its credentials. V-79-57344-38730: "Backup Exec failed to authenticate with virtual machine 'PATH TO VM' and was unable to collect the necessary metadata to restore individual application items.

Satpaul 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery

Because I found out that the tape drive request logged since one and half week ago in Windows Event viewer (event 58064) and no one knows about it. The credentials which you specify for the backup job job must have appropriate permissions to access these applications. 0 Kudos Reply Hi, This problem has TCSIT Level 2 ‎04-27-2015 04:01 AM but when i calculate backup sets on that disk its stored more than 15 TB on that dedup disk . (i think Interface is showing wrong ratio) also i upgraded my Thanks GraigV 0 Kudos Reply Re: Failed to connect to virtual machine CraigV Moderator Partner Trusted Advisor Accredited ‎07-28-2010 11:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed

Backup Exec (2010 R3) can now only see one of the servers, but not the other one. thanks

0 0 03/06/15--13:50: Problem connecting to remote agent on Exchange server - Error e000846b Contact us about this article I need a solution Hi All, I recently applied Windows See Related Documents (TECH159562 ) 9. The Network and Security settings are configured incorrectly so that the Media Server unable to communicate with the virtual machines over the network.     Terms check over here Vous ne pouvez pas effectuer des restaurations de données d'application compatibles GRT à partir de cette sauvegarde.

Is there anything that I can do to check further as to what may be causing this problem, which only just came back 2 weeks ago? Trialling 2012, recieving V-79-57344-38730 error in logs. What credentials should I use when backing up these virtual machines? From an time taken to recover point of view I would like to improve this performance..

Now for the disks configured on the VM 'SCOrchestrator2012', are they Basic, MBR or some thing else like GPT, Dynamic, RDM. 0 Kudos Reply Right after pasting the log Jean-Sebastien1 Level