Example host mappings
The following examples describe scenarios where you may want to create host mappings to consolidate host names or to ensure successful communication between hosts.
See Examples of auto-discovered mappings for a cluster.
See Example of host names that are displayed for a multiple NIC environment.
See Example of auto-discovered mappings for a cluster in a multiple NIC environment.
See Examples of auto-discovered mappings for SQL Server environments.
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 |
After you approve all the 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 |
In some advanced NetBackup configurations like a multi-NIC environment, a NetBackup host may display under two host names in the . One name reflects the operating system (OS) name and the other name reflects the name that was specified when NetBackup was installed. This behavior does not affect the ability to connect to the host or to view or edit the host's properties.
For example, you may see the following entries for Host 1 that is in a multi-NIC environment.
Table: Multiple host name entries for a host in a multi-NIC environment
osname-host1.domain.com | OS name of Host 1 |
clientname-host1.domain.com | Client name of Host 1 |
To consolidate these host names, to the host clientname-host1.domain.com add a mapping for osname-host1.domain.com. After you add the mapping, you see only one entry for the host in host properties.
Table: Host mapping for a multi-NIC environment
client01-name.domain.com | clientname-host1.domain.com, osname-host1.domain.com |
Backups of a cluster in a multi-NIC environment require special mappings. 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 |
After you approve all the valid mappings, you see the Mapped host or IP address settings that are similar to the following entries.
Host | Mapped host names or 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 |