NetBackup status code 2809: SQL restore failure

Problem

NetBackup status code 2809 was introduced in NetBackup 7.x for SQL restores 

Solution

Perform the following items in the order presented:

A) Ensure that the client’s server list contains entries for the master server and any media servers that can be used during the restore.
B) Examine the status or the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server. 
C) The Windows account which starts the NetBackup Client Service on the SQL server must have administrative rights to the directory where the database files are being placed. Restore the database to a directory path where the NetBackup Client Service account has administrative rights.
D) Confirm the restore is being launched from the client using the NetBackup Microsoft SQL Client GUI.
E) To restore to a different server or database, use an SQL move script
F) Assume the time required for a restore is the backup time multiplied by two. If backup took one hour, assume two hours for the restore
G) For restores of larger databases, it may be necessary to increase the client read timeout in the SQL server.
H) If the restore is initiated from a Terminal Server session, and then the session is ended, the restore fails with a timeout error.

I)Change the values in the restore script of: MAXTRANSFERSIZE and NUMBUFS

J) Check the following NetBackup logs for additional failure information at the SQL side(Netbackup logs are not enabled by default):

install_path\NetBackup\logs\dbclient
install_path\NetBackup\logs\bpbkar (Snapshot Client)
install_path\NetBackup\logs\bpfis (Snapshot Client)
install_path\NetBackup\logs\bppfi (instant recovery)
install_path\NetBackup\logs\user_ops\MsSql\logs

If no clue can be found in the logs, try increasing the log verbosity:

1. Connect to the SQL server
2. Choose Start > Programs > VERITAS NetBackup > Backup, Archive, and Restore.
3. Choose File > NetBackup Client Properties.
4. Click the Troubleshooting tab.

Set the General debug level to 2
Set the Verbose debug level to 5
Set the Database debug level to 9 
 

Then repeat the restore and check logs again.

K) Check the SQL server’s event viewer (application and system) for any errors or message related to the restore operation.
L) Review the Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide to make sure that the restore is being launched correctly.

Correct the problems that you find and retry the restore.