16:01:54.259 [15948.16636] <2> do_pbx_service: [vnet_connect.c:2116] via PBX bprd CONNECT FROM 10.66.30.4.55971 TO 10.66.30.11.1556 fd = 1256
16:01:54.259 [15948.16636] <2> async_connect: [vnet_connect.c:1644] connect async CONNECT FROM 10.66.30.4.55971 TO 10.66.30.11.1556 fd = 1256
16:01:54.259 [15948.16636] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO whbrtwnbu01 10.66.30.11 bprd VIA pbx
16:01:54.259 [15948.16636] <2> logconnections: BPRD CONNECT FROM 10.66.30.4.55971 TO 10.66.30.11.1556 fd = 1256
16:01:54.259 [15948.16636] <2> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:843] Assuming no VxSS for DB Agents 0 0x0
16:01:56.349 [15948.16636] <16> writeToServer: ERR - send() to server on socket failed:
16:01:56.349 [15948.16636] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket

Looks like its not able to communicate with master server.

what is the below command output in Client, it will tell you if client able to connet the master server or not

bpcltncmd -pn

if it did not return anyting..

you may need to check your hosts and registory entiries.

Check your setup

16:12:56.476 [4364.4464] <16> CDBbackrec::CDBbackrec: USER - Verify that an active SQL Server policy exists for this client

16:12:58.582 [4364.4464] <8> VxBSADeterminePolicy: WARNING - NBBSA_CLIENT_HOST name= <WHBRTWSQLBC01> differs from NBU config name= <whbrtwssc01>
 

You may need to create this file on your Master server

C:\Program Files\Veritas\NetBackup\db\altnames\No.Restrictions

Please show us your backup script.

Which hostname is physical nodename and which one is virtual hostname? (WHBRTWSQLBC01 / whbrtwssc01 )
Which hostname is defined in backup policy?

Seems these errors can be ignored:

16:01:56.349 [15948.16636] <16> writeToServer: ERR - send() to server on socket failed:
16:01:56.349 [15948.16636] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket

See TN: http://www.symantec.com/docs/TECH182435

Other errors in dbclient log:

 <16> CDBbackrec::InitDeviceSet_Part2(): ERR - Error in GetConfiguration: 0x80770003.

<16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'VNBU0-15948-9352-1357747320'. Operating system error 0x80070002(The system cannot find the file specified.).>.

<16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.>

These errors look like SQL errors - not NBU. 
Have you checked Event Viewer Application log as well as SQL Error log?

I always recommend to run NBU Client Service account with the same logon account that is used for SQL services.

Script looks good.

Please ask your SQL dba to have a look at the error in Application log. This is not NBU error...

They should also check SQL Error and VDI logs.

Just a few basics here to make sure things were right from the start ...

1. On the client have you opened the NBU SQL Agent GUI and set the authentication to the SQL Database - it is this that gets used rather than the client service when doing the backup - I am guessing that you have as the script has been produced but wanted to double check

2. Can the client communicate with the Master Server properly - all file system backups only communicate with the Media Servers - SQL backups are different as they communicate directly with the Master before they communicate with the Media Servers

3. As Marianne says check the clients event logs - unusual for 2008R2 to have such issues but worth checking it is up to date with all patches / hotifxes from Microsoft etc.

4. Your first posted log also indicates that a connection is forcibly closed - it effectively times out after 5 minutes whilst preparing the script - please increase the client read timeout on your Master and Media Servers - the log indicates it is set to 300 so try 1800 for now

5. In view of the client name difference shown i am wondering if this is a clustered server? If so have you set the Agent GUI authentication on both nodes? Does the policy use the Virtual name?

Hope this helps / guides you

Have a look at this Microsoft forum discussion - especially George M Jones with W2008 and SQL 2005 in 2-node cluster:

http://social.msdn.microsoft.com/forums/en-US/sqldatabaseengine/thread/2df560fe-0c4d-4ce6-a651-3abfcbf62574 

See how he managed to fix the problem in his last post...

No idea if this is applicable to your environment, but try to convince the SQL DBAs that you need to work together to find a solution.
Check SQL Error and VDI logs for additional info.

Have you tried to log into SQL GUI interface as the same user used for NBU services, and do a backup to local disk? Is that working fine?

Please check the with DBA team the path are exist on destination server where u doing a restoration.

As we check the dbclient log it shows the below error.

"<16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'VNBU0-15948-9352-1357747320'. Operating system error 0x80070002(The system cannot find the file specified.).>." 

Regards

Bharat

== update ==

OK, try this

NetBackup Management > Host Properties

Action > Configure Client

  enter the physical client name

Client Properties > Client name

  enter the virtual computer name

OK

Run the backup job again

Hi All ,

I just found that the nslookup forward and backward is running fine for the Virtual cluster name , but when I try to connect the host property of the virtual server its showing , connection refused , but both my physical host are able to connect with the client host property 

backup is failing with EC 59?

are you able to make the file system backups?

do you have the correct server entires made in registory of client

please provide the bpcd log.

if you dont have the log.

create a bpcd directory in client /installpath/veritas/netbackup/logs/bpcd 

and then try backup, and provide the bpcd log 

Attach current logs, please: bphdb, bpclient, bpcd

WR -> you should probably create a seperate thread for you issue.

As for Status 59, please revisit requirements

NetBackup status code: 59

Message: access to the client was not allowed

Explanation: The master or the media server tries to access the client, but the

client does not recognize the server as a valid server.

If the server is a valid server, verify that it is in the server list on the client. If

necessary add it as follows:

■ On Windows clients: Add the server on the Server to use for backups and

restores drop-down in the Specify NetBackup Machines and Policy Type

dialog box. To display this dialog box, start the Backup, Archive, and Restore

interface on the client. Then click SpecifyNetBackupMachinesandPolicy

Type on the File menu.

Hi All ,

Issue is resolved as client is instead of using the backup LAN for connecting the master \media server , using  the Management network , due to which backup is failing .

Want to say thanks all of them for providing me valuable feedback and suggestion 

First time you mentioned backup LAN?

If we knew from the start we would've referred you to this section in NBU for SQL manual:

then why I need to add the master server entry  on the client machine

Where did you need to add master server entry?
In hosts file?

Did you test forward and reverse lookup for backup NICs / IPs?
Are there different hostnames for the backup IPs in DNS?

Did you go through the section in the manual to config cluster backups for backup network?