Reviewing the auto-discovered mappings in Host Management
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 SQL Server, you must approve each valid Auto-Discovered Mapping that NetBackup discovers in your environment. These mappings appear in the Host Management properties on the master server. You can also use the nbhostmgmt command to manage the mappings. See the Security and Encryption Guide for more details on Host Management properties.
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 SQL Server is clustered, the host is associated with its node name and the virtual name of the cluster.
In a SQL Server 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
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 Administration Console, expand Security Management > Host Management.
- At the bottom of the Hosts pane, click the Mappings for Approval 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
- If a mapping is valid, right-click on a host entry and click Approve.
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 at the bottom of the Hosts pane.
For hosts
client01.lab04.comandclient02.lab04.com, you see Mapped Host Names/IP Addresses 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.
Click on the Hosts tab, then right-click in the Hosts pane and click Add Shared or Cluster Mappings. For example, provide the name of the virtual name of the cluster. Then click Select Hosts to choose the node names in the cluster to which you want to map that virtual name.
In Table: Example mapped host names for SQL Server environments, FCI is a SQL Server failover cluster instance. AG is an availability group. 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 | |
AG (primary and secondary) | Primary name | WSFC name |
Secondary name | WSFC name | |
AG 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 |
If you have a SQL Server cluster in a multi-NIC environment, you need to approve each valid Auto-Discovered Mapping for the hosts in that environment. You must map the virtual name of the SQL Server cluster on the private network to the private name of each SQL Server cluster node.
To approve the auto-discovered mappings for a SQL Server cluster in a multiple NIC environment
- In the NetBackup Administration Console, expand Security Management > Host Management.
- At the bottom of the Hosts pane, click the Mappings for Approval 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 in a multi-NIC environment with hosts
client01-bk.lab04.comandclient02-bk.lab04.com, you may see the following entries:Host
Auto-discovered Mapping
client01-bk.lab04.com
clustername-bk.lab04.com
client02-bk.lab04.com
clustername-bk.lab04.com
- If a mapping is valid, right-click on a host entry and click Approve.
For example, if following mapping is valid for
client01-bk.lab04.com, then you approve it.Auto-discovered Mapping
Valid name for
clustername-bk.lab04.com
The virtual name of the SQL Server cluster on the private network
- When you finish approving the valid mappings for the hosts, click on the Hosts tab at the bottom of the Hosts pane.
For hosts
client01-bk.lab04.comandclient02-bk.lab04.com, you may see the following Mapped Host Names/IP Addresses.Host
Mapped Host Names/IP Addresses
client01-bk.lab04.com
clustername-bk.lab04.com
client02-bk.lab04.com
clustername-bk.lab04.com
- If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Click on the Hosts tab, then right-click in the Hosts pane and click Add Shared or Cluster Mappings. For example, provide the name of the virtual name of the cluster. Then click Select Hosts to choose the hosts to which you want to map that virtual name.
Table: Example mapped host names for a SQL Server cluster in a multi-NIC environment
Private name of Node 1 | Virtual name of the SQL Server cluster on the private network |
Private name of Node 2 | Virtual name of the SQL Server cluster on the private network |