When the STANDBYPATH batch parameter is commented out in the MOVE script, the NetBackup for SQL agent doesn't fail the restore and reports a successful parent job even though the restore has failed.

  • Article ID:100014172
  • Modified Date:
  • Product(s):

Problem

Using the NetBackup for SQL agent, when a restore is executed with the STANDBYPATH batch parameter (mandatory for RECOVEREDSTATE STANDBY) commented out in the MOVE script, the SQL agent doesn't fail the restore, although the restore does fail.  Additionally, the Activity Monitor incorrectly reports success (status code 0) for the parent job.  (For Full and Differential-Incremental restore, NetBackup doesn't show the restore job on the Activity Monitor but reports errors on the View status dialog in the NetBackup for SQL agent GUI.)

Error Message

STANDBYPATH keyword (as shown below) for Transaction log restore.

Progress log snippet:
#STANDBYPATH "C:\Program Files\Veritas\NetBackup\Logs\SQLStandBy\db1-20140626235952-20140626114050.udo"
...
USER - You must specify STANDBYPATH if you choose RECOVEREDSTATE STANDBY.
INF - Results of executing <F:\Scripts\move_restore.bch>:
<2> operations succeeded. <0> operations failed.

Here, the transaction log restore operation should fail reporting a partially successful status for the Parent Job on Activity monitor. But it does not. 

Similar log entries can be found in progress logs for Differential-Incremental and Full restores.

Solution

ETA of Fix:
The formal resolution for this issue (Etrack 3580484) was expected to be included in the following release:

  • NetBackup 7.6 Maintenance Release 4 (7.6.0.4), expected to be released in the fourth quarter of 2014

When NetBackup 7.6.0.4 is released, please visit the following link for download and README information:
 https://go.Veritas.com/nb

Workaround:
To avoid this issue, do not comment out the STANDBYPATH in the MAKE script.

Best Practices:
Veritas strongly recommends the following best practices:
1. Always perform a full DR backup prior to making any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.
3. Perform periodic "test" restores.

Applies To

All currently supported versions of the NetBackup Agent for SQL are affected (through version 7.6.0.3).

Was this content helpful?

Get Support