pls post dbclient log from SQL client. If log directory is not created , create it and perform the restore again. Make sure you increase verbosity of logging from backup archive and restore (general 2, verbose 5)

below URL will help you....

https://www-secure.symantec.com/connect/articles/how-backup-and-restore-microsoft-sql-server-backup-netbackup

http://www.symantec.com/business/support/index?page=content&id=TECH35344

ur trying to do redirect SQL restore.

1 ON master server

- Create this directory:  <install_path>\NetBackup\db\altnames 

First of all, test SQL backup on destination client.

Comms is different when database backup is done - SQL client initiates connection to master, master then needs to resolve client's incoming IP address to valid hostname. 
This does not happen with filesystem backup.

During restore, client initiates connection to master. Master needs to resolve client's IP address to valid hostname and check/verify permissions for this client name to browse/restore source client's data.

Please follow steps in NBU for Microsoft SQL Server Admin Guide  .

Look for topic called: Redirecting a restore to a different host.

Step 1 is done on master server. Creating No.Restrictions file is the easiest.

Step 2 onwards is done on Destination Client.

Also read this section in the same manual: Minimizing timeout failures on large database restores.

Be sure to create log folders before you start. This is the only way to troubleshoot failures:

On master: bprd (NBU needs to be restarted to enable bprd logging)

On media server: bpbrm and bptm (no restart needed)

On destination client: (bpcd and dbclient)

Please rename logs to reflect process name (e.g. bprd.txt) and post as File attachments.

Hello,

Thanks you for hints.

Finally I see restore job on master server but it failed with RC 5. Here is status:

10.8.2012 10:49:23 - begin Restore
10.8.2012 10:49:24 - Info dbclient (pid=9184) INF - RESTORE STARTED USING
10.8.2012 10:49:24 - Info dbclient (pid=9184) Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
10.8.2012 10:49:24 - Info dbclient (pid=9184) Apr  2 2010 15:48:46
10.8.2012 10:49:24 - Info dbclient (pid=9184) Copyright (c) Microsoft Corporation
10.8.2012 10:49:24 - Info dbclient (pid=9184) Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
10.8.2012 10:49:24 - Info dbclient (pid=9184) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\redirect_restore_ttpb_full.bch, Op# = 1.
10.8.2012 10:49:24 - Info dbclient (pid=9184) INF - Restoring from <2> images. The first is <TTPBP-A0001.MSSQL7.TTPBP-A0001\TTPB_D.db.TTPB.~.7.001of002.20120808075135..C>.
10.8.2012 10:49:24 - Info dbclient (pid=9184) INF - Number of stripes: 2, Number of buffers per stripe 2.
10.8.2012 10:49:24 - Info dbclient (pid=9184) INF - Created VDI object for SQL Server instance <TTPB_D>. Connection timeout is <300> seconds.
10.8.2012 10:54:26 - Info dbclient (pid=9184) ERR - Error in GetConfiguration: 0x80770003.
10.8.2012 10:54:26 - Info dbclient (pid=9184)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
10.8.2012 10:54:27 - Info dbclient (pid=9184) DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'VNBU0-9184-12172-1344588564'. Operating system error 0x80070002(The system cannot find the file specified.).>.
10.8.2012 10:54:27 - Info dbclient (pid=9184) DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally.>
10.8.2012 10:54:34 - Info dbclient (pid=9184) ERR - Error in VDS->Close: 0x80770004.
10.8.2012 10:54:34 - Info dbclient (pid=9184)     CONTINUATION: - An abort request is preventing anything except termination actions.
10.8.2012 10:54:34 - Info dbclient (pid=9184) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\redirect_restore_ttpb_full.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 311(311) seconds.
10.8.2012 10:54:36 - Info dbclient (pid=9184) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\redirect_restore_ttpb_full.bch>:
10.8.2012 10:54:36 - Info dbclient (pid=9184) <0> operations succeeded. <1> operations failed.
 

Do you have some idea what is wrong now? Thanks in advance.

Have you read through all the documentation in my previous post?

You need to increase timeouts on media server dramatically for restores!

The default of 5 minutes (300 seconds) is not nearly enough.

Please also see the following troubleshooting logs (also in my previous post):

Be sure to create log folders before you start. This is the only way to troubleshoot failures:

On master: bprd (NBU needs to be restarted to enable bprd logging)

On media server: bpbrm and bptm (no restart needed)

On destination client: (bpcd and dbclient)

Please rename logs to reflect process name (e.g. bprd.txt) and post as File attachments.

**** EDIT *****

Collection of TN's for SQL backup and restore issues: http://www.symantec.com/docs/TECH74475

Hi,

I tried to find something in dbclient, bpcd logs and in mssql_backup_failures log.(see attached files) 

In mssql_backup_failures is:

STATUS -1
INFO Error in GetConfiguration: 0x80770003.
INFO The api was waiting and the timeout interval had elapsed.

I found some topic regarding this:

http://www.symantec.com/connect/forums/failed-sql-...

Connection checked through commands

bpclntcmd -hn <hostname>
bpclntcmd -ip <ip-address>

seems to be ok, right names and IP addresses, reachable...

Is something in logs what I overlooked?

Check if this helps

http://www.symantec.com/docs/TECH42958

I don't see any of the following logs:

master's bprd log

media server's bpbrm and bptm logs.

We need to first of all see how master interpreted client's restore request. This will tell us why we see status 37's in dbclient log.