• A Guide to Disaster Recovery in the CloudLearn how VMware vCloud® Air™ Disaster Recovery provides an affordable cloud-based solution to protect your applications and data.
    Please register now for a free copy of this e-book.

    Download
  •  Dell EMC Elect 2017 

    Dell EMC Elect represents an unprecedented opportunity for members to receive exclusive access, privileges, and status in appreciation for their contributions to the Dell EMC community.

    Read more

  • Demo Image Everything you need and nothing you don’t. EMC MOBILE is the essential tool for those of us who live EMC. Now your documentation library is available and in-sync online or off direct from the EMC Cloud

    Download

  • Mikes AppMikes.eu App listed in Top Free Business App Windows Store. This simple but very clear app shows all the new posts from this site. Available for Windows 8 and 10. Try it out!

    Download
  • Demo ImageWhy Advertise on Mikes.eu

    Mikes.eu traffic varies depending on the post. We have a VERY focused audience in the Virtualization, Storage and Cloud Marketing space. We have been ranked in the top 5 of Favorite Independent Blogger and one of the most visited website.

Print

Failed EMC Avamar to connect to vCenter 5.1. The vCenter name or IP may not be reachable

Written by on . Posted in How to

After upgrading to VMware vSphere 5.1 All images backups returned with a No Data error. So there is/are no backup of the client(s). So what are we dealing with here? Simple. vCenter Single Sign-On is a new feature of vSphere 5.1 which is causing this problem. EMC Avamar is not authorized to make connection to the vSphere server. SSO is not just an authentication broker but also a security token exchange providing a more secure way of accessing your vSphere solutions. What that means is that when you previously logged into vCenter Server, you were authenticated with the provided username and password against the Active Directory configured for vCenter Server. With vSphere 5.1 and vCenter Single SIgn-On you no longer log directly into vCenter Server but with a security domain defined by your vSphere environment. When logging in to vSphere 5.1 you actually pass authentication to the  vCenter Single Sign-On server which can be configured with multiple identity sources like Active Directory and OpenLDAP and on successful authentication, your username and password is exchanged for a security token which is then used to access the vSphere components like vCenter Server and vCenter Orchestrator etc.

Start your EMC Avamar Administrator and Click Administration

Right Click on your vCenter server and Click Edit Client

Add you domain before the vCenter account. After Ok it should be able to connect again.

Restart the VMware vCenter Connection Monitor from the Avamar Administrator GUI (Administration / Services Administration). Run a manual backup to see if it work

Download Free Designs http://bigtheme.net/ Free Websites Templates