Approve or add mappings for a host that has multiple host names
A NetBackup host can have multiple host names. For example, both a private and a public name or a short name and a fully qualified domain name (FQDN). A NetBackup host may also share a name with other NetBackup host in the environment. NetBackup also discovers cluster names, including the host name and fully qualified domain name (FQDN) of the virtual name of the cluster.
The NetBackup client name of a host (or the primary name) is automatically mapped to its host ID during certificate deployment. For successful communication between NetBackup hosts, NetBackup also automatically maps all hosts to their other host names.
However, that method is less secure. Instead, you can choose to disable this setting and choose to manually approve the individual host name mappings that NetBackup discovers.
See Disable automatic mapping of NetBackup host names.
See Approve the host mappings that NetBackup discovers.
See Map other host names to a host.
See Map shared or cluster names to multiple NetBackup hosts.
See Examples of auto-discovered mappings for a cluster.
See Example of auto-discovered mappings for a cluster in a multiple NIC environment.
See Examples of auto-discovered mappings for SQL Server environments.
NetBackup automatically discovers many shared names or cluster names that are associated with the NetBackup hosts in your environment. Use the Mappings to approve tab to review and accept the relevant host names. When is enabled, the list shows only the mappings that conflict with other hosts.
Note:
You must map all available host names with the associated host ID. If you deploy a certificate on a host using a host name that is not mapped with the associated host ID, NetBackup deploys a new certificate and issues a new host ID to the host as NetBackup considers it as a different host.
To approve the host names that NetBackup discovers
- On the left, select Security > Hosts.
- Click the Mappings to approve tab.
- Click the name of the host.
- Review the mappings for the host and click Approve if you want to use the discovered mapping.
Click Reject if you do not want to associate the mapping with the host.
The rejected mappings do not appear in the list until NetBackup discovers them again.
- Click Save.
You can manually map the NetBackup host to its host names. This mapping ensures that NetBackup can successfully communicate with the host using the other name.
To map a host name to a host
- On the left, select Security > Hosts.
- Select the host and click Manage mappings.
- Click Add.
- Enter the host name or IP address and click Save.
- Click Close.
Add a shared or a cluster name mapping if multiple NetBackup hosts share a host name. For example, a cluster name.
Note the following before you create a shared or a cluster name mapping:
NetBackup automatically discovers many shared names or cluster names. Review the Mappings to approve tab.
If a mapping is shared between an insecure and a secure host, NetBackup assumes that the mapping name is secure. However, if at run-time the mapping resolves to an insecure host, the connection fails. For example, assume that you have a two-node cluster with a secure host (node 1) and an insecure host (node 2). In this case, the connection fails if node 2 is the active node.
To map shared or cluster names to multiple NetBackup hosts
- On the left, select Security > Hosts.
- Select the host and click Add shared or cluster mappings.
- Enter a Shared host name or cluster name that you want to map to two or more NetBackup hosts.
For example, enter a cluster name that is associated with NetBackup hosts in your environment.
- On the right, click Add.
- Select the NetBackup hosts that you want to add and click Add to list.
For example, if you entered a cluster name in step 3 select the nodes in the cluster here.
- Click Save.
For a cluster with hosts client01.lab04.com and client02.lab04.com, you may see the following entries. For each host, approve the mappings that are valid.
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 |
When you have approved all valid mappings, you see the Mapped host or IP address settings that are similar to the following entries.
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 |
To perform backups of a cluster in a multi-NIC environment you must map the cluster node names to the virtual name of the cluster on the private network.
Table: Mapping host names for a cluster in a multi-NIC environment
Private name of Node 1 | Virtual name of the cluster on the private network |
Private name of Node 2 | Virtual name of the cluster on the private network |
For example, for a cluster in a multi-NIC environment with hosts client01-bk.lab04.com and client02-bk.lab04.com, you may see the following entries. For each host, approve the mappings that are valid.
Host | Auto-discovered Mapping |
|---|---|
client01-bk.lab04.com | clustername-bk.lab04.com |
client02-bk.lab04.com | clustername-bk.lab04.com |
When you have approved all valid mappings, you see the Mapped host or IP address settings that are similar to the following entries.
Host | Mapped Host Names/IP Addresses |
|---|---|
client01-bk.lab04.com | clustername-bk.lab04.com |
client02-bk.lab04.com | clustername-bk.lab04.com |
In Table: Example mapped host names for SQL Server environments, FCI is a SQL Server failover cluster instance. WSFC is Windows Server Failover Cluster.
Table: Example mapped host names for SQL Server environments
Environment | ||
|---|---|---|
FCI (cluster with two nodes) | Physical name of Node 1 | Virtual name of the SQL Server cluster |
Physical name of Node 2 | Virtual name of the SQL Server cluster | |
Basic or advanced availability group (primary and secondary) | Primary name | WSFC name |
Secondary name | WSFC name | |
Basic or advanced availability group, with an FCI (primary FCI and secondary FCI) | Primary FCI name | WSFC name |
Secondary FCI name | WSFC name | |
Physical name of Node 1 | Virtual name of the SQL Server cluster | |
Physical name of Node 2 | Virtual name of the SQL Server cluster |