NetBackup™ Web UI Microsoft SQL Server Administrator's Guide
- About NetBackup for SQL Server
- Installation and host configuration
- Planning the installation of NetBackup for SQL Server
- Configuring SQL Server hosts and user permissions
- Configuring the NetBackup services for SQL Server backups and restores
- Configure local security privileges for SQL Server
- Assign an RBAC role to the SQL Server administrator
- Configuring the primary server host name for the SQL Server agent
- Configure the number of jobs allowed for backup operations
- Configure the Maximum jobs per client setting
- Managing SQL Server discovery and credentials
- Managing protection plans for SQL Server
- Viewing SQL Server asset details
- Protecting SQL Server
- Restoring SQL Server
- Requirements for restores of SQL Server
- Perform a complete database recovery
- Recover a single recovery point
- Options for SQL Server restores
- Restore a database (non-administrator users)
- Select a different backup copy for recovery
- Restore a SQL Server availability database to a secondary replica
- Restore a SQL Server availability database to the primary and the secondary replicas
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Things to consider before you configure an instant access database
- Configure Samba users for SQL Server instant access
- Configure an instant access database
- View the livemount details of an instant access database
- Delete an instant access database
- Options for NetBackup for SQL Server instant access
- NetBackup for SQL Server terms
- Frequently asked questions
- Protecting SQL Server with VMware backups
- Performance and troubleshooting
Configuring 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:
NBSERVERvalue.For protection plans, this name is the host name by which the primary server identifies itself. Or the host name in the operation that the SQL Server backup administrator configured.
SQL Server agent registry setting.
The primary server name () 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_SERVERThe first
SERVERentry 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\ServerDomain 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 thecertmapinfo.jsonfile.
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
NBSERVERvalueDomain server value
To change the USE_REQUESTED_MASTER setting to FALSE
- Add the following statement to a text file (for example,
new_config.txt).USE_REQUESTED_MASTER = FALSE - On the primary or the media server, enter the following command:
# bpsetconfig -h ClientA new_config.txtNetBackup sets the configuration change on client host
ClientA.