NetBackup Status Code 74

[baba20009]

I get this error running

1/26/2012 9:39:21 AM - connected; connect time: 00:00:01
1/26/2012 9:44:22 AM - Error bpbrm(pid=3952) from client dalfilesvr01: ERR - bpstart_notify timed out    
1/26/2012 9:44:22 AM - Error bpbrm(pid=3952) could not send server status message      
1/26/2012 9:44:26 AM - end writing
client timed out waiting for bpstart_notify to complete(74)

***

using NetBackup version 6.5.6

running a differential backup policy

Thanks

[Will_Restore]

bpstart_notify script on the client is taking too long to complete.  If you are certain it is working as it should, you can increase  BPSTART_TIMEOUT  on the media server.

URL http://www.symantec.com/docs/TECH57953

[smakovits]

If you are not sure if it is working or not, you can also try copying the bpstart_notify from a working to the one that is failing to see if that doesnt work.  

[Mark_Solutions]

Just to clarify the is bpstart_notify timeout is per client and found on the clients host properties Ensure that the script actually runs to completion Post it on here for examination if you wish It will be on the client in the NetBackup/bin directory

[baba20009]

I checked and most of my clients do not have bpstart_notify.bat.  this particular server did have one! so i renamed it and now I am getting this error:

1/26/2012 1:57:36 PM - connected; connect time: 00:00:01
1/26/2012 1:57:43 PM - Error bpbrm(pid=5256) could not send server status message      
1/26/2012 1:57:48 PM - end writing
none of the files in the file list exist(71)

[Will_Restore]

sounds like your bpstart is supposed to mount a remote filesystem (CIFS, NFS, etc)

maybe that went away?  check with the server admin.  if so, then remove the path from the policy backup selections.

[baba20009]

I am not clear what I am supposed to do now.

the bpstart_norify.bat on fileserver that i renamed had one line in it net use map a nas box which i do not want to backup anymore.

if I rename back to original i would get error 74

[Will_Restore · Accepted solution]

remove the nas path from the policy backup selection

[baba20009]

so the file will be empty.  it only has one line

[Marianne]

Find out from system owner what needs to be backed up.

If this path in Backup Selection should no longer be backed up, deactivate or delete the policy.

[Will_Restore]

 nothing to back up then so you can go home

[baba20009]

more detail:

Policy 1 had two servers to do cumm diff backup daily (server A & Server B).

Server B no loner needed to backup so i removed couple yesterday).

Server A backuped failling

Server A had the bpstart_norify.bat with one line in net use to map to Server C.  Server C is a NAS.  I do not care about now.

I am the netbackup two admin shop backing up 100 servers.

i am trying to backup server A only.  full backup runs Friday night for Server A.

I wish i could go home with no backup!!

[baba20009]

Got Server A backup running. 

Thanks Wrobbins "remove the nas path..." did the

Thanks all for responses.

[baba20009]

Any ideas why Server A had bpstart_notify.bat file and non of other servers had this file? 

My partner and I have no idea how map to nas server got put in this file!!

[Will_Restore]

Somebody at your site set it up that way, maybe some time ago.  There is sample file on the Master server but obviously it would have no knowledge of specific NAS mapping. 

[baba20009]

ok that make sense long time ago.