Hi Linda

Thanks very much for posting that. I had actually spotted it on the
other forum but we had already trashed our installation ready for the
Production build by then. If it happens again I will definitely give it
a go.


I had a response from Symantec on the Vault 'feature' and after
investigation they have confirmed it was a bug:-

"Engineering have come back and said that they recognise the problem and
have fixed the code. The fix will be included in MP3, if its ultra
critical I can request a binary for you in the meantime. MP3 should be
available around July."


Regards

Richard

-----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 Linda
Bunty
Sent: Thursday, 27 April 2006 6:42 am
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NB 6.0 MP2 vault duplication - tape in use

     We upgraded to 6.0 mp6 on solaris for media and master server
yesterday.  We had the same with vault duplication.  I seen your message
of the Peer to Peer Newsgroups forum.  I post this there and emailing
what we found out last night.  I found on another site a workaround. 
According to the veritas forum it is a Solution from Symantec support:
 
Run "nbrbutil -dump" and analyze the output, looking for the "MDS
allocations in EMM" section. Find the allocation key for the tape that
is "in use".
 
Then run "nbrbutil -releaseMDS <allocation key #>".
 
The tape will now be released, and can be expired, moved, deleted, or
whatever you need to do with it. 
 

Here's the output of nbrbutil with no arguments (-help and -Q aren't
valid):
 
************
Arguments:
-dump -- dump all nbrb allocation and request list -dumptables -- have
nbrb log its internal state -release <GUID> -- Release the allocation
with the given identifier -cancel <GUID> -- Cancel the allocation
request with the given identifier -resetAll -- Reset all nbrb
allocations, requests, and persisted state -resetMediaServer mediaserver
-- Reset all nbrb EMM/MDS allocations related to LTID on the mediaserver
-listOrphanedMedia -- List media reserved in EMM but with no
corresponding allocation in RB -listOrphanedDrives -- List drives
reserved in EMM but with no corresponding allocation in RB
-listOrphanedStus -- List storage units reserved in EMM but with no
corresponding allocation in RB -releaseOrphanedMedia <name> -- Release
media reserved in EMM but with no corresponding allocation in RB
-releaseOrphanedDrive <name> -- Release drives reserved in EMM but with
no corresponding allocation in RB -releaseOrphanedStu <name> -- Release
storage units reserved in EMM but with no corresponding allocation in RB
-releaseMDS <ID> -- Release EMM/MDS allocations by MDS allocation ID
-releaseAllocHolds -- Release allocation holds due to alloction errors
for drives/media -suspend -- Suspend nbrb processing -resume -- Resume
nbrb processing
************* 
 
**URL got this from is:
http://forums.veritas.com/discussions/thread.jspa?threadID=61500&start=1
5&tstart=0

 

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


**********************************************************************
This electronic email and any files transmitted with it are intended 
solely for the use of the individual or entity to whom they are addressed. 

The views expressed in this message are those of the individual 
sender and may not necessarily reflect the views of the Christchurch
City Council.

If you are not the correct recipient of this email please advise the
sender and delete.

Christchurch City Council
http://www.ccc.govt.nz
**********************************************************************