Hosts are listed as Unmanaged in SE 9.5 Backup Manager
We are running SE 9.5 and have Backup Manager installed.
From system manager my hosts look OK, they have been discovered and I can get information and topology details for them. However, in Backup manager the same hosts are reported as Unmanaged and have a question mark above them. The host FQDN is listed and the links to the Data Protector Cell manager are displayed.
How can I get Backup Manager to manage these hosts?
Re: Hosts are listed as Unmanaged in SE 9.5 Backup Manager
Unmanaged is the expected state (and correct) for all backup clients and media managers - and not required to have these systems "managed". This is the DP Cell Manager's perspective you are being shown, as only the Cell Manager is being discovered it is the only managed system in context - all _backup_ related details in reference to the "unmanaged" clients is available. These are not counted toward licensing.
If you choose to manage (discover) the clients directly, you would simply go about deploying the SE CIM Extension(s) to the systems and discover them directly, assuming of course these are supported OS, and be sure to run and schedule data collection to make them "managed", and you would then have additional details (outside of the context of Backup Manager), also, these managed hosts will count toward the MAP count, min. 1 MAP per server, or 1 MAP per HBA port.
There are a number of states for a given system:
discovered - a generic placeholder, generated via fabric discovery visibility of WWNs. A more accurate term would be "undiscovered or unmanaged" for this context. These can be manually grouped and renamed with a couple of user defined custom properties but have no depth (utilization, configuration details) - they are just WWNs shown on the map and can be filtered out. Consider these a "to do" list for deploying agents, or consideration for inferred or agentless discovery.
inferred - an unknown object which has been processed via the rules based option to suppliment the detail by parsing a hostname from the HSG, zone, or alias - which SE will run fwd/rev dns against and then automatically group them, and provide FQDN, IP address and mapping of presented storage capacity (total capacity, not utilizaton). The rules based option is recommended for most any environment where a naming convention and DNS can be leveraged - as it is a quick means to clean up mapping, and provides some good value with minimal effort.
unmanaged - no agent, no discovery, visible from an indirect perspective (for example clients from the perspective of a backup manager discovery). To "manage" a system, deploy a CIM Extension, or if applicable use an agentless (WMI for Windows, SSH for Linux, or VC/ESX discovery) to discover the system and gather full details.
missing - a managed host which is not reachable, the CIM Extension might have been uninstalled, or disabled, credentials invalid, network connectivity missing, etc.
quarantine - a managed host exceeded the default timeout and was quarantined to avoid extending subsequent data collection.
From the SE User Guide:
Media Manager Host
– A host that has the backup application running as the media manager
application. A media manager application and its host can be discovered through the Backup
Manager host (similar to the way that hosts are detected through a switch). If a media manager
host is discovered through a backup manager host, the media manager host is considered to be
“unmanaged,” meaning that the management server has discovered it, but cannot obtain
additional information about the element. If the IP address of the media manager host is
specified in Step 1 of discovery (a CIM Extension deployed, and a subsequent discovery is performed) the media manager host will be considered “managed.”
Wiley Thrasher Storage Management Expert HP Storage TCE and Quality Tiger Team WW L3 Pre-sales Support Hewlett-Packard Company