NetBackup™ for Microsoft SQL Server Administrator's Guide
- About NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Installing the Veritas VSS provider for vSphere
- Configuring RBAC for SQL Server administrators
- Managing SQL Server assets and their credentials
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Configuring backups with SQL Server Intelligent Policy
- Performance tuning and configuration options
- Protecting SQL Server availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with batch file-based policies
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- About protecting a specific node in a SQL Server availability group (batch file-based policies)
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- Protecting SQL Server with VMware backups
- About protecting an application database with VMware backups
- Create a protection plan to protect SQL Server data with a VMware backup
- Configuring backup policies with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped snapshots
- Protecting SQL Server in a cluster environment
- Managing protection plans for SQL Server
- Restoring SQL Server with the NetBackup web UI
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Configuring batch-file based policies for SQL Server backups
- Requirements to use batch files with NetBackup for SQL Server
- Schedule properties for SQL Server batch file-based policies
- Configure a batch file-based policy for a user-directed backup of read-only filegroups
- Performing backups and restores with the NetBackup MS SQL Client
- Redirect a SQL Server database to a different host (NetBackup MS SQL Client)
- Restoring multistreamed SQL Server backups
- Using NetBackup for SQL Server with multiple NICs
- Performance and troubleshooting
- About debug logging for SQL Server troubleshooting
- About disaster recovery of SQL Server
- Appendix A. Other configurations
- About SQL Server backups and restores in an SAP environment
- About NetBackup for SQL Server with database mirroring
- Appendix B. Register authorized locations
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 (
) 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 thecertmapinfo.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
valueDomain 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.txt
NetBackup sets the configuration change on client host
ClientA
.