Error bpbrm (pid=36700210) socket read failed: errno = 119 - System call timed out - file read failed (13)

Do you have bpfis and bpbkar log folders on the client?

Please create the log folders and increase logging level to 3.

It might be a good idea to actually log onto the client when the backup starts to see what is happening.

Trace steps in bpstart_notify script and look at logs for further clues.

PS: 

I have moved this post to NBU forum as it does not seem to be an Appliance issue.

Thanks  Marianne

Will provide logs once available, but how can we trace steps of bpxxxx_notify scripts?

Last night backup failed with error 71, looks like script unable to mount drive and unmount it, need really to track bpstart & bpend notify scripts,  please help

Thanks Marianne

We able to fix the script , drives are mounting & unmount OK now, but another issue we have now is

On testing out bpstart & bpend notify scripts for multistreaming jobs found that they get called for each child job because we got two SAN drives which get mounted when bpstart_notify start but if any of the stream completed, then it goes to bpend_notify and unmount both drives same time.

So how do we fix the script so it won't call immediately after any child job finishes rather it called bpend when parent job completed, please advise

Hi Guys

I found this article, I think this is exactly solution we required, but need help in editing script

https://support.symantec.com/en_US/article.TECH69986.html

OR , question I have, If we create two policies, one for each SAN drive, so can we have have two bpstart & bpend policies?

For eg:-

Policy 1 schedule at   2 am

Policy 2 schedule at 2 am

bpstart_notify.Policy1.bat

bpstart_notify.Policy2.bat  and same with bpend

Is it possible?

Hi LIMRA !

Yes it is possible. You can have bpstart/bpend scripts as bpend_notify.policy.schedule.bat or only for policy or only as generic (every policy every schedule)

These notify scripts are triggered by bpbkar/bpbkar32.exe. In multisteam Backups you have bstart/bpend scripts running for every bpbkar.

If your intention is to notify you should use parent_start_notify and parent_end_notify. These scripts are running on master server.

A complete list of scripts you will find here: http://www.symantec.com/docs/HOWTO106041

If you like to something on your client before and after backup (stop-start service or application) you should setup a policy with the backuptarget where these steps are needed. So if you backup F:\mysql for example you can have a policy backup up all end exclude F:\ an a second policy backup up F:\ and a script for start and stop of mysql. (Iknow mysql is a bad exqample since there is a 3th party agent for :- )

If not:

The idea is in bpstart_notify to pick up the first stream and let them all do and in bpend_notify to pick up the last stream haes finishing.

these scripts are running with parameters:

%1 = CLIENT_NAME
%2 = POLICY_NAME 
%3 = SCHEDULE_NAME 
%4 = SCHEDULE_TYPE, one of the following: FULL, INCR, CINC, UBAK, UARC
%5 = STATUS, always 0
%6 = RESULT_FILE

known variables are:

• STREAM_NUMBER  number of streams  (1 smallest, 0 if no Multistreaming)
• STREAM_PID             Prozess-ID des bpbkar
• STREAM_COUNT     number of Streams in job

example from bpstart_noify.bat

REM Services to Stop
@REM --------------------------------------------------------------------
@REM BPSTART_NOTIFY.bat 4 Multistream Beginn
@echo "" > "C:\Program Files\VERITAS\NetBackup\scripts\%1.%2.%STREAM_PID%"
@REM Wenn erster Stream der Policy, dann Stop von
@if %STREAM_NUMBER%==1 goto :STOP

goto :NOSTOP

:STOP
@REM Hier Stoppen von ... Eintragen
NET STOP "xxxxx"

:NOSTOP
@REM BPSTART_NOTIFY.bat 4 Multistream Ende

example for bpend_notify.bat

REM Services to Start
@REM-----------------------------------------------------------------------
@REM BPEND_NOTIFY.bat 4 Multistream:
@del "C:\Program Files\VERITAS\NetBackup\scripts\%1.%2.%STREAM_PID%" /Q
@if not exist "C:\Program Files\VERITAS\NetBackup\scripts\%1.*" goto :START

goto :NOSTART

:START
@REM Hier das Starten von ... eintragen
NET START "xxx"

:NOSTART

@REM BPEND_NOTIFY.bat 4 Multistream:

So the idea behind:

The first stream have to do something in bpstart_notify. Every stream writes a PID-File.

After backup every stream deletes his own PID-File and look for other PID-Files. If no PID-file exists it have to do something in bpend_notify.

I found this solution somewhere in symantec. (but cant find now)

The disadvantage is if the backup processes are killed it is possible that the pid-files are left over.

Next time bpend_notify will not do what it should.

ciao

Martin