lol True
What we've found out is that its the firewall between media and client
which is cutting off this connection after 2 hours. The bpstart script
is still running on the client but after the firewall tcp timeout of 2
hours its as though part of the connection (i'm thinking the bpbrm
process) is terminated.
This causes netbackup to log a status 13 on the master but the job stays
active. I'm guessing it stays active becuase the master -> media server
is still open and netbackup has got in a mess.
There must be a way to sort this issue though if this is the chain :-
Master ---> Media --- [Firewall] ---> Client
when there are large bpstart jobs greater than Fw timeouts? Anyone any
ideas?
Cheers
Lightner, Jeff wrote:
> Logs?! Who needs logs?
>
> In the Windows world troubleshooting boils down to:
>
> If it doesn't work reboot it.
>
> If that doesn't fix it reinstall the application and reboot.
>
> If that doesn't fix it reinstall the OS reboot and reinstall the
> application.
>
> If that doesn't work update your resume and go somewhere where they
> don't have the gall to install software that can't be repaired with
> "standard" Windoze troubleshooting.
>
> :-)
>
> P.S. The vxlog thingy exists in UNIX/Linux as well and I agree it's a
> pain to use.
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dave
> Markham
> Sent: Friday, May 14, 2010 9:57 AM
> To: Whelan, Patrick; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Strange status 13 during bpstart script
>
> Well on the client they are empty and on the master server windows its
> using the vxlog thingy which i've not looked at before. I.e there's
> nothing in ~netbackup\logs\bpbrm. :(
>
> I'm a unix engineer so find windows very frustrating as regards looking
> and searching through logs.
>
> cheers
>
> Whelan, Patrick wrote:
>
>> What do the brbrm logs say?
>>
>>
>> Regards,
>>
>> Patrick Whelan
>> NetBackup Specialist
>> Wholesale Markets and Treasury & Trading
>> Lloyds Banking Group
>> Desk: +44 (0) 207 158 6123
>> Loc: OBS 2C-132
>> P please don't print this e-mail unless you really need to.
>>
>>
>> -----Original Message-----
>> From: Dave Markham [mailto:dave.markham AT fjserv DOT net]
>> Sent: 14 May 2010 14:30
>> To: Whelan, Patrick
>> Subject: Re: [Veritas-bu] Strange status 13 during bpstart script
>>
>> No it's just set to 900 still.
>>
>> We could increase that, but if it's the CLIENT_READ_TIMEOUT why is
>>
> that
>
>> not being hit and exiting sooner.
>>
>> Looking at the history when there is a problem, its reporting out
>>
> status
>
>> 13 and this brbrm forcible shutdown after 2hours each time
>>
>> Cheers
>>
>> Whelan, Patrick wrote:
>>
>>
>>> Have you increased the CLIENT_READ_TIMEOUT parameter?
>>>
>>>
>>> Regards,
>>>
>>> Patrick Whelan
>>> NetBackup Specialist
>>> Wholesale Markets and Treasury & Trading Lloyds Banking Group
>>> Desk: +44 (0) 207 158 6123
>>> Loc: OBS 2C-132
>>> P please don't print this e-mail unless you really need to.
>>>
>>>
>>> -----Original Message-----
>>> From: Dave Markham [mailto:dave.markham AT fjserv DOT net]
>>> Sent: 14 May 2010 13:40
>>> To: Whelan, Patrick; veritas-bu AT mailman.eng.auburn DOT edu
>>> Subject: Re: [Veritas-bu] Strange status 13 during bpstart script
>>>
>>> Yeah sorry perhaps not explained correctly.
>>>
>>> The bpstart time out is 8 hours (28800)
>>>
>>> The status 74 is what we would expect to see on the Master Server job
>>> view, and is actually what the CLIENT bpbkar log shows after 8 hours
>>>
>>>
>> of
>>
>>
>>> the job hanging.
>>>
>>> However, the issue is the Master server is reporting Status 13 after
>>>
> 2
>
>>> hours of inactivity, i.e whilst the bpstart job is running on the
>>>
>>>
>> client
>>
>>
>>> and BEFORE the timeout is reached.
>>>
>>> Cheers
>>>
>>>
>>>
>>> Whelan, Patrick wrote:
>>>
>>>
>>>
>>>> I'm not quite sure what you are asking. Obviously the
>>>>
> BPSTART_TIMEOUT
>
>>>>
>>>>
>>
>>
>>>> needs to be increased. If the error 74s stop then the error 13s
>>>>
>>>>
>> should
>>
>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>> go away. Or am I missing the point altogether?
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Patrick Whelan
>>>> NetBackup Specialist
>>>> Wholesale Markets and Treasury & Trading Lloyds Banking Group
>>>> Desk: +44 (0) 207 158 6123
>>>> Loc: OBS 2C-132
>>>> P please don't print this e-mail unless you really need to.
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
>>>> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dave
>>>> Markham
>>>> Sent: 14 May 2010 12:37
>>>> To: veritas-bu AT mailman.eng.auburn DOT edu
>>>> Subject: [Veritas-bu] Strange status 13 during bpstart script
>>>>
>>>> Guys i've been reading on Status 13 quite a bit but am still
>>>>
>>>>
>> flummoxed
>>
>>
>>>> as to why we are getting this on an environment here.
>>>>
>>>> Ok
>>>>
>>>> Netbackup 6.0MP4 Windows 2003 Master server Netbackup 6.0MP4 Windows
>>>> 2003 Media server attached to EMC disk virtual storage.
>>>> Netbackup 6.0MP4 Linux Client running Suse linux
>>>>
>>>> Basically we run a bpstart script which waits for a flag to appear
>>>>
>>>>
>>>>
>>> from
>>>
>>>
>>>
>>>> another script ran from cron.
>>>> Once the flag is found we run a 3rd party application script to shut
>>>> down some applications.
>>>> Occasionally these 3rd party app shutdown scripts dont finish
>>>>
>>>>
>> properly
>>
>>
>>>> and dont return to our bpstart script so it just sits there.
>>>> After the bpstart time out is reached the bpbkar on the client shows
>>>>
>>>>
>> a
>>
>>
>>>> status 74 and exits.
>>>>
>>>> Now the weird bit.
>>>>
>>>> On the master server after 2 hours of the job starting a Status13 is
>>>> reported that the bpbrm process was forcibly terminated on the
>>>>
>>>>
>> client.
>>
>>
>>>> The job then sits as active in the activity monitor sometimes, and
>>>>
>>>>
>>>>
>>> other
>>>
>>>
>>>
>>>> times finished with status 13.
>>>>
>>>> As this isn't a windows client vsp and vss are not to blame.
>>>>
>>>> There are firewalls between media servers and clients though, so i
>>>>
>>>>
>> was
>>
>>
>>>> wondering if some network issue was to blame???
>>>>
>>>> Any pointers welcomed
>>>>
>>>> Cheers
>>>>
>>>> _______________________________________________
>>>> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>>>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>>>
>>>>
>>>> This e-mail is private and confidential and may contain privileged
>>>>
>>>>
>>>>
>>> material. If you have received this e-mail in error, please notify
>>>
> the
>
>>> sender and delete it immediately. You must not copy, distribute,
>>> disclose or use any of the information in it or any attachments.
>>>
>>>
>>>
>>>> Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh
>>>>
> EH1
>
>>>>
>>>>
>>>>
>>> 1YZ. Registered in Scotland, number 95000. Telephone: 0131 225 4555.
>>>
>>>
>>>
>>>> Lloyds TSB Bank plc. Registered Office: 25 Gresham Street, London
>>>>
>>>>
>> EC2V
>>
>>
>>>>
>>>>
>>>>
>>> 7HN. Registered in England and Wales, number 2065. Telephone: 020
>>>
> 7626
>
>>> 1500.
>>>
>>>
>>>
>>>> Lloyds TSB Scotland plc. Registered Office: Henry Duncan House, 120
>>>>
>>>>
>>>>
>>> George Street, Edinburgh EH2 4LH. Registered in Scotland, number
>>>
>>>
>> 95237.
>>
>>
>>> Telephone: 0131 225 4555.
>>>
>>>
>>>
>>>> Cheltenham & Gloucester plc. Registered Office: Barnett Way,
>>>>
>>>>
>>>>
>>> Gloucester GL4 3RL. Registered in England and Wales, number 2299428.
>>> Telephone: 01452 372372.
>>>
>>>
>>>
>>>> Cheltenham & Gloucester Savings is a division of Lloyds TSB Bank
>>>>
> plc.
>
>>>> Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham &
>>>>
>>>>
>>>>
>>> Gloucester plc are authorised and regulated by the Financial Services
>>> Authority.
>>>
>>>
>>>
>>>> Telephone calls may be monitored or recorded.
>>>>
>>>>
>>>>
>>>>
>>>>
>> ______________________________________________________________________
>>
>>
>>>> This email has been scanned by the MessageLabs Email Security
>>>>
> System.
>
>>>> For more information please visit http://www.messagelabs.com/email
>>>>
>>>>
>>>>
>> ______________________________________________________________________
>>
>>
>>>>
>>>>
>>>>
>>>>
>>>
> ______________________________________________________________________
>
>>> This email has been scanned by the MessageLabs Email Security System.
>>> For more information please visit http://www.messagelabs.com/email
>>>
>>>
> ______________________________________________________________________
>
>>>
>>>
>>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the MessageLabs Email Security System.
>> For more information please visit http://www.messagelabs.com/email
>> ______________________________________________________________________
>>
>>
>>
>>
> Wel
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
> Proud partner. Susan G. Komen for the Cure.
>
> Please consider our environment before printing this e-mail or attachments.
> ----------------------------------
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
> information and is for the sole use of the intended recipient(s). If you are
> not the intended recipient, any disclosure, copying, distribution, or use of
> the contents of this information is prohibited and may be unlawful. If you
> have received this electronic transmission in error, please reply immediately
> to the sender that you have received the message in error, and delete it.
> Thank you.
> ----------------------------------
>
>
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
