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. Configure the primary server host name for the SQL Server agent
NetBackup™ for Microsoft SQL Server Administrator's Guide

Configure the primary server host name for the SQL Server agent

In some environments, you may need to override the host name that NetBackup for SQL Server uses for server-directed backup and restores. Specifically, when the primary server knows itself by one host name and the client must connect to a different host name to reach the primary server. For example, when the primary server has more than one IP address or associated host name. In this case some client hosts may not resolve and network route to the host name by which the primary server knows itself.

The SQL Server agent obtains the host name for the primary server from several sources, in the following order:

  • NBSERVER value.

    For intelligent policies and protection plans, this name is the host name by which the primary server identifies itself. For other operation types, this name is the host name of the primary server that is configured in the batch file. Or, the host name in the operation that the SQL Server backup administrator configured.

  • SQL Server agent registry setting.

    The primary server name (Current NetBackup Server) in the NetBackup client properties of the NetBackup MS SQL Client interface. This setting corresponds to the following registry entry:

    HKEY_CURRENT_USER\Software\Veritas\NetBackup\NetBackup for Microsoft SQL Server\DEFAULT_SQL_NB_MASTER_SERVER

  • The first SERVER entry in the NetBackup registry on the client host.

    This setting is located in the following registry entry:

    HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\Server

  • Domain server value.

    The host name of the primary server from which the client last requested a host ID certificate. This value is the "serverName" for the primary server in the certmapinfo.json file.

Alternatively, you can set USE_REQUESTED_MASTER = FALSE on the client to give the NBSERVER value lower precedence:

  • SQL Server agent registry value

  • Primary server value

  • NBSERVER value

  • Domain server value

To change the USE_REQUESTED_MASTER setting to FALSE

  1. Add the following statement to a text file (for example, new_config.txt).

    USE_REQUESTED_MASTER = FALSE

  2. On the primary or the media server, enter the following command:

    # bpsetconfig -h ClientA new_config.txt

    NetBackup sets the configuration change on client host ClientA.

Feedback

Was this page helpful?
Previous

Configure NetBackup for the SQL Server non-readable secondary instances that are hidden

Next

Configure the number of jobs allowed for backup operations

Feedback

Was this page helpful?