NetBackup™ Web UI Microsoft SQL Server Administrator's Guide
- Introducing the NetBackup web user interface
- About NetBackup for SQL Server
- Installation and host configuration
- Monitoring and notifications
- Managing SQL Server discovery and credentials
- About discovery of SQL Server objects
- Managing protection plans for SQL Server
- Create a protection plan to protect SQL Server assets
- Protecting SQL Server
- 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
- Create a protection plan to protect SQL Server data with a VMware backup
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.