X hits on this document





114 / 200


Using NetBackup for SQL Server Automatic retry of unsuccessful backups

Running batch files

Once you have created a batch file, you manually run it from the NetBackup for SQL Server interface.

To run a batch file


Log in to the host and instance you wish to access. Refer to “Selecting the SQL host and instance” on page 63.

2 3 4 5

Choose File > Manage script files. Double-click on the desired batch file. Click Start. To monitor the operation, choose File > View status.

Automatic retry of unsuccessful backups

NetBackup for SQL Server provides the following options for retrying unsuccessful backup attempts.

Automatic retry

NetBackup for SQL Server keeps track of the unsuccessful backups that may have resulted from executing 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

This retry is similar to automatic retry except that NetBackup does not launch the rewritten batch file. Instead it is written to the install_path\dbext\mssql\retry\ directory. The end-user can then choose when to run the new batch file.

To use automatic retry, add the following line to your batch file. RETRYTYPE AUTO

By default, the unsuccessful backups will be retried once automatically after 60 seconds. If you wish to change the delay following the unsuccessful attempt, then add the following to your batch file. RETRYWAITSECONDS <integer>

You can also specify the number of retries by adding the following to your batch file. NUMRETRIES <1 to 9>.

To use manual retry, add the following line to your batch file. RETRYTYPE MANUAL

Document info
Document views631
Page views631
Page last viewedThu Jan 19 04:49:28 UTC 2017