Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
- Introducing NetBackup for SQL Server
- Installation and host configuration
- Host configuration and job settings
- Managing SQL Server objects for use with SQL Server Intelligent Policies
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Registering instances or availability replicas with an instance group
- Configuring backups with SQL Server Intelligent Policy
- About tuning parameters for SQL Server backups
- Performing restores of SQL Server
- Redirecting a SQL Server database to a different host
- Protecting SQL Server data with VMware backups
- About protecting an application database with VMware backups
- Configuring backups 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 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)
- About protecting a specific node in a SQL Server availability group (legacy backup policies)
- About protecting the preferred replica in a SQL Server availability group (legacy backup policies)
- Protecting SQL Server in a cluster environment
- Configuring backups with legacy SQL Server policies using clients and batch files
- About using batch files with NetBackup for SQL Server
- About schedule properties
- Performing user-directed backups of SQL Server databases
- Performing user-directed backups of read-only filegroups
- Using NetBackup for SQL Server with multiple NICs
- Performance and troubleshooting
- About debug logging for SQL Server troubleshooting
- About disaster recovery of SQL Server
- Appendix A. Other configurations
- About SQL Server backups and restores in an SAP environment
- Appendix B. 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