NetBackup™ Web UI Microsoft SQL Server Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.3.0.1, 10.3)
  1. About NetBackup for SQL Server
    1.  
      Overview of NetBackup for SQL Server
    2.  
      Detailed features for NetBackup for SQL Server
  2. Installation and host configuration
    1. Planning the installation of NetBackup for SQL Server
      1.  
        NetBackup server and client requirements
      2.  
        Requirements for using NetBackup for SQL Server in a NetBackup cluster
      3.  
        License for NetBackup for SQL Server
    2. Configuring SQL Server hosts and user permissions
      1.  
        Installing the Veritas VSS provider for vSphere
    3.  
      Configuring the NetBackup services for SQL Server backups and restores
    4.  
      Configure local security privileges for SQL Server
    5.  
      Assign an RBAC role to the SQL Server administrator
    6.  
      Configuring the primary server host name for the SQL Server agent
    7.  
      Configure the number of jobs allowed for backup operations
    8.  
      Configure the Maximum jobs per client setting
  3. Managing SQL Server discovery and credentials
    1. About discovery of SQL Server objects
      1.  
        Discover advanced or basic availability groups on demand
      2.  
        Discover databases on demand
      3.  
        Discover read-scale availability groups
    2. About SQL Server credentials
      1.  
        Add a credential for SQL Server
      2.  
        Select a credential for a SQL Server instance or replica
      3.  
        View the credential name that is applied to an asset
      4.  
        Edit or delete a named credential
    3.  
      Remove SQL Server instances
    4.  
      Manually add a SQL Server instance
  4. Managing protection plans for SQL Server
    1.  
      About protecting SQL Server availability groups
    2. Create a protection plan to protect SQL Server assets
      1.  
        Schedules
      2.  
        Performance tuning and configuration options
    3.  
      Add SQL Server assets to a protection plan
    4.  
      Customize protection settings for a Microsoft SQL Server asset
    5.  
      Remove protection from SQL Server assets
    6.  
      Protect a SQL Server availability group that crosses NetBackup domains
  5. Configuring backup policies with Snapshot Client
    1.  
      About NetBackup Snapshot Client for SQL Server
    2.  
      How SQL Server operations use Snapshot Client
    3.  
      Snapshot methods
    4.  
      Configuration requirements for SQL Server snapshot and Instant Recovery backups
    5.  
      Configure a snapshot policy for SQL Server
    6.  
      Configure a policy for Instant Recovery backups of SQL Server
    7. Using copy-only snapshot backups to affect how differentials are based
      1.  
        Creating a copy-only backup (legacy SQL Server policies)
      2.  
        Creating an Instant Recovery backup that is not copy-only (legacy SQL Server policies)
    8. About SQL Server agent grouped snapshots
      1.  
        Restoring a database backed up in a group
  6. Viewing SQL Server asset details
    1.  
      Browse SQL Server assets
    2.  
      View the protection status of databases, instances, or availability groups
  7. Restoring SQL Server
    1.  
      Requirements for restores of SQL Server
    2.  
      Perform a complete database recovery
    3.  
      Recover a single recovery point
    4.  
      Options for SQL Server restores
    5.  
      Restore a database (non-administrator users)
    6.  
      Select a different backup copy for recovery
    7.  
      Restore a SQL Server availability database to a secondary replica
    8.  
      Restore a SQL Server availability database to the primary and the secondary replicas
  8. Using instant access with SQL Server
    1. Prerequisites when you configure an instant access SQL Server database
      1.  
        Hardware and configuration requirements of instant access
    2.  
      Things to consider before you configure an instant access database
    3.  
      Configure Samba users for SQL Server instant access
    4.  
      Configure an instant access database
    5.  
      View the livemount details of an instant access database
    6.  
      Delete an instant access database
    7.  
      Options for NetBackup for SQL Server instant access
    8.  
      NetBackup for SQL Server terms
    9.  
      Frequently asked questions
  9. Protecting SQL Server with VMware backups
    1. About protecting an application database with VMware backups
      1.  
        Limitations of VMware application backups
    2. Create a protection plan to protect SQL Server data with a VMware backup
      1.  
        Backup options and Advanced options
      2.  
        Exclude disks from backups
      3.  
        Snapshot retry options
    3.  
      Protect SQL Server data with a VMware backup
    4.  
      Restore SQL Server databases from a VMware backup
  10. Performance and troubleshooting
    1.  
      NetBackup for SQL Server performance factors
    2.  
      Troubleshooting credential validation
    3.  
      Troubleshooting VMware backups
    4.  
      SQL Server log truncation failure during VMware backups 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 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.

See Limitations of VMware application 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 Exclude boot disk 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 Enable virtual Machine quiesce 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 Reuse VM selection query results for 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.

 

You can recover the entire virtual machine from the backup, but you cannot recover the databases individually.

You did not select Microsoft SQL Server, which allows recovery of the databases from the virtual machine backups.

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.