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
Add SQL Server assets to a protection plan
The following procedure describes how to subscribe an SQL Server asset to a protection plan. When you subscribe an asset to a protection plan, you assign predefined backup settings to the asset.
Note the following:
For backups to be successful, a SQL Server instance or replica must have a valid credential configured for it in Instances tab.
See Select a credential for a SQL Server instance or replica.
Your user account is assigned to the RBAC role or another role with the same permissions for protection plans and for SQL Server.
See Default RBAC roles and RBAC permissions in the NetBackup Web UI Administrator's Guide. Or, contact your NetBackup administrator for assistance.
Ensure other requirements are met for the NetBackup environment and for non-administrator users.
Databases only appear on the tabs if they meet one of the following criteria: A backup exists of the database, the database instance has validated credentials, or a manual discovery of databases was performed.
To add SQL Server assets to a protection plan
- On the left, click Workloads > Microsoft SQL Server.
- Choose the asset or assets that you want to protect.
All the databases in an instance
On the Instances tab, select the box for the instance that you want to protect.
An individual database
On the Instances tab, click on the instance that contains the database you want to protect.
On the Databases tab, click the box for one or more databases.
An availability group
On the Availability groups tab click the box for the availability group name.
An individual availability database
On the Availability groups tab click on the availability group name that contains the database that you want to protect.
On the Databases tab, click the box for one or more databases.
A SQL Server cluster
On the Instances tab, select the box for the instance that belongs to the cluster.
The Host name is the virtual name of the SQL Server cluster.
A SQL Server failover cluster instance (FCI)
On the Instances tab, select the instance name depending on if you want to protect the cluster or a node in the cluster:
The instance name, where the Host name is the cluster name of the FCI.
The backup is attempted on the active node. Both nodes must be hosts of the same primary server and the instances must have valid credentials registered.
The instance name, where the Host name is one of the physical node names of the FCI.
For the backup to succeed, this node must be the active node in the cluster. The backup is cataloged under the cluster name.
A SQL Server host that uses multiple NICs
On the Instances tab, select the instance:
The instance name, where the Host name is the private interface name of the SQL Server host.
The instance name for a SQL Server cluster that uses multiple NICs, where the Host name is the private interface name of the virtual SQL Server.
- Click Add protection.
- Select a protection plan and click Next.
For a snapshot backup, look for a protection plan that lists Snapshot options and a Snapshot method.
See Snapshot methods.
For an availability group, select a protection plan that has a configured Availability database backup preference, either Protect primary replica or Protect preferred replica.
Do not subscribe an availability group to a protection plan that has a setting of None or Skip availability databases.
- You can adjust one or more of the following settings:
Schedules and retention
Change the backup start window. For transaction log schedules, you can also edit the frequency and the retention.
See Schedules.
Backup options and Configuration options
Adjust the performance tuning options or change or enable any options for the protection plan.
- Click Protect.
The results of your choices appear under Instances or Databases.