OK. The "equivalent" way to do the TS3500, treating as 2 separate libraries:
Using the TS3500 web interface, create 2 "logical" libraries/partitions in the
TS3500. Name them Manny and Moe (or whatever you want - TSM will not know or
care what the partition names are).
One "logical library" or "partition" would correspond to each of your current
category codes.
I will call them "libraries" from here on.
Assign 9 drives to one and 8 to the other.
Create at least one, preferably 2 control paths on any drive in each library
(more about control paths later).
Rescan device addresses from the OS, and the control path(s) will be presented
to the OS as a media changer device(s).
Define one library (Manny) on your TSM1 server, define the library path using
the media changer address, define the drives, define the paths using the drive
device addresses. .
TSM only knows the library by the Name you give it when you DEFINE LIBRARY, and
the device name when you define the library path. Doesn't know that it's
living in a partition in a bigger library, or what the library partition name
is from the TS3500.
Define Moe to your TSM2 server, etc.
I don't know how you were managing cartridges in your 3494; I always made sure
I had different ranges of volsers for each TSM.
Assuming you did that, in the TS3500 web interface, you create a "cartridge
assignment policy" for each logical library.
If your barcodes are TSM1xx for TSM server 1 and TSM2xx for TSM server 2, you
create a "cartridge assignment policy" in the Manny library that says all
barcodes TSM1xx go to the Manny partition. In the Moe partition, you create a
"cartridge assignment policy" that assigns all TSM2xx barcodes to Moe.
The "cartridge assignment policy" just affects what happens when you put tapes
in the I/O door. When you put tapes in through the door, the "cartridge
assignment policy" causes tapes in the door to be assigned to the "virtual I/O
door" of the appropriate library, so when you do a checkin from TSM1, it gets
only his barcodes. If you don't create a cartridge assignment policy, I
believe what still happens with ALMS is that when you put tapes in the door,
you get a prompt on the library display asking which library to assign the
cartridges to.
Now all you'll need to do is change the syntax of your CHECKIN command
appropriately, and from there on you can pretend everything works exactly like
it did with the 3494.
Note:
>From a TSM point of view, this is NOT "library sharing", this is 2 separate
>libraries (which could be physical or logical).
Differences: if you are "library sharing" with TSM, you have 1 partition, 1 set
of barcodes, 1 shared scratch pool, one of the TSM servers is the "library
manager/owner", and each TSM server can use all the drives.
Control paths:
You can go in the library web interface and define a control path on EVERY
drive in the logical library.
If you do, then you will have 8 or 9 media changer devices presented to the OS,
and you can use any one of them you want to define the library path.
But, having multiple control paths defined doesn't do you much practical good
unless you also have I/O path failover working in the O/S.
(I've seen it set up for AIX, never had a Windows customer do it.)
If you don't have I/O path failover working in the O/S, and the drive fails
that you are using for the library path, you're down anyway, whether you have
more control paths defined or not. If that happens, you go into TSM and update
the library path to use one of the other media changer device names, and you
can work that way until the failed drive is replaced. But that is still a
manual process/outage. So you can define a 2nd control path at that time, or
have an extra one defined ahead. No point in defining all of them, really.
The main thing you need to remember, which is different from the 3494, is that
if you have IBM come in and do firmware updates, and it takes the control path
drive out of service, you are going down until you redefine the library path
from TSM.
Wanda
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray
Sent: Tuesday, April 23, 2013 12:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500
2-libraries with fixed drives. One library has 9 drives the other one has 8.
-------------
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never
use email to request that you reply with your password, social security number
or confidential personal information. For more details visit
http://infosecurity.vcu.edu/phishing.html
When you say in your 3494 that "each owns n-3592 drives":
Do your current TSM servers share the drives, or do you use it as if it is
2 separate physical libraries?
Wanda
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray
Sent: Tuesday, April 23, 2013 10:28 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Equating current 3494 configuration to TS3500
As you are aware from previous posts, we are replacing our 3494 with a
TS3500/3584.
I am trying wrap my mind around the proper way to configure the TS3500 so it
functions the same way our 3494 does. If changing our current configuration
makes things easier for the transition, now would be the time to do it since
the install is tentatively scheduled for May. This is our current config:
We have 2-TSM servers acting at Library Managers/Owner, thus each LM has its
own "3494 category codes", each owns n-3592 drives, etc. This was done for
redundancy, fail-over, etc. We have tape drives spinning most of the time so
having all library functionality and drives attached to only 1-TSM server is
not a good idea.
>From the server perspective, there is one control path to the library via the
>IP address/connection. In the 3494, each Library Manager is defined, via the
>servers IP address.
Do I define 2-virtual libraries, 1-per library manager server? Does this mean
the drives as well as storage cells are defined/associated to each "virtual
library"?
>From reading through the various TS3500 books, they cite multiple ways to
>configure "Library Sharing", including virtual stuff since we are getting the
>ALMS feature.
Since I have never dealt with the issue of a tape drive "path" being used for
library control path/function, I guess I need to define more than one of these
paths, in case the drive has a problem?
Thoughts? Suggestions?
--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never
use email to request that you reply with your password, social security number
or confidential personal information. For more details visit
http://infosecurity.vcu.edu/phishing.html
|
