NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Managing SQL Server objects for use with SQL Server Intelligent Policies
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Registering instances or availability replicas with an instance group
- Configuring backups with SQL Server Intelligent Policy
- About tuning parameters for SQL Server backups
- Performing restores of SQL Server
- Redirecting a SQL Server database to a different host
- Protecting SQL Server data with VMware backups
- About protecting an application database with VMware backups
- Configuring backups with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped snapshots
- Protecting SQL Server availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with legacy policies
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- About protecting a specific node in a SQL Server availability group (legacy backup policies)
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- Protecting SQL Server in a cluster environment
- Configuring backups with legacy SQL Server policies using clients and batch files
- About using batch files with NetBackup for SQL Server
- About schedule properties
- Performing user-directed backups of SQL Server databases
- Performing user-directed backups of read-only filegroups
- 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
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 nbsetconfig command to make the host property changes.
does not have permissions to edit the host properties. Alternatively, workload administrators can log on locally to the host and use theODBC 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 } } } }