Please enter search query.
Search <book_title>...
NetBackup™ Web UI Microsoft SQL Server Administrator's Guide
Last Published:
2024-03-27
Product(s):
NetBackup (10.4)
- 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
SQL Server log truncation failure during VMware backups of SQL Server
SQL Server transaction log truncation may fail during VMware backups of SQL Server if a database name contains special characters or if the %TEMP% directory path is too long. During SQL Server log truncation, the NetBackup for SQL Server agent creates a temporary log backup. This backup specifies the current user's configured %TEMP% directory and database name as part of the destination backup device. SQL Server limits the path that can be used for backup devices to 259 characters. Under certain circumstances the SQL Server agent may generate a backup device that is longer than 259 character and cause log truncation to fail.
The following conditions cause failure:
A configured %TEMP% directory that is longer than 259 characters.
When the combined length of the database name and %TEMP% directory path is longer than 259 characters.
One workaround for this issue is to configure the %TEMP% directory so that the path is substantially less than 259 characters long.