Re: [Veritas-bu] (no subject)

Thanks TIm,

I understand what you mean and thats what i used to think, but bptm has already selected the media and is stating it is writing. I've checked ACS logs and can see the associated mount and no subsequent job grabs the same tape. So in effect it's saying it can't lock the media itself, not sure whether the old SCSI reserve comes in to play and something has been left around from a previous mount. I'm prepared to be completely blown out of the water.

MP6 at the moment/

Mike

Michael Ketley
Senior Support Analyst
Storage Support
* e-mail: michael.ketley AT orange-ftgroup DOT com
( Mobile: +44 (0)7968 409214

-----Original Message-----
From: Tim Hoke [mailto:thoke AT northpeak DOT org]
Sent: 06 May 2008 15:16
To: KETLEY, Michael
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] (no subject)

Michael,

The "unable to lock media" message has to do with bptm selecting media. Without the log, my guess is that you'll see bptm is attempting to obtain a piece of media for a backup. One part of that process is going through it's local mediaDB to see if it fan find a match for what it needs (correct volume pool, retention, etc). If a particular tape is in use, then you'll see the "unable to lock media" message.

I don't think this is related to the problem you originally posted. BTW, what patch level?

-Tim

On Tue, May 6, 2008 at 8:47 AM, <michael.ketley AT orange-ftgroup DOT com> wrote:

Folks,

Not sure whether anyone can help or give a workaround solution?

We're having issues in NBU 5.1 environment with HP-UX media servers and jobs
not going to end writing. This is a fairly irregular occurrence but always
tends to occur with logical logs in the middle of the night (oh joy!). This
isn't a scheduler issue as everything else chugs along nicely. We're using
ACSLS 7.1.0.

>From bptm logs I can see lots of occurences of "12:08:30.310 [27067] <2>
db_lock_media: unable to lock media at offset 14' . Which could mean the
media is in use by another host, but I know it isn't. My guess is theres a
communication error between Media server and ACSLS.

So my question is, what can I do to kickstart this? Sometimes I can go into
the Activity Monitor and end job, and it miraculously finishes. Other times
when on-bar processes go, then it's a Master server restart.

Regards
Mike K

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu