I went thru this. Setting up a separate LibraryManagerServer that does nothing other than handling tapes is such a benefit that it outweighs having a small AIX machine (there is not such thing any more) doing nothing but.
However, the transition was, to use your word, cumbersome. My first thought was to checkout, remove=no, all those volumes whose category value was not that of the new LMS, and then check them in search=yes volr=whole-range owner=server. Unfortunately, search= and owner= are mutually exclusive. Fortunately, I had already used a select of all data volumes to a file. That I used to feed the individual checkin required by owner=. I had to repeat the process for server2. While the two processes were running, over a week for almost 2000 volumes, I couldn't check in any scratch with search=yes.
I hope someone may have found a better way.
At 03:41 PM 3/2/2005 -0600, you wrote:
Hi all,
Our current setup: 2 TSM servers, both at 5.2.3.0, both on AIX 5.2. TSM1 is the library manager server for a 3584 library; TSM0 is the library manager client. Both servers are 'full-fledged' in that they both have lots of clients that back up lots of data to them.
I'm considering changing to a configuration where we'd have a library manager server that does essentially nothing else, with the library client TSMs being the ones that actually have clients backing up to them. This seems to me to be a cleaner setup - it gives more flexibility in upgrading TSM server levels, for one thing.
My first thought is to set up a third TSM server - call it TSMTAPE - and make it the library manager, changing TSM1 to be a library client so that both TSM0 and TSM1 use TSMTAPE as their library manager server.
Most of the changes needed to accomplish this seem relatively straightforward, but I'm not so sure about the library inventory - the libvolumes table - that's currently in TSM1. Specifically, what's the best way to get all those libvolume entries out of TSM1 and into TSMTAPE? So far, all I've been able to come up with is some fairly ugly checkout/checkin scenarios, but that seems awfully cumbersome...I'd have to deal with scratch versus private, who owns the privates, etc. The 3584 has a bulk I/O door, which both eases and complicates things for the checkout and checkin processes. Perhaps using 'remove=no' on the checkout could save the physical moving around of tapes, but then it doesn't appear that I can specify 'owner=' on the checkin unless I'm checking in one tape at a time via the I/O door? It seems as if I'm looking at hundreds of single-tape checkins?
Has anyone else already been through this? Is there not an easier way? I'd love to have someone point out how dense I'm being about this and how I'm missing the obvious.
Thanks, Bill
Bill Kelly Auburn University OIT 334-844-9917
Fred Johanson ITSM Administrator University of Chicago 773-702-8464
