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
  3. NetBackup™ for Microsoft SQL Server Administrator's Guide
  5. Using NetBackup for SQL Server with multiple NICs
  7. Configuration and requirements for SQL Server backups with multiple NICs
NetBackup™ for Microsoft SQL Server Administrator's Guide

Configuration and requirements for SQL Server backups with multiple NICs

Many administrators want to reserve a separate network interface for their SQL Server host machines that are used for routing backup traffic. This type of environment requires additional configuration for backup policies and the NetBackup client that backs up SQL Server. Special configuration is also required to perform restores.

Note:

If you have a SQL Server cluster in a private network, you must configure the mappings for distributed application restores. Also review the auto-discovered mappings for the hosts in your environment.

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

See Reviewing the auto-discovered mappings.

Ask your NetBackup administrator for assistance.

The following distinct network resources exist in a multi-NIC environment:

  • The public name of each SQL Server host (for example, sqlhost1 and sqlhost2)

  • The private interface name that is used to back up each of the SQL Server hosts (for example, sqlhost1-NB and sqlhost2-NB)

The following additional resources exist for a SQL Server cluster in a multi-NIC environment:

  • The public virtual name of the SQL Server (for example, virtsql)

  • The private virtual name of the SQL Server (for example, virtsql-NB)

The following requirements exist to use NetBackup for SQL Server in a multi-NIC environment:

  • Install the NetBackup client on the SQL Server using the private name of the SQL Server host as the NetBackup client name.

    Alternatively, you can configure the NetBackup client name after installation.

    See Configure the NetBackup client with the private interface name.

  • For intelligent policies, configure a backup policy that includes the private interface name of the host or client.

    See Configure backups of SQL Server when you have multiple NICs (SQL Server Intelligent Policies).

    See Configure backups of a SQL Server cluster when you have multiple NICs (SQL Server Intelligent Policies).

  • For batch file-based policies, configure a backup policy that includes the private interface name of the host or client.

    See Configure backups for SQL Server when you have multiple NICs (batch file-based policies).

    See Configure backups of a SQL Server cluster when you have multiple NICs (batch file-based policies).

    Note that if you want to protect a SQL Server cluster with a batch file-based policy, you must edit the backup batch file. The BROWSECLIENT parameter must indicate the private name of the SQL Server host or virtual SQL Server.

  • Configure permissions to allow all nodes in the cluster to browse for backups across the private interface (redirected restores). The administrator can allow all clients or allow single clients to browse and restore a backup that is performed over the multi-NIC connection.

    See Configuring permissions for redirected restores.

Feedback

Was this page helpful?
Previous

Using NetBackup for SQL Server with multiple NICs

Next

Configure the NetBackup client with the private interface name

Feedback

Was this page helpful?