The big problem is that with two media servers thinking they both own
the same tape, they'll each go through and happily overwrite the other's
images. I've seen a tape marked as FULL on one media server and barely
used on a second - not pretty. 

Your best bet is going to be to expire the tape contents on each media
server (so the catalog is consistent again) and then import the tape
back into the catalog (from the server of your choice). Alternately, you
could run a media contents report against it and delete every image the
media servers showed except the ones on the report. Little easier to
mess that up though. 

That's the only way you're going to get a good feeling about the true
tape contents and your ability to restore images from that tape. 

- John Nardello

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Darren
Dunham
Sent: Friday, July 21, 2006 10:20 AM
To: Veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Duplicates in bpmedialist.

> Are you saying you have two media with the same barcode label?

Nope (at least I don't think so).

I believe there is one media and it had been "allocated" by different
media servers at different times (at some point in the past).  (Maybe
someone deassigned it instead of expiring it?)

> I've had
> that problem in the past with SDLT tapes.  I just ran the 
> mediacontents report on each tape.  You can't have them both in the 
> robot at the same time.  I always found that one of them didn't have 
> any images on it.  I took the empty tape label off, threw it away, and

> put a new label on it.

Even before you did that, did you have two 'bpemdialist' entries?
That's the bit I need to correct.  

One of them believes it is an empty, frozen tape.  The other thinks it
is a normal, full tape.  I want to tell the one that thinks it's empty
and frozen to get rid of it's information.

Interesting is that if I do 'bpmedialist -m <volume>' I only get one
entry. If I do 'bpmedialist | grep ^volume', I see it twice.  I think in
the first case after it finds an entry on one media server it stops
looking.

# bpmedialist -l | grep ^0151L2
0151L2 *NULL* 1 14 1099888658 1100061437 2147483647 1118707970 308609962
15 15 24 8 3 552 1024 0 1054426 0 0 0 0 0 0 0
0151L2 *NULL* 1 14 1078041614 0 0 0 0 0 0 3 5 0 17 1024 0 0 0 0 0 0 0 0
0 # 

status = 17 = 0x11.  Anyone know what status 0x10 bit is?  I don't see
that in the man page.

-- 
Darren Dunham                                           ddunham at taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >
_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu