Hi.

Don't use the  vmquery -deassignbyid  command. It will only cause you
headaches. When using this command, the tapes are not cleaned up correctly
(see http://seer.support.veritas.com/docs/241574.htm).
When you want ot expire tape always use the bpexpdate command. Only if this
fails should you use  vmquery -deassignbyid  .

I would suggest that you print all tapes assigned to all media servers
seperatly (use bpmedialist -h <mediaserver>). Check to see if you have tape
that show up on different servers.

I had a customer that used  vmquery -deassignbyid  , and he ended up having
tapes assing to multiple media servers. He had an SSO enviroment though, I
don't know if this is your case (If you have media servers using the same
robot and most probably the same tapes, you could have a problem)

Regards,
Jim Peppas

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Martin,
Jonathan (Contractor)
Sent: Monday, December 19, 2005 4:56 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Media Experation

N00b question here I know, but what sets the media expiration date?  I'm
taking over a Netbackup 5.1 environment and we seem to have a load of issues
with media never expiring / having to vmquery -deassignbyid to get stuff to
go back into the scratch pool.  I'd say the GUI is useless for 80% of my
media returns from offsite.

-Jonathan

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