Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Microsoft SQL Server Administrator's Guide
  3. Host configuration and job settings
  4. Reviewing the auto-discovered mappings
NetBackup™ for Microsoft SQL Server Administrator's Guide

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 SQL Server, 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.

See Auto-discovered mappings for a SQL Server cluster in a multiple NIC environment.

See Manually map host names.

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.

These mappings are configured in the Security > Host mappings 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.

Auto-discovered mappings for a 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, the virtual name must be mapped to each node.

    If the NetBackup Client is only installed on one node, then no mapping is necessary.

Approve the auto-discovered mappings for a cluster

To approve the auto-discovered mappings for a cluster

  1. In the NetBackup web UI, expand Security > Host mappings.
  2. 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.com and client02.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

  3. Click the name of the host.
  4. 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

  5. When you finish approving the valid mappings for the hosts, click on the Hosts tab.

    For hosts client01.lab04.com and client02.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

  6. If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.

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

Host

Mapped host names

FCI (cluster with two nodes)

Physical name of Node 1

Instance cluster name

Physical name of Node 2

Instance cluster name

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

 

Auto-discovered mappings for a SQL Server cluster in a multiple NIC environment

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

  1. In the NetBackup web UI, expand Security > Host mappings.
  2. 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 in a multi-NIC environment with hosts client01-bk.lab04.com and client02-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

  3. Click the name of the host.
  4. Review the mappings for the host and click Approve if you want to use the discovered mappings.

    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

  5. When you finish approving the valid mappings for the hosts, click on the Hosts tab.

    For hosts client01-bk.lab04.com and client02-bk.lab04.com, you may see the following Mapped host or IP address.

    Host

    Mapped host or IP address

    client01-bk.lab04.com

    clustername-bk.lab04.com

    client02-bk.lab04.com

    clustername-bk.lab04.com

  6. If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.
Example mapped host names for a SQL Server cluster in a multi-NIC environment

Table: Example mapped host names for a SQL Server cluster in a multi-NIC environment

Host

Mapped host names

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

Manually map host names

If you need to add a mapping that NetBackup did not automatically discover, you can add it manually.

To manually map host names

  1. In the NetBackup web UI, expand Security > Host mappings.
  2. Click on the Hosts tab.
  3. 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.

Feedback

Was this page helpful?
Previous

Configure local security privileges for SQL Server

Next

Configuring mappings for restores of a distributed applications, clusters, or virtual machines

Feedback

Was this page helpful?