ADSM-L

Re: [ADSM-L] LABEL LIBV & VOLHIST problem

2007-06-06 15:04:46
Subject: Re: [ADSM-L] LABEL LIBV & VOLHIST problem
From: William Boyer <bjdboyer AT COMCAST DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Jun 2007 15:03:50 -0400
If you are completely...totally sure that TSM-SERVER-3 has no record of this 
volume, you can do a couple things:

1. AUDIT LIBRARY <library> CHECKL=B on the library client. This will re-sync 
the OWNER of the tapes checked in and the TYPE=REMOTE
entries in the volhist on the library manager.

2. On the library manager issue "del volhist type=remote force=yes 
volume=OI0066" to remove the entry from the volhist.

#1 is probably the easiest.

Bill Boyer
"A life? Cool! Where can I download one of those?" - ??


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Michael Green
Sent: Wednesday, June 06, 2007 2:14 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: LABEL LIBV & VOLHIST problem

On 6/6/07, Richard Sims <rbs AT bu DOT edu> wrote:
> On Jun 6, 2007, at 10:30 AM, Michael Green wrote:
>
> > I'm just looking for a confirmation of my assumption that I cannot
> > label/checkin stat=scr because it appear to belong to TSM-SERVER-3
> > in the volume history. If yes (or if no) how can I fix this?
>
> Michael -
>
> This gets back to procedures.  The TSM server on which you performed
> the volume history examination said the volume type is REMOTE, which
> means that it belongs to a library client, ostensibly a TSM server
> separate from the one on which you performed the examination.  The
> Volume Location field identifies the owner server, where management of
> the volume should occur.  Refer to the Admin Guide manual for the
> procedures.

Richard, thanks. I have no problem with reading the documentation.
I have examined the volhistory file on both servers (event though I didn't 
mention it in my initial email). The owner server
(TSM-SERVER-3) doesn't contain any record related to the volume (OI0066).  It 
only appears on the server that manages the library.
This leads to the situation when one server points to the other server. And the 
other server has no idea of the volume whatsoever.
And based on that the first server thinks the volume is managed by the second 
server it refuses to LABEL/CHECKIN it as SCRATCH
volume.


--
Warm regards,
Michael Green