Veritas-bu

Re: [Veritas-bu] Media Server Issue

2007-07-18 06:48:10
Subject: Re: [Veritas-bu] Media Server Issue
From: Justin Piszcz <jpiszcz AT lucidpixels DOT com>
To: "Clooney, David" <david.clooney AT bankofamerica DOT com>
Date: Wed, 18 Jul 2007 06:35:06 -0400 (EDT)

On Wed, 18 Jul 2007, Clooney, David wrote:

> Hi All
>
>
>
> We have a unusual situation going which maybe some of you have come
> across?
>
>
>
> Environment - all 5.1 MP5
>
> Mater - Solaris 8
>
> Media Servers - winodws2000/2003
>
>
>
> On Friday we started to experience numerous "Status 52: timed out
> waiting for media manager to mount volume".
>
>
>
> After a nightmare of a weekend we are still having issues. The following
> is what I have found.
>
>
>
> We have a particular media server that seems to be causing the issue for
> reasons unknown.
>
>
>
>> From testing when this media is up and Netbackup is up or down and I
> initiate a restore on another media server, the job starts and I can see
> the mount request in the ACSLS log, however the job will staying in a
> mounting state.  If I then reboot the problem media server( I think) and
> keep a constant ping on the server, as soon as I lose ip connectivity
> the job on the other media server will immediately issue the SCSI
> reserve on the drive and the restore will complete.
>
>
>
> For some reason this media server seems to causing mount requests to
> complete throughout the environment just by being powered on as I have
> tested with netbackup DOWN.
>
>
>
> All our media servers are SAN connected and  are sharing 14 stk 9940B
> drives, I have rebuilt the SSO environment and we have no discrepancies
> in the global device DB.
>
>
>
> It just seems that when this problem media server is powered on it is
> causing issues.
>
>
>
> Anyone have any ideas ?
>
>
>
> Thanks
>
>
>
> Dave
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Notice to recipient:
> The information in this internet e-mail and any attachments is confidential 
> and may be privileged. It is intended solely for the addressee. If you are 
> not the intended addressee please notify the sender immediately by telephone. 
> If you are not the intended recipient, any disclosure, copying, distribution 
> or any action taken or omitted to be taken in reliance on it, is prohibited 
> and may be unlawful.
>
> When addressed to external clients any opinions or advice contained in this 
> internet e-mail are subject to the terms and conditions expressed in any 
> applicable governing terms of business or client engagement letter issued by 
> the pertinent Bank of America group entity.
>
> If this email originates from the U.K. please note that Bank of America, 
> N.A., London Branch and Banc of America Securities Limited are authorised and 
> regulated by the Financial Services Authority.
>

Usually when I get that, it is because of a DOWN'd drive, bad TAPE or 
robotic error, is it only happening on that one media serve? If so the 
drives may be no good.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>