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
Limitations of VMware application backups
Databases are cataloged and protected only for the configurations that are supported for VMware backups. Make sure to store databases and transaction logs on supported storage.
VMware application backups do not support the following policy options and configurations:
Incremental backups. Instead, you can create a protection plan or policy for SQL Server incremental backups.
SQL Server clusters or SQL Server availability groups.
(NetBackup web UI only) Restores from a non-primary copy. You can only restore from the primary copy. Only the primary copy is displayed for restore, even if there are other copies. If you want to restore from another copy, promote that copy to the primary copy.
SQL Server databases are not cataloged and backed up if they exist on the following:
Any virtual machines that use raw device mapping (RDM).
Virtual Machine Disk (vmdk) volumes that are marked as independent.
Mount points that use MBR disks. Mount points that contain SQL Server database files are only supported when the underlying disk is a GPT disk.
Virtual hard disks (VHDs).
RAID volumes.
ReFS file systems.
An excluded Windows boot disk.
For VMware backups with the T-SQL snapshots, the following limitations apply:
T-SQL snapshots require SQL Server 2022. If there are multiple SQL Server instances of different versions (for example, 2019 and 2022) on the guest virtual machine and T-SQL snapshots are enabled, the policy only protects the SQL Server 2022 instances or databases.
NetBackup limits the number of databases that can be processed simultaneously to 62.
Only user databases are protected. System databases cannot be protected with this method. This limitation is from Microsoft. (A policy can contain system databases, but NetBackup skips these databases.)
Log truncation is not supported with T-SQL snapshots.