OK, this is what I have now found out but had no idea what's going on. After completely removing and redefining the lib,drives and paths I still get the same errors as below. So, for example I can't
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
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 a
Author: "Smith, I (Ian)" <Ian.Smith AT RABOBANK DOT COM>
Date: Mon, 27 Mar 2006 11:00:41 +0100
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 th
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
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
Author: "Smith, I (Ian)" <Ian.Smith AT RABOBANK DOT COM>
Date: Mon, 27 Mar 2006 11:58:29 +0100
Try running the audit library <lib name> checklabel=barcode to refresh the library inventory in TSM from the library itself. Check the help for the specifics associated with your library. ___________
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 eve
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
Hi, 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 DAT
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
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 thank
Author: Rainer Wolf <rainer.wolf AT UNI-ULM DOT DE>
Date: Tue, 28 Mar 2006 12:58:42 +0200
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. A
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
I share this opinion. Acknowledging that there are times when it's a ridiculous distinction to make, ( i.e. 99% full volume that's 99% reclaimable ) the point of reclamation is to improve the chance
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Tue, 28 Mar 2006 12:28:00 -0500
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
I don't think this is the case any more. Here's an onsite reclamation example taken from today on one of my servers; the stgpool is collocated, and this volume, while mostly empty, is also mostly re
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Tue, 28 Mar 2006 14:02:53 -0500
Interesting. I've never seen one of our tapes do that. I don't think this is the case any more. Here's an onsite reclamation example taken from today on one of my servers; the stgpool is collocated,