01-26-2012 09:40 AM
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
Solved! Go to Solution.
01-26-2012 01:37 PM
remove the nas path from the policy backup selection
01-26-2012 10:24 AM
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.
01-26-2012 10:36 AM
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.
01-26-2012 10:53 AM
01-26-2012 12:01 PM
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)
01-26-2012 12:58 PM
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.
01-26-2012 01:29 PM
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
01-26-2012 01:37 PM
remove the nas path from the policy backup selection
01-26-2012 01:40 PM
so the file will be empty. it only has one line
01-26-2012 01:45 PM
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.
01-26-2012 01:46 PM
nothing to back up then so you can go home
01-26-2012 02:16 PM
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!!
01-26-2012 04:03 PM
Got Server A backup running.
Thanks Wrobbins "remove the nas path..." did the
Thanks all for responses.
01-27-2012 08:01 AM
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!!
01-27-2012 08:09 AM
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.
01-27-2012 09:11 AM
ok that make sense long time ago.