The problem that the original poster was/is having, is that the media in
question exists in the volume database on the master server, but not in
any media database. This means, that unless his scratch pool is MISPD,
this tape will never be utilized in its current state, since it is
marked "assigned".
All that he needs to do in this case, is vmquery -m <mediaid> to get the
pool and status, then vmquery -deassignbyid <media id> <vol pool> 0
(zero, not the letter o)
What you need to be careful of when databases get out of sync, is that
you have media which contains live images in the image database, but has
no corresponding volume/media databse entry. This means, that the tape
is effectively a scratch tape and is readily available to NBU.
When I find these, I immediately move them to a volume pool called
"SAFE". None of our policies are configured to use the SAFE pool,
therefore, I won't run the risk of having these images overwritten. I
let them sit in the volume pool until they expire, at which time, they
will return to the scratch pool.
Another iteration of loss of sync, is media with entries in the image
and volume databases, but not corresponding entry in any media database.
In these cases, I just let them be, until such time that I need to use
the tape for a restore, at which time I do a Phase 1 import, which
returns it to the media server that it belongs to. Otherwise, I just let
the images expire and return to the scratch pool.
Last, there are cases where a piece of media has entries in the volume
and media databases, but not the image databases. What I want ot do in
these cases, is return these tapes to the scratch pool. Sometimes they
are simply frozen. Otherwise, it can be a little tricky, since it's
possible that the volume pool numbers don't match. If they do, I run:
bpexpdate -m <mediaid> -d 0 -justmedia -force
If the volume pools don't match, I run:
vmquery -m <mediaid> to get the pool and status, then vmquery
-deassignbyid <media id> <vol pool> 0 (zero, not the letter o)
HTH,
--Steve
Barber, Layne (Contractor) wrote:
> Tried the vmquery and here is what I got
>
>vmquery -m dou079
>Could not query by media ID DOU079: volume does not exist in database
>(35)
>
>-----Original Message-----
>From: Spearman, David [mailto:spe08 AT co.henrico.va DOT us]
>Sent: Wednesday, January 25, 2006 07:58
>To: Barber, Layne (Contractor); Robert Nusser;
>veritas-bu AT mailman.eng.auburn DOT edu
>Subject: RE: [Veritas-bu] Media id's not appearing in NB media database
>
>I had the same thing happen and got a solution from Veritas (excuse me,
>symantec). It is drastic but it does work. You need to know the tape ID
>and the pool number.
>
>install_path\volmgr\bin\vmquery.exe -deassignbyid <media-id> <pool-num>
>0 (that's a zero, use on a tape that is NOT a catalog)
>
>
>install_path\volmgr\bin\vmquery.exe -deassignbyid <media-id> <pool-num>
>1 (use for a catalog tape, must use bplabel after.
>
>To find a pool number
><install_path>\veritas\volmgr\bin\vmquery.exe -m XXXXXX where X is
>media ID
>
>You will get a nastygram about the database possibly being out of sync,
>ir has never happened to me but if you run a physical inventory followed
>by an NBU inventory you will definitely be in sync.
>
>
>David Spearman
>County of Henrico, Va.
>
>
>-----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 Barber,
>Layne (Contractor)
>Sent: Wednesday, January 25, 2006 8:48 AM
>To: Robert Nusser; veritas-bu AT mailman.eng.auburn DOT edu
>Subject: RE: [Veritas-bu] Media id's not appearing in NB media database
>
>
>I have a similar situation. I have a tape that shows up in the media
>list in the gui, but I can't delete it or anything. I get the message
>that the volume is not in the NB database.
>
>-----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 Robert
>Nusser
>Sent: Wednesday, January 25, 2006 04:58
>To: veritas-bu AT mailman.eng.auburn DOT edu
>Subject: [Veritas-bu] Media id's not appearing in NB media database
>
>Hi all,
>
>I am having problems with some of my media id's not appearing in the "NB
>media database". I have attempted bplabeling the tape again, and then
>assigning it with vmquery -assignbyid. Alas it seems I am back where I
>started and I can see the tape using vmquery, but I cannot see the tape
>using bpmedialist, and thus can also not freeze and unfreeze the tape. I
>also know the backups will fail on those tapes that I cannot see with
>the bp commands.
>
>I only have one standalone Veritas Netbackup server with the tape drives
>attached to it. Consequently supplying the -h switch to bpmedialist with
>the host name doesn't help either.
>
>So I would love to know how I can get this media id added to the NB
>media database?
>
>
># /usr/openv/volmgr/bin/vmquery -m MPDY56
>========================================================================
>====
>media ID: MPDY56
>media type: DLT cartridge tape 2 (16)
>barcode: --------
>description: Added by NetBackup
>volume pool: MISPD (6)
>robot type: NONE - Not Robotic (0)
>volume group: ---
>created: Mon Oct 31 22:08:37 2005
>assigned: Mon Jan 23 14:26:10 2006
>last mounted: Mon Jan 23 14:33:58 2006
>first mount: Mon Oct 31 22:08:38 2005
>expiration date: ---
>number of mounts: 3
>max mounts allowed: ---
>status: 0x0
>========================================================================
>====
>
># /usr/openv/netbackup/bin/admincmd/bpmedialist -ev MPDY56 requested
>media id was not found in NB media database and/or MM volume database
>
>
>Thanks,
>Robert
>
>
>
>
>_______________________________________________
>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>_______________________________________________
>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>_______________________________________________
>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
--
===================================
Steven L. Sesar
Senior Operating Systems Programmer/Analyst
UNIX Application Services R10A
The MITRE Corporation
202 Burlington Road - KS101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
mobile: (617) 893-9635
email: ssesar AT mitre DOT org
===================================
|
