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
Troubleshooting VMware backups
Note the following when you perform a VMware backup that protects an application:
The Application State Capture (ASC) job contacts the NetBackup client on the guest virtual machine and catalogs the application data for recovery.
One ASC job is created per VM, regardless of which applications are selected in the policy.
ASC messages are filtered based on the ASC job details in the Activity monitor.
Failure results in the discovery job or parent job exiting with Status 1.
If you enable recovery for a particular application but that application does not exist on the VM, the ASC job returns Status 0.
bpfis is run and simulates a VSS snapshot backup. This simulation is required to gain logical information of the application.
Table: Issues with using a VMware policy to protect databases
Issue | Explanation |
|---|---|
A database backup fails. | Databases are cataloged and protected only if the configuration is supported for VMware backups. |
NetBackup is installed on an excluded Windows boot disk. The ASC job detects this type of disk and treats it like an independent disk. Do not select the option if NetBackup is installed on the boot drive (typically C:). | |
ASC job produces a status 1 (partially successful). | You selected databases for backup that exist on both supported and on unsupported disks. See "A database backup fails" for unsupported disk information. |
Full-text catalog files exist on the mounted folders. The databases are not cataloged. | |
The Application State Capture (ASC) job fails and the databases are not protected. | When the ASC job fails, the VMware snapshot or backup continues. Application-specific data cannot be restored. When you query the SQL Server Management Studio (SSMS), it may show that the database was backed up. In this case, though the database was skipped, the snapshot was still successful. |
You disabled the option. | |
Database objects are on a VHD disk. No objects in the backup are not cataloged, including those that do not exist on the VHD. | |
You excluded any data disks from the VMware policy, on the Exclude disks tab. Be sure that any disks that you exclude do not contain database data. | |
The VMware disk layout has changed since the last discovery. In this situation, you must force NetBackup to rediscover virtual machines by lowering the value of the option. See the NetBackup for VMware Administrator's Guide. | |
You cannot use a VMware incremental policy to protect SQL Server. However, the VMware backup job is successful. | |
If is enabled, ensure that the SQL Server VSS Writer service is disabled on the guest virtual machine (SQL Server client) to prevent the ASC job failure. | |
ASC job fails with status code 142. | The NetBackup version on the primary server, media server, and the client must be at version 10.4 to support T-SQL snapshot backups. Legacy VMWare-ASC backups are supported for back-level versions. The ASC job may fail with status code 142 if you attempt T-SQL snapshot backups on back-level NetBackup versions. |
You can recover the entire virtual machine from the backup, but you cannot recover the databases individually. | You did not select option on the VMware tab in the policy, which allows recovery of the databases from the virtual machine backups. |
Transaction log backups fail. | You must first perform a full VMware backup without log truncation ( option). |
The databases are not quiesced. | Neither the Veritas VSS provider nor the VMware VSS Provider were installed at the time of backup. In this case, the recovery of a database after it is restored may require manual steps. |
Unable to recover from SQL Server agent differential backup. | If you enabled the option for VMware backups and the backup failed, NetBackup is not able to inform SQL Server that the backup failed. The next differential backup becomes invalid because there is no full backup on which to base the incremental backup. This issue is resolved after the next full backup is successful. |