Please enter search query.
Search <book_title>...
Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
Last Published:
2021-06-07
Product(s):
NetBackup (9.1)
- Introducing NetBackup for SQL Server
- Installation and host configuration
- Host configuration and job settings
- Configuring SQL Server hosts
- Installing the Veritas VSS provider for vSphere
- Configuring the NetBackup services for SQL Server backups and restores
- Configure local security privileges for SQL Server
- Reviewing the auto-discovered mappings in Host Management
- Configuring mappings for restores of a distributed applications, clusters, or virtual machines
- Configuring the number of jobs allowed for backup operations
- Configuring the Maximum jobs per client setting
- Managing SQL Server objects for use with SQL Server Intelligent Policies
- About the Applications utility
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- About credentials used with SQL Server Intelligent Policy
- Registering a SQL Server instance or availability replica
- Registering instances or availability replicas with an instance group
- Registering instances or availability replicas automatically
- Authorizing a DBA to register instances or availability replicas with the nbsqladm command
- Deleting SQL Server objects from the Applications utility
- Manually add a SQL Server instance
- Deactivating or activating an instance
- Cleaning up instances
- Configuring backups with SQL Server Intelligent Policy
- About SQL Server Intelligent Policies
- Creating a SQL Server Intelligent Policy
- About policy attributes
- About schedule properties
- Schedule backup types for SQL Server Intelligent Policies
- Adding instances to a policy
- Adding databases to a policy
- Adding filegroups or files to the backup selections list
- Manually adding files or filegroups to the backup selections list
- Adding instance groups to a backup policy
- About tuning parameters for SQL Server backups
- Backing up read-only filegroups
- Backing up read-write filegroups
- Performing restores of SQL Server
- Starting the NetBackup MS SQL Client for the first time
- Selecting the SQL Server host and instance
- Browsing for SQL Server backup images
- Options for NetBackup for SQL Server restores
- Restoring a SQL Server database backup
- Staging a full SQL Server database recovery
- Restoring SQL Server filegroup backups
- Recovering a SQL Server database from read-write filegroup backups
- Restoring SQL Server read-only filegroups
- Restoring SQL Server database files
- Restoring a SQL Server transaction log image without staging a full recovery
- Performing a SQL Server database move
- About performing a SQL Server page-level restore
- Configuring permissions for redirected restores
- Redirecting a SQL Server database to a different host
- Performing a restore of a remote SQL Server installation
- Restoring multistreamed SQL Server backups
- About using bplist to retrieve SQL Server backups
- About NetBackup for SQL Server backup names
- Protecting SQL Server data with VMware backups
- About protecting an application database with VMware backups
- About configuring NetBackup for VMware backups that protect SQL Server
- Configuring the NetBackup services for a VMware backup that protects 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
- Restore SQL Server databases from a VMware backup
- Configuring backups with Snapshot Client
- About NetBackup Snapshot Client for SQL Server
- How SQL Server operations use Snapshot Client
- Configuration requirements for SQL Server snapshot and Instant Recovery backups
- Configuring a snapshot policy for SQL Server
- Configuring 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 backups (legacy SQL Server policies)
- Protecting SQL Server availability groups
- About protecting SQL Server availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with legacy policies
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- Prerequisites for protecting SQL Server availability groups
- Configuring an automatic backup policy for the preferred or the primary replica of a SQL Server availability group
- Creating batch files for the policy that protects the preferred or the primary replica
- Adding the batch files to the policy that protects the preferred or the primary replica
- About protecting a specific node in a SQL Server availability group (legacy backup policies)
- Configuring an automatic backup policy for a specific replica of a SQL Server availability group
- Creating a batch file for the policy that protects a specific availability replica in an availability group
- Adding the batch files to the policy that protects a specific replica in the availability group
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- Protect a SQL Server availability group that crosses NetBackup domains
- Browsing for SQL Server availability group backup images
- Restoring a SQL Server availability database to a secondary replica
- Restoring a SQL Server availability database to the primary and the secondary replicas
- Restoring an availability database when an availability group crosses NetBackup domains
- Protecting SQL Server in a cluster environment
- Configuring backups with legacy SQL Server policies using clients and batch files
- About legacy SQL Server policies
- About configuring backups with legacy SQL Server policies
- Configuring the NetBackup services for SQL Server backups and restores (legacy SQL Server policies)
- About SQL Server security with NetBackup legacy backup policies
- About using batch files with NetBackup for SQL Server
- Adding a new SQL Server legacy policy
- About schedule properties
- Adding clients to a policy
- Adding batch files to the backup selections list
- Selecting the SQL Server host and instance
- Options for SQL Server backup operations
- About viewing the properties of the objects selected for backup
- Performing user-directed backups of SQL Server databases
- Performing user-directed backups of SQL Server transaction logs
- Performing user-directed backups of SQL Server database filegroups
- Performing user-directed backups of read-only filegroups
- Performing user-directed backups of read-write filegroups
- Performing user-directed backups of SQL Server database files
- Performing partial database backups
- Performing a backup of a remote SQL Server installation
- About file checkpointing with NetBackup for SQL Server
- About automatic retry of unsuccessful SQL Server backups
- Using NetBackup for SQL Server with multiple NICs
- About configuration of SQL Server backups with multiple NICs
- Configuring the NetBackup client with the private interface name
- Configuring backups of SQL Server when you have multiple NICs (SQL Server Intelligent Policies)
- Configuring backups for SQL Server when you have multiple NICs (legacy SQL Server policies)
- Performing restores of SQL Server when you have multiple NICs
- Configuring backups of a SQL Server cluster when you have multiple NICs (SQL Server Intelligent Policies)
- Configuring backups of a SQL Server cluster when you have multiple NICs (legacy SQL Server policies)
- Creating a batch file for backups of a SQL Server cluster when you have multiple NICs (legacy SQL Server policies)
- Performing restores of a SQL Server cluster when you have multiple NICs
- Performance and troubleshooting
- What are the components of NetBackup for SQL Server?
- How does NetBackup for SQL Server back up a database?
- How does NetBackup for SQL Server recover a database?
- Performing a manual backup
- About debug logging for SQL Server troubleshooting
- About NetBackup for SQL Server performance factors
- About monitoring NetBackup for SQL Server operations
- Setting the maximum trace level for NetBackup for SQL Server
- Troubleshooting credential validation
- Reporting of unsuccessful filegroup or file backups
- About minimizing timeout failures on large SQL Server database restores
- Troubleshooting VMware backups and restores of SQL Server
- Delays in completion of backup jobs
- SQL Server log truncation failure during VMware backups of SQL Server
- 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
- Appendix A. Other configurations
- Configuring multiplexed backups of SQL Server
- Restoring a multiplexed SQL Server backup
- About SQL Server backups and restores in an SAP environment
- Configuring NetBackup to support database log-shipping
- Backing up SQL Server in an environment with log shipping
- Appendix B. Register authorized locations
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.