Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installing NetBackup for SQL Server
- Instance Management for SQL Server Intelligent Policies
- Viewing the SQL Server instances and instance groups in instance management
- About registering SQL Server instances
- Configuring SQL Server backups with SQL Server Intelligent Policy
- Configuring NetBackup for SQL Server
- Performing restores of SQL Server
- Redirecting a SQL Server database to a different host
- Restoring multistreamed SQL Server backups
- Protecting SQL Server data with VMware backups
- About protecting SQL Server data with VMware backups
- Using NetBackup for SQL Server with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped backups (legacy SQL Server policies)
- Protecting SQL Server in high availability (HA) environments
- About using NetBackup to protect SQL Server availability groups
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- About protecting a specific node in a SQL Server availability group
- About NetBackup for SQL Server with database mirroring
- Backup and recovery concepts
- Overview of SQL Server backup and recovery concepts
- About recovery factors for SQL Server
- Using NetBackup for SQL Server with multiple NICs
- Configuring backups with legacy SQL Server policies using clients and batch files
- About using batch files with NetBackup for SQL Server
- About schedule properties
- Backing up read-only filegroups
- Performing user-directed operations with dbbackex
- Using bplist to retrieve a list of SQL Server backups
- SQL Server backups and restores in an SAP environment (legacy SQL Server policies)
- About SQL Server backups and restores in an SAP environment
- Troubleshooting
- About debug logging for SQL Server troubleshooting
- Disaster recovery of a SQL Server
- Appendix A. Sample batch files
- About sample backup batch files for legacy SQL Server policies
- About sample restore batch files
- About sample backup batch files for legacy SQL Server policies
- Appendix B. Multiplexed backups
- Appendix C. Register authorized locations
About automatic retry of unsuccessful SQL Server backups
NetBackup for SQL Server provides the following options to retry unsuccessful backup attempts.
Automatic retry | NetBackup for SQL Server keeps track of the unsuccessful backups that may have resulted from the execution of a batch file. When the initial backup attempt is complete, the agent rewrites the batch file, including only those operations that failed. The rewritten batch file is launched automatically. |
Manual retry |
A manual retry is similar to an automatic retry except that NetBackup does not launch the rewritten batch file. Instead it is written to the install_path\dbext\mssql\temp directory. The user can then choose when to run the new batch file. |
To use automatic retry, add the following line to your batch file.
RESTARTTYPE AUTO
By default, the unsuccessful backups are retried one time automatically after 60 seconds. To change the delay following the unsuccessful attempt, then add the following to your batch file.
RESTARTWAITSECONDS <integer>
You can also specify the number of retries. Add the following to your batch file.
NUMRESTARTS <1 to 9>
To use manual retry, add the following line to your batch file.
RESTARTTYPE MANUAL
Retry may also be used with file checkpoints. Any parts of the operation that fail can be written to a new batch file that can be launched either automatically or manually.
You can enable file checkpointing with automatic retry in the backup dialog in the NetBackup for SQL Server Client. Select a single database (or filegroup), then from the
list, select .This action creates a batch file that contains the following scripting:
MAXRESTARTSETS 32 RESTARTWAITSECONDS 60 NUMRESTARTS 1
MAXRESTARTSETS 32 means that up to 32 pieces are backed up independently. The keywords RESTARTWAITSECONDS and NUMRESTARTS are synonymous with the following:
RETRYWAITSECONDS 60 NUMRETRIES 1
These keywords indicates the following things: first, that an automatic retry is launched after 60 seconds for all of the pieces that failed to get backed up on the first time. Second, the restart is attempted only one time. You can manually change either of these parameters.
In addition, you can choose to not have the retry script automatically launched. Replace the NUMRETRIES command with RETRYTYPE MANUAL. For example, replace the following:
NUMRETRIES 1
with
RETRYTYPE MANUAL
Note:
All of the keyword-value pairs that are described in this topic are only permitted in the first operation of the batch file.
More Information