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
 
 
Frequently asked questions
Here are some frequently asked questions for Microsoft SQL instant access Build Your Own (BYO).
Table:
Applicable for  | Frequently asked question  | Answer  | 
|---|---|---|
BYO  | How can I enable the Microsoft SQL Server instant access feature on BYO after storage is configured or upgraded without the nginx service installed?  | Perform the steps in the following order: 
  | 
BYO  | How can I resolve the following issue in the vpfs-config.log file that is raised from:
  | Perform the steps in the following order: 
  | 
BYO  | Instant Access for BYO uses a self-signed certificate by default and only supports  How do I  replace it with a certificate signed by external CA (  | To configure the external certificate, perform the following steps. If the new certificate is already generated (the certificate must contain long and short host names for the media server), go to step 4. 
  | 
BYO  | How can I disable media automount for the instant access live mount share in gnome? If the automount is enabled, the source folder is mounted from the live mount share in gnome and smaller disks appear. In this scenario, the instant access feature does not work properly. The mounted disk content source is from the   | Follow the guideline to disable the gnome automount:  | 
BYO  | How can I resolve the following issue in the  
  | Perform the steps in the following order: 
  | 
BYO and Flex Appliance  | How can I enable host-based authentication and secure logon for Samba share so that the SQL Server instant access works on specific windows clients?  | Perform the steps in the following order: 
  | 
NetBackup Appliance  | How can I enable host-based authentication and secure logon for Samba share so that the MSSQL instant access works on NetBackup Appliance and Windows clients?  | Perform the steps in the following order: 
 
 For Appliance, the  The local users are added to Samba database automatically and the Samba password is the same as the logon password. The Windows clients can access the appliance's Samba share using credentials of the appliance's local users. 
 Perform the steps in the following order: 
  |