NetBackup™ for Microsoft SQL Server Administrator's Guide
- About NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Installing the Veritas VSS provider for vSphere
- Configuring RBAC for SQL Server administrators
- Managing SQL Server assets and their credentials
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Configuring backups with SQL Server Intelligent Policy
- Performance tuning and configuration options
- Protecting SQL Server availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with batch file-based policies
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- About protecting a specific node in a SQL Server availability group (batch file-based policies)
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- Protecting SQL Server with VMware backups
- About protecting an application database with VMware backups
- Create a protection plan to protect SQL Server data with a VMware backup
- Configuring backup policies with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped snapshots
- Protecting SQL Server in a cluster environment
- Managing protection plans for SQL Server
- Restoring SQL Server with the NetBackup web UI
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Configuring batch-file based policies for SQL Server backups
- Requirements to use batch files with NetBackup for SQL Server
- Schedule properties for SQL Server batch file-based policies
- Configure a batch file-based policy for a user-directed backup of read-only filegroups
- Performing backups and restores with the NetBackup MS SQL Client
- Redirect a SQL Server database to a different host (NetBackup MS SQL Client)
- Restoring multistreamed SQL Server backups
- 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
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).
If SE Linux is configured, ensure that the
policycoreutils
andpolicycoreutils-python
(for RHEL 7) orpolicycoreutils-python-utils
(for RHEL 8) packages 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
/mnt
folder 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.