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
- Reviewing the auto-discovered mappings
- Configuring mappings for restores of a distributed applications, clusters, or virtual machines
- Configuring the ODBC connection
- Configure NetBackup for the SQL Server non-readable secondary instances that are hidden
- 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
- Configuring RBAC for SQL Server administrators
- Managing SQL Server discovery and credentials
- Managing protection plans for SQL Server
- About protecting SQL Server availability groups
- Create a protection plan to protect SQL Server assets
- Add SQL Server assets to a protection plan
- Customize protection settings for a Microsoft SQL Server asset
- Remove protection from SQL Server assets
- Protect a SQL Server availability group that crosses NetBackup domains
- Configuring backup policies with Snapshot Client
- About NetBackup Snapshot Client for SQL Server
- How SQL Server operations use Snapshot Client
- Snapshot methods
- Configuration requirements for SQL Server snapshot and Instant Recovery backups
- Configure a snapshot policy for SQL Server
- Configure a policy for Instant Recovery backups of SQL Server
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped snapshots
- Viewing SQL Server asset details
- 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
- About protecting an application database with VMware backups
- About configuring NetBackup for VMware backups that protect SQL Server
- Configuring a VMware backup policy to protect SQL Server
- Configuring a VMware policy to protect SQL Server using Replication Director to manage snapshot replication
- Create a protection plan to protect SQL Server data with a VMware backup
- Protect SQL Server data with a VMware backup
- Restore SQL Server databases from a VMware backup
- Performance and troubleshooting
- NetBackup for SQL Server performance factors
- About debug logging for SQL Server troubleshooting
- Troubleshooting credential validation
- Troubleshooting VMware backups
- SQL Server log truncation failure during VMware backups of SQL Server
- About monitoring NetBackup for SQL Server operations
- Setting the maximum trace level for NetBackup for SQL Server
- Reporting of unsuccessful filegroup or file backups
- About minimizing timeout failures on large SQL Server database restores
- SQL Server restore fails when you restore a SQL Server compressed backup image as a single stripe or with multiple stripes
- Incorrect backup images are displayed for availability group clusters
- A restore of a SQL Server database fails with Status Code 5, or Error (-1), when the host name of the SQL Server or the SQL Server database name has trailing spaces
- A move operation fails with Status Code 5, or Error (-1), when the SQL Server host name, the database name, or the database logical name has trailing spaces
- Unable to discover or browse availability group replicas
- About disaster recovery of SQL Server
Configuring the ODBC connection
NetBackup handles the encryption settings of an ODBC connection from a NetBackup client to a target SQL Server instance. These settings are configured in the host properties for the connecting client and can only be configured with the hostProperties API endpoint or the nbsetconfig command.
Note:
The RBAC role does not have permissions to edit the host properties. Alternatively, workload administrators can log on locally to the host and use the nbsetconfig command to make the host property changes.
ODBC connections are created using an ODBC connection string. This string is made up of a list of key-value pairs that changes the connection's behavior depending on the key-value pair.
Table: hostProperties API endpoint parameters for ODBC connections
Parameter | Description |
|---|---|
| Whether to encrypt the connection using TLS. For NetBackup clients that are updated to 10.4 or later, the SQL Server ODBC connections from the client to a target SQL Server instance are encrypted by default. |
| Whether to trust the target SQL Server instance's certificate. For 10.4 and later clients, |
| The name of the supported SQL Server ODBC driver to use during the connection. The value can be one or many individual driver names. List driver names in the order of preference. Or, set the value to The driver The available driver values are as follows: "SQL Native Client" "SQL Server Native Client 10.0" "SQL Server Native Client 11.0" "SQL Server" "ODBC Driver 11 for SQL Server" "ODBC Driver 13 for SQL Server" "ODBC Driver 17 for SQL Server" "ODBC Driver 18 for SQL Server" "OLDEST" "NEWEST" |
The following example uses the host properties API endpoint to enable encryption, trust the target client certificate, and indicates NetBackup should use the driver "SQL Server". If that driver is not available, then NetBackup should use "ODBC Driver 17 for SQL Server".
PATCH https://{{primary-server}}/netbackup/config/hosts/{{client-host-id}}/
host-properties?fieldset%5BhostProperties%5D=clientMssql
Body:
{
"data": {
"type": "hostProperties",
"id": "{{client-host-id}}",
"attributes": {
"clientMssql": {
"trustServerCertificate": true,
"preferredODBCDriver": [
"SQL Server",
"ODBC Driver 17 for SQL Server"
],
"encrypt": true
}
}
}
}