Backup is failling for just1 win 2003vm, over 50 other vm's with same account are working fine -I have tried backing up directly from ESX server using root account, but fails No Yes How can we make this article more helpful? Clean old server names and IP address out of the existing selection lists -Open the backup job -Click View Selection Details -Delete any selections that are not valid. 3. There is no issue with the VMotion as we have aggreed to select the VM when its shifted to another host server. Source
Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page e0009541 - Could not connect to the vCenter For information on how to contact Symantec Sales, please see http://www.symantec.com Workaround: (Backup Exec 2012) Please verify that all permissions are correct for the account being used for the backup process. For and I can see all the VM inside the Host server. Go to HKey_Local_Machine\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\VMware Agent. https://kb.vmware.com/kb/1010837
We are already planning to do the step as mentioned in the dos. Go to Solution. Thank You! Logs are located at C:\Program Files\Symantec\Backup Exec\Logs 0 Kudos Reply Accepted Solution!
I will change the mrinal_sarkar62 Level 6 12-11-2012 04:17 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Ok.. Please enable debugging on Backup Exec media server from registry and try to backup win 2003 vm. I have check the crediantioal through Policy windows but when its trying for backup its giving the following error:- Final error: 0xe0009541 - Could not connect to the vCenter server or Vcenter Cannot Connect To Host Details: The server took too long to respond" "VMware Infrastructure Client could not establish a connection with server "xyz".
Error in the beremote debug:  2012-07-06T11:57:32.353 [ndmp\loops] - The media server BK2-SRV is already in the advertisement list. 2012-07-06T11:57:32.403 [fsys\shared] - vddkConnectToVMWareServer() GD: vmcConnect OK, vddkSession = 0000000009221320 2012-07-06T11:57:32.413 [fsys\shared] Cannot Connect To Vcenter Server Make sure your BESA has the pkh Moderator Trusted Advisor Certified 12-10-2012 01:57 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Thank You! Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue.
I have already selected the required VMs for backup. https://www.veritas.com/support/en_US/article.000086467 An old server may be still in the selection list - Symptoms: Jobs appear successful but still contain the error Newly configured backup jobs do not hrow this error 3. Vcenter Cannot Contact The Specified Host Thanks.. Call "datacenter.queryconnectioninfo" For Object On Vcenter Server Failed. Error Message V-79-57344-38209 0xe0009541 - Could not connect to the vCenter server or ESX server. Please verify the credential supplied for login.
Incapsula incident ID: 108001310306589595-1371361999395227705 Request unsuccessful. this contact form Incapsula incident ID: 108001310306589595-328539262707042353 Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products You may also refer to the English Version of this knowledge base article for up-to-date information. Thanks. 0 Kudos Reply If you read the document pkh Moderator Trusted Advisor Certified 12-10-2012 05:27 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Authenticity Of The Host's Ssl Certificate Is Not Verified
Please verify the credential supplied for login. Cannot Contact The Specified Host Esxi 6 It is possible that updates have been made to the original version after this document was translated and published. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
Email Address (Optional) Your feedback has been submitted successfully! Backup were in disk. 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 Cannot Contact The Specified Host Esxi 5.5 After Update Go to Solution.
Incapsula incident ID: 108001310306589595-1535083416824580154 Request unsuccessful. Create/Manage Case QUESTIONS? Final error category: Resource Errors I am using a domain user for taking backup for all access (VCenter, Datacenter and the VMs) I have tried for single VM same error. Check This Out Please verify the credential supplied for login.
Labels: 2012 Backup and Recovery Backup Exec Basics 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! BE 2012 on Windows 2008 R2. 3.