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. Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
  5. Using NetBackup for SQL Server with multiple NICs
  7. About configuration of SQL Server backups with multiple NICs
Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide

About configuration of 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 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 and review the auto-discovered mappings for the hosts in your environment.

See Configuring mappings for restores of a distributed application, cluster, or virtual machine .

See Reviewing the auto-discovered mappings in Host Management.

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 for SQL Server in a multi-NIC environment:

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

    Alternatively, you can configure the client name after installation.

    See Configuring the 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 Configuring backups of SQL Server when you have multiple NICs (SQL Server Intelligent Policies).

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

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

    See Configuring backups for SQL Server when you have multiple NICs (legacy SQL Server policies).

    See Configuring backups of a SQL Server cluster when you have multiple NICs (legacy SQL Server policies).

    Note that if you want to protect a SQL Server cluster with a legacy SQL Server policy, you must edit the backup batch file. The BROWSECLIENT parameter must indicate the private name of 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.

  • For restores in a multi-NIC environment, refer to the following topic:

    See Performing restores of SQL Server when you have multiple NICs.

    If you want to perform a restore from a SQL Server cluster, you must edit the restore batch file. In the batch file, you must change the BROWSECLIENT parameter to indicate the private name of virtual SQL Server.

    See Performing restores of a SQL Server cluster when you have multiple NICs.

Feedback

Was this page helpful?
Previous

Using NetBackup for SQL Server with multiple NICs

Next

Configuring the client with the private interface name

Feedback

Was this page helpful?