Reviewing the auto-discovered mappings
In certain scenarios, a NetBackup host shares a particular name with other hosts or has a name that is associated with a cluster. To successfully perform backups and restores with NetBackup for Sybase, you must approve each valid auto-discovered mapping that NetBackup discovers in your environment. Or, manually add the mappings.
See Approve the auto-discovered mappings for a cluster.
Examples of the configurations that have multiple host names include:
A host is associated with its fully qualified domain name (FQDN) and its short name or its IP address.
If the Sybase server is clustered, the host is associated with its node name and the virtual name of the cluster.
These mappings are configured in the node in the NetBackup web UI. You can also use the nbhostmgmt command to manage the mappings. See the NetBackup Security and Encryption Guide and NetBackup Web UI Administrator's Guide for more details.
In a Sybase cluster environment, you must map the node names to the virtual name of the cluster if the following apply:
If the backup policy includes the cluster name (or virtual name)
If the NetBackup client is installed on more than one node in the cluster, the virtual name must be mapped to each node.
If the NetBackup Client is only installed on one node, then no mapping is necessary.
To approve the auto-discovered mappings for a cluster
- In the NetBackup web UI, expand Security > Host mappings.
- Click the Mappings to approve tab.
The list displays the hosts in your environment and the mappings or additional host names that NetBackup discovered for those hosts. A host has one entry for each mapping or name that is associated with it.
For example, for a cluster with hosts
client01.lab04.comandclient02.lab04.com, you may see the following entries:Host
Auto-discovered mapping
client01.lab04.com
client01
client01.lab04.com
clustername
client01.lab04.com
clustername.lab04.com
client02.lab04.com
client02
client02.lab04.com
clustername
client02.lab04.com
clustername.lab04.com
- Click the name of the host.
- Review the mappings for the host and click Approve if you want to use the discovered mappings.
For example, if the following mappings are valid for
client01.lab04.com, then you approve them.Auto-discovered mapping
Valid name for
client01
The short name of the client
clustername
The virtual name of the cluster
clustername.lab04.com
The FQDN of the virtual name of the cluster
- When you finish approving the valid mappings for the hosts, click on the Hosts tab.
For hosts
client01.lab04.comandclient02.lab04.com, you see entries for Mapped host or IP address that are similar to the following:Host
Mapped host names/IP addresses
client01.lab04.com
client01.lab04.com, client01, clustername, clustername.lab04.com
client02.lab04.com
client02.lab04.com, client02, clustername, clustername.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Table: Example mapped host names for a Sybase cluster environment
Environment | ||
|---|---|---|
Cluster with two nodes | Physical name of Node 1 | Virtual name of Sybase server |
Physical name of Node 2 | Virtual name of Sybase server |
If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
To manually map host names
- In the NetBackup web UI, expand Security > Host mappings.
- Click on the Hosts tab.
- Click Add shared or cluster mappings.
For example, type the name of the virtual name of the cluster. Then click Add to choose the hosts to which you want to map that virtual name.