Interesting. I've never seen one of our tapes do that.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Allen S. Rout
Sent: Tuesday, March 28, 2006 1:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Update - Tape problem after moving TSM to new s
>> On Tue, 28 Mar 2006 12:28:00 -0500, "Prather, Wanda" <[EMAIL PROTECTED]>
>> said:
> If a tape is is marked READWRITE/READINLY, it doesn't become
> eligible for reclaimation until it is marked FULL. If a tape is
> marked OFFSITE, it becomes eligible for reclamation as soon as
> %reclaim is be
sday, March 28, 2006 2:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Update - Tape problem after moving TSM to new server
I have never seen reclamation take a Filling volume. I thought the Big
Idea ever since the product was called WDSF was to fill up the Filling
volumes until they are Full, let
>> On Tue, 28 Mar 2006 00:59:53 -0600, Roger Deschner <[EMAIL PROTECTED]> said:
> I have never seen reclamation take a Filling volume. I thought the
> Big Idea ever since the product was called WDSF was to fill up the
> Filling volumes until they are Full, let expiration gradually eat
> holes in t
Hello Roger
I have seen it happen. We have collocate turned on for the tape storage pools.
We had several clients that had very little in the way of changing data, with
this usage pattern, we can see a filling tape that is mostly expired holes and
it will reclaim. It does not happen very offen,
Hi,
its really no problem but something changed since we are using the bigger
3592 drives - the volumes increased here from 40 GB -> 300 GB
and at the same time we started to use group-collocation.
After one year in use now Volumes are much more longer in 'filling'.
So of course it's nothing else
Hi Gary
I did as you suggested and commented out the entries in the
/kernel/drv/st.conf file and now when I boot -r, I see just the 0 and 1 IBM
entries that I wanted, so that's great news, many thanks.
Now I just hope that it solves my strange little 'unable to write to
filling tapes' problem.
A
I have never seen reclamation take a Filling volume. I thought the Big
Idea ever since the product was called WDSF was to fill up the Filling
volumes until they are Full, let expiration gradually eat holes in them,
and then reclaim them. What's the point in reclaiming a tape that isn't
full yet? Ev
On Mar 27, 2006, at 1:56 AM, Rainer Wolf wrote:
Hi,
Roger Deschner wrote:
3. The Full tapes should reclaim themselves normally. However,
reclamation will not select any tape that is still marked as
Filling, so
you've got to reclaim them manually yourself with MOVE DATA. Might
take
a while, w
Of course I have another problem with this. I only have 1 frame of a
3494 and not many free slots. If I set all the filling tapes to readonly,
after the next backup TSM will grab 36 brand new tapes (as I have
collocation on in the library, 1 for each client).
So realistically I would have to turn
Thanks Ian
Sadly I wont be able to do that until I try this upgrade again (possibly
this coming weekend). That's what is such a pain with this as I need to get
as many ideas together before I can even attempt it again :-(
Farren
|-+-
Try running the audit library checklabel=barcode to refresh the
library inventory in TSM from the library itself.
Check the help for the specifics associated with your library.
_
Ian Smith
SAN/TSM Specialist
IT Infrastructure
Rabobank International
Thames Court, O
Hi Ian
I only deleted and recreated the library, drives and paths, but I did not
touch the 3590 Device Class. Do I need to remove and recreate that too? If
I do this, how will it effect the tapepool & copypool that this device
class specified?
I actually printed screen dumps of the drives etc bef
Morning all
Regarding my problem with this, does anyone know what the following devices
are ? There are just two 3590s fibre attached to this new server so I don't
know where the other two came from or what they are. If it wasn't for them,
the drives would still have the same /dev/rmt/ mapping
Did you make any changes to mountlimit or format on the device classes? When
you recreated the drives and paths after the migration did you bind them to the
correct device class/device type?
After the migration did you audit the library?
_
Ian Smith
SAN/TSM Special
Good morning Roger
Thank you so much for that information. Backing out wasn't a big problem
for me as the old server was still left as it was so all I had to do was
connect the drives and lib again and bring it back up (phew).
This is a very annoying problem though. Surely TSM should be able to s
Hi,
Roger Deschner wrote:
>
> 3. The Full tapes should reclaim themselves normally. However,
> reclamation will not select any tape that is still marked as Filling, so
> you've got to reclaim them manually yourself with MOVE DATA. Might take
> a while, which is OK as long as you don't run out of
This happened to me too, when doing a similar migration. I looked up my
notes from the time.
The problem is that your Filling tapes were started on a different
drive type than you have now, and so it won't append any more data onto
them. (Even if they are the very same drives, this can still happe
18 matches
Mail list logo
