Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
  3. Configuring backups with legacy SQL Server policies using clients and batch files
  4. About automatic retry of unsuccessful SQL Server backups
Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide

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 Resume options for this selection list, select Save work and restart at point of failure.

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

About file checkpointing with NetBackup for SQL Server

Feedback

Was this page helpful?
Previous

About file checkpointing with NetBackup for SQL Server

Next

Using NetBackup for SQL Server with multiple NICs

Feedback

Was this page helpful?