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 RBAC for SQL Server administrators
- Managing SQL Server discovery and credentials
- Managing protection plans for SQL Server
- Create a protection plan to protect SQL Server assets
- Configuring backup policies with Snapshot Client
- 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
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- 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
- Performance and troubleshooting
- About debug logging for SQL Server troubleshooting
- About disaster recovery of SQL Server
Reporting of unsuccessful filegroup or file backups
If you select specific databases and specific filegroups or files in a backup policy, NetBackup reports any unsuccessful filegroup or file backups differently than if you select an entire instance (DATABASE $ALL
). Consider the following scenarios:
Scenario 1 - For
SQLINSTANCE1
(DATABASE $ALL
or all the databases), back up the filegroupsFG1
,FG2
, andFG3
. If NetBackup cannot back upFG1
,FG2
, orFG3
, NetBackup skips the backup of the filegroup for that database. The parent job completes with a status 0.Scenario 2 - For
DATABASEA
andDATABASEC
inSQLINSTANCE1
, back up the filegroupsFG1
,FG2
, andFG3
. If NetBackup cannot back up any of these filegroups forDATABASEA
orDATABASEC
, the parent job completes with a status 2. The job details indicate that one or more of the filegroups that you selected were not backed up.