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
Prerequisites when you configure an instant access SQL Server database
The prerequisites are only applicable to Microsoft SQL Server instant access Build Your Own (BYO).
The BYO server operating system version must be Red Hat Enterprise Linux 7.6 or later.
Ensure that the Samba service is installed and the Samba share permission is allowed in the selinux policy using the following command
setsebool -P samba_export_all_rw=1
The storage server with NGINX installed.
The NGINX version must be same as the one in the corresponding official RHEL version release. You need to install it from the corresponding RHEL yum source (epel).
Ensure that the
policycoreutilsandpolicycoreutils-pythonpackages are installed from the same RHEL yum source (rhel server). Then run the following commands:semanage port -a -t http_port_t -p tcp 10087
setsebool -P httpd_can_network_connect 1
Ensure that the
/mntfolder on the storage server is not mounted by any mount points directly. User mount points should be mounted to its subfolders.Enable the logrotate permission in selinux using the following command:
semanage permissive -a logrotate_t
Instant access is only supported for SQL Server backup images when the following conditions are met:
Snapshots are enabled in the policy or the protection plan.
The backup is a full database backup.
The primary server, media server, storage server, and client must be at version 8.3 or later.
For instant access using backup copies from cloud LSU (logical storage unit), the primary server and media server must be at version 10.0.1 or later.
For more information about limitations of instant access for cloud LSU (logical storage unit), refer to the NetBackup Deduplication Guide.
The storage server must be an appliance or BYO that meets the earlier specified prerequisites.
Note:
Instant access for incremental and transaction log backups depends on the instant access capability of its base backup image.