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
About protecting SQL Server availability groups
NetBackup for SQL Server supports backups and restores of SQL Server Always On and read-scale availability groups. For information on supported versions and environments, see the Application/Database Agent Compatibility List.
You can protect an availability group environment in the following ways:
With a protection plan that protects the preferred or the primary replica.
With a policy that protects the preferred or the primary replica.
If an availability group crosses multiple NetBackup domains, you can use Auto Image Replication (A.I.R.) to replicate the backup to the other NetBackup domains.
See Protect a SQL Server availability group that crosses NetBackup domains.
Note the following before you configure the policy or the protection plan:
NetBackup can only fully protect the availability group environment if each replica on which backups occur is registered with credentials.
NetBackup runs a backup job on each replica in the availability group. On the replicas which are not the backup source, the job skips the backup.
NetBackup does not support the following types of backups for availability databases:
Snapshot backups of filegroups or files
Instant Recovery backups
VMware backups
SQL Server does not support the following types of backups on a secondary replica:
Full backups
If a full backup takes place on a secondary replica, NetBackup converts the full backup to a copy-only backup.
Certain differential backups that are performed with a SQL Server Intelligent policy
A differential backup is skipped when an availability group is added as a backup selection.
A differential backup fails when an availability database is added as a backup selection.
A differential backup that is performed with a legacy (batch-file based) policy
Backups of this type result in a failed backup.
Copy-only transaction log backups
Backups of this type result in a failed backup.
(SQL Server 2022) An issue exists with filegroup backups on a non-readable secondary. They are not supported at this time due to a Microsoft limitation.