Re: TSM library manager instance
>> On Mon, 16 Mar 2009 15:58:18 -0400, Sean English >> said: > So from what I gather below, you have 1 LM with 20 library client > TSM instances connected to it? How many libraries do you have? Just the one. > Do you have a bunch of storage agents? Nope. > Reason I ask is we have a single LM with 15 TSM instances and we > have some issues surrounding that. It could be the number of storage > agents we have or maybe something else. But I would be curious in > how you are setup if you don't mind me asking. Not at all. Sorry for the delayed response: I've been out sick. We're pretty basic in architecture; though I'm about to switch a little. I've got one p630 with a RIO drawer (IBM AIX hardware) with one library manager instance and a passel of (as I call them) "customer-facing" instances. The customer-facing instances serve audiences ranging in size from a single application (IBM content manager) to a single service machine (central mail back-end with ~50M files) to a single service, to a single organizational unit, to "some folks". :) I started with one big instance, and calved new ones off as the administrative distinctions became apparent and important. The most significant calving events tend to be flavored: "Don't let -their- failure affect -me-". - Allen S. Rout
Re: TSM library manager instance
Allen, So from what I gather below, you have 1 LM with 20 library client TSM instances connected to it? How many libraries do you have? Do you have a bunch of storage agents? Reason I ask is we have a single LM with 15 TSM instances and we have some issues surrounding that. It could be the number of storage agents we have or maybe something else. But I would be curious in how you are setup if you don't mind me asking. Sean English "Allen S. Rout" Sent by: "ADSM: Dist Stor Manager" 03/16/2009 03:31 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM library manager instance >> On Mon, 16 Mar 2009 10:59:09 -0400, Mark Devine said: > (AIX 5.3 / TSM 5.4.3) > Any snags with adding a library manager TSM server instance alongside an > active TSM server on the same host? They will share HBAs, NICs, etc. > The current TSM server is clustered (HACMP), so I'm proposing moving these > in tandem during a failover. Haven't HACMPed them, but I've been running the LM on the same box with 20 instances for a long time. Runs very easily. - Allen S. Rout
Re: TSM library manager instance
>> On Mon, 16 Mar 2009 10:59:09 -0400, Mark Devine said: > (AIX 5.3 / TSM 5.4.3) > Any snags with adding a library manager TSM server instance alongside an > active TSM server on the same host? They will share HBAs, NICs, etc. > The current TSM server is clustered (HACMP), so I'm proposing moving these > in tandem during a failover. Haven't HACMPed them, but I've been running the LM on the same box with 20 instances for a long time. Runs very easily. - Allen S. Rout
Re: TSM library manager instance
Hi, Just give them their own ports and you should be fine. Regards/Met vriendelijke groet, Karel _ Karel Bos Technical Expert PU EIS SMS MSS-WEST Atos Origin Nederland B.V. Naritaweg 52 1043 BZ Amsterdam Office: +31 (0)88 265 95 43 Fax:+31 (0)20 Mobile:+31 (0)6 51 29 88 01 Mail: karel@atosorigin.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mark Devine Sent: maandag 16 maart 2009 15:59 To: ADSM-L@VM.MARIST.EDU Subject: TSM library manager instance Hey folks, (AIX 5.3 / TSM 5.4.3) Any snags with adding a library manager TSM server instance alongside an active TSM server on the same host? They will share HBAs, NICs, etc. The current TSM server is clustered (HACMP), so I'm proposing moving these in tandem during a failover. -- Mark ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2
TSM library manager instance
Hey folks, (AIX 5.3 / TSM 5.4.3) Any snags with adding a library manager TSM server instance alongside an active TSM server on the same host? They will share HBAs, NICs, etc. The current TSM server is clustered (HACMP), so I'm proposing moving these in tandem during a failover. -- Mark
Re: TSM Library Manager
The renaming-of-rmts makes me shiver, for what are atavistic reasons, I guess. I keep track of the same mappings: "This serial number has this physical location, and is this drive name on the lib manager". But I keep it in a little csv file, DRIVE0,07892730,460,new DRIVE1,07892835,470,new DRIVE2,07892870,480,new DRIVE3,07892900,490,new DRIVE4,07892702,100,new DRIVE5,07892704,101,new DRIVE6,07892705,102,new DRIVE7,07892710,103,new rather than in the ODM. Maybe it's just "dinking with the ODM" that frightens me. Then I've got a script which takes that csv file, looks at the tapes that are out there, and does e.g. update path CTRL DRIVE6 srct=server destt=drive libr=3592lib device=/dev/rmt4 update path CTRL DRIVE4 srct=server destt=drive libr=3592lib device=/dev/rmt0 update path CTRL DRIVE0 srct=server destt=drive libr=3592lib device=/dev/rmt6 update path CTRL DRIVE7 srct=server destt=drive libr=3592lib device=/dev/rmt13 update path CTRL DRIVE1 srct=server destt=drive libr=3592lib device=/dev/rmt2 update path CTRL DRIVE2 srct=server destt=drive libr=3592lib device=/dev/rmt3 update path CTRL DRIVE3 srct=server destt=drive libr=3592lib device=/dev/rmt9 update path CTRL DRIVE5 srct=server destt=drive libr=3592lib device=/dev/rmt8 with it. I can run the same collection of scripts on a new machine, and get the right device paths for instances on that box. This is another case where the DB2 behavior will be very pleasant. We can finally (virtually) tack on the extra columns we need, so we can demonstrate their utility. - Allen S. ROut
Re: TSM Library Manager
Paul,
Thanks for sharing your script. Everybody has their own naming
convention for tape drives. I like a convention where the TSM name
makes it possible to tell where the drive is in the physical library.
That makes it a lot easier when discussing the tape drive problem with
IBM, since the CE's seem to think in terms of physical locations.
If it is OK to post scripts directly, I will post mine:
root# cat TSM-rename-rmt-devices.ksh
#!/bin/ksh
# TSM-rename-rmt-devices.ksh
# A script to take FC rmt devices and rename them according to names
found
# in a table in /usr/local/bin/TSM-rename-rmt-devices.data
#
# History
# 02/06/2007 JDSchneider Original Version
#
#
print "This script will examine the existing FC tape rmt devices, and
rename"
print "them according to the table found in the config file:"
print " /usr/local/bin/TSM-rename-rmt-devices.data."
print "If there are no devices that need to be renamed, then no output
will"
print "be produced. Use \"lsdev -Cc tape\" to verify the status of the
drives."
print
print "Enter Y to proceed, or anything else to exit."
print
read ans
if [[ "$ans" != "Y" && "$ans" != "y" ]]
then
print "Exitting without doing anything..."
exit 0
fi
DEV_file=/tmp/TSM_lsdev.txt
SN_file=/tmp/TSM_SNfile.txt
DATA_file=/usr/local/bin/TSM-rename-rmt-devices.data
print "Gathering device data, please wait..."
lsdev -Cc tape | grep 3590 > $DEV_file 2>&1
lsdev -Cc tape | grep 3592 >> $DEV_file 2>&1
lsdev -Cc tape | grep 3580 >> $DEV_file 2>&1
rm $SN_file > /dev/null 2>&1
cat $DEV_file | while read rmt_device avail path junk
do
if [[ "$rmt_device" != "" ]]
then
serial_string=`lscfg -vl $rmt_device | grep 'Serial Number' |
cut -c37-`
path=`echo $path | cut -c1-5`
print $rmt_device $path $serial_string >> $SN_file
fi
done
cat $DATA_file | while read rmt_device tsm_drive path sn alt_path junk
do
if [[ "$sn" != "" && "$sn" != "Serial" ]]
then
path=`echo $path | cut -c1-5`
rmt_org=`grep $sn $SN_file | grep $path | head -1 | cut
-f1 -d" "`
if [[ "$rmt_org" != "" ]]
then
if [[ $rmt_org != $rmt_device ]]
then
print "Device $rmt_org being changed to
${rmt_device}."
echo chdev -l $rmt_org -a new_name=$rmt_device
chdev -l $rmt_org -a new_name=$rmt_device
if [[ $alt_path = "ALT" ]]
then
echo chdev -l $rmt_device -a alt_pathing=yes
chdev -l $rmt_device -a alt_pathing=yes
fi
fi
fi
fi
done
exit
stlo-tsm01_root#
Here is a sample of the data file it runs against. Note that the script
permits drives to have more than one path to the server (the ALT
parameter), and turn on IBM's alt_pathing support if so.
root# cat TSM-rename-rmt-devices.data
rmt-nameTSM-drivePath Serial Number Alt Path
rmt_f1_d01a drive_f1_d01 09-08 07808221 ALT
rmt_f1_d02a drive_f1_d02 09-08 07808146 ALT
rmt_f1_d03a drive_f1_d03 09-08 07807587 ALT
rmt_f1_d04a drive_f1_d04 09-08 07809316 ALT
rmt_f1_d05a drive_f1_d05 09-08 07802698 ALT
rmt_f1_d06a drive_f1_d06 09-08 07807535 ALT
rmt_f1_d07a drive_f1_d07 09-08 07807590 ALT
rmt_f1_d01b drive_f1_d01 0C-08 07808221 ALT
rmt_f1_d02b drive_f1_d02 0C-08 07808146 ALT
rmt_f1_d03b drive_f1_d03 0C-08 07807587 ALT
rmt_f1_d04b drive_f1_d04 0C-08 07809316 ALT
rmt_f1_d05b drive_f1_d05 0C-08 07802698 ALT
rmt_f1_d06b drive_f1_d06 0C-08 07807535 ALT
rmt_f1_d07b drive_f1_d07 0C-08 07807590 ALT
rmt-nameTSM-drivePath Serial Number Alt Path
lto4_f1_d01 lto4_f1_d01 09-09 0007850942
lto4_f1_d02 lto4_f1_d02 09-09 0007850931
lto4_f1_d03 lto4_f1_d03 09-09 0007850943
lto4_f1_d04 lto4_f1_d04 0C-09 0007850935
lto4_f1_d05 lto4_f1_d05 0C-09 0007851058
lto4_f1_d06 lto4_f1_d06 0C-09 0007850928
lto4_f1_d07 lto4_f1_d07 0D-09 0007850906
lto4_f1_d08 lto4_f1_d08 0D-09 0007850924
lto4_f1_d09 lto4_f1_d09 0D-09 0007854535
lto4_f1_d10 lto4_f1_d10 0G-09 0007854530
lto4_f1_d11 lto4_f1_d11 0G-09 0007854519
lto4_f1_d12 lto4_f1_d12 0G-09 0007854527
root#
Best Regards,
John D. Schneider
Phone: 314-364-3150
Cell: 314-750-8721
Email: john.schnei...@mercy.net
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Paul Zarnowski
Sent: Tuesday, March 10, 2009 2:41 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Library Manager
At 03:17 PM 3/10/2009, Schneider, John wrote:
>Gr
Re: TSM Library Manager
And always consider what the truly smart guys have to say first when reading the list! Thanks Paul. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Paul Zarnowski Sent: Tuesday, March 10, 2009 1:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library Manager At 03:17 PM 3/10/2009, Schneider, John wrote: >Greetings, > I have a solution to the problem of library sharing and >different rmt names. We have a similar, but different solution. We have a script we use to rename AIX tape devices to a predictable name, based on the last 4 characters of the WWN. After running it on each AIX system, the device names will be the same on each system. After running "tsmchrmt rmt0", the device will have a name similar to: rmt.f0c6.0.0 where "f0c6" are the last 4 chars of the device's WWN. I don't recall where we got the seed for this script, but here is our version, which we call "tsmchrmt": #!/bin/sh if [ $# != 1 ] then echo "must specify 1 rmt device name as an argument." exit 4 fi d=$1 WWN=`/usr/sbin/lsattr -El $d -a ww_name|cut -f2 -d" "|cut -c15-` LUN=`/usr/sbin/lsattr -El $d -a lun_id|cut -f2 -d" "|cut -c3` root=`echo $d|cut -c1-3` new_name=$root.$WWN.$LUN.0 let "j=0" while [[ -e /dev/$new_name ]] do let "j=j+1" new_name=$root.$WWN.$LUN.$j done /usr/sbin/chdev -l $d -a new_name=$new_name ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: TSM Library Manager
At 03:17 PM 3/10/2009, Schneider, John wrote: Greetings, I have a solution to the problem of library sharing and different rmt names. We have a similar, but different solution. We have a script we use to rename AIX tape devices to a predictable name, based on the last 4 characters of the WWN. After running it on each AIX system, the device names will be the same on each system. After running "tsmchrmt rmt0", the device will have a name similar to: rmt.f0c6.0.0 where "f0c6" are the last 4 chars of the device's WWN. I don't recall where we got the seed for this script, but here is our version, which we call "tsmchrmt": #!/bin/sh if [ $# != 1 ] then echo "must specify 1 rmt device name as an argument." exit 4 fi d=$1 WWN=`/usr/sbin/lsattr -El $d -a ww_name|cut -f2 -d" "|cut -c15-` LUN=`/usr/sbin/lsattr -El $d -a lun_id|cut -f2 -d" "|cut -c3` root=`echo $d|cut -c1-3` new_name=$root.$WWN.$LUN.0 let "j=0" while [[ -e /dev/$new_name ]] do let "j=j+1" new_name=$root.$WWN.$LUN.$j done /usr/sbin/chdev -l $d -a new_name=$new_name ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: TSM Library Manager
Greetings, I have a solution to the problem of library sharing and different rmt names. We have a number of AIX TSM servers that all share the same tape libraries, and at first it was a big aggrevation because frame1 drive 3 would be rmt3 on one server, and rmt5 on another server, and so on. Anytime we needed to delete and rediscover a drive, it might come back as a different logical name and we would have to update the path. Eventually I got tired of it, and I wrote a script that runs against a small table in a flat file, and renames the AIX device name so they are the same on each system. (our naming convention for the drives, ie. f1_d05, means frame 1, drive 5. You can use any convention you want of course.) The table contains lines like: rmt-nameTSM-drivePath Serial Number lto4_f1_d01 lto4_f1_d01 09-09 0007850942 lto4_f1_d02 lto4_f1_d02 09-09 0007850931 lto4_f1_d03 lto4_f1_d03 09-09 0007850943 lto4_f1_d04 lto4_f1_d04 0C-09 0007850935 lto4_f1_d05 lto4_f1_d05 0C-09 0007851058 lto4_f1_d06 lto4_f1_d06 0C-09 0007850928 That show the logical tape name the tape drive should have, the TSM name, and the path and serial number. The script looks at each tape drive on a system, and if its serial number appears in this table, it checks to see if the logical name matches what is in the table. If it doesn't, it uses the 'chdev' command to rename the device. So, when you first do the discovery the drives might be: root# lsdev -Cc tape rmt0 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 0D-09-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP) rmt6 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP) rmt7 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP) And after you run the script the devices will be: root# lsdev -Cc tape lto4_f1_d01 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP) lto4_f1_d02 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP) lto4_f1_d03 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP) lto4_f1_d04 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP) lto4_f1_d05 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP) lto4_f1_d06 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP) lto4_f1_d07 Available 0D-09-02 IBM 3580 Ultrium Tape Drive (FCP) That way your path statements in TSM map the TSM device called lto4_f1_d01 to AIX path /dev/lto4_f1_d01, and that remains true on every AIX host. This makes them a lot easier to maintain. Anytime we have to delete a tape drive, we just rediscover the drive with cfmgmr, and then rerun our script, and they get renamed back to the logical name they should be. If anyone would like the script I would be happy to share it, but I didn't know if it was acceptible practice to just post it to the whole list. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: john.schnei...@mercy.net -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 1:28 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library Manager Thanks to all because of your emails you got me looking at how I created the paths and this is where my problem was. I had the name reversed. Once I changed this things started working. Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Abid Ilias Sent: Tuesday, March 10, 2009 1:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager Also turn the SAN Discovery option ON, we have figured out that the only way SAN Discovery would work was to run TSM as Root in UNIX. If you have SAN Discovery option ON, it is supposed to fix any discrepancy. I would make a spread sheet of all devices for library manager/client and update the path definition on Library manager to reflect that. Here is any example of one, in this case the rmt number match for Library Manager and clinet. When you define a drive leave the default for "serial" option and for the path definition use "autodetect=yes" which is not default. Drive Name Frame Row Element No Manager Client DR5218 1 1 257 rmt7rmt7 DR5167 1 2 258 6 6 DR5467 1 3 259 3 3 DR5457 1 4 260 0 0 DR5460 1 5 261 2 2 DR5475 1 6 262 5 5 DR5136 1 7 263 11 11 DR5304 1 8 264 12 12 DR5316 1 9 265 13
Re: TSM Library Manager
Thanks to all because of your emails you got me looking at how I created the paths and this is where my problem was. I had the name reversed. Once I changed this things started working. Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Abid Ilias Sent: Tuesday, March 10, 2009 1:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager Also turn the SAN Discovery option ON, we have figured out that the only way SAN Discovery would work was to run TSM as Root in UNIX. If you have SAN Discovery option ON, it is supposed to fix any discrepancy. I would make a spread sheet of all devices for library manager/client and update the path definition on Library manager to reflect that. Here is any example of one, in this case the rmt number match for Library Manager and clinet. When you define a drive leave the default for "serial" option and for the path definition use "autodetect=yes" which is not default. Drive Name Frame Row Element No Manager Client DR5218 1 1 257 rmt7rmt7 DR5167 1 2 258 6 6 DR5467 1 3 259 3 3 DR5457 1 4 260 0 0 DR5460 1 5 261 2 2 DR5475 1 6 262 5 5 DR5136 1 7 263 11 11 DR5304 1 8 264 12 12 DR5316 1 9 265 13 13 DR5335 1 10 266 14 14 DR5337 1 11 267 15 15 DR5338 1 12 268 16 16 DR0074 2 1 269 8 8 DR0053 2 2 270 9 9 DR0120 2 3 271 17 17 DR9931 2 4 272 18 18 DR0049 2 5 273 10 10 DR9995 2 6 274 19 19 DR5876 2 7 275 1 1 DR5956 2 8 276 4 4 DR5342 2 9 277 20 20 DR5846 2 10 278 21 21 Thanks Abid Ilias TSM Administrator Networking Services and Information Technology The University of Chicago -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: Tuesday, March 10, 2009 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library Manager Are you comparing the element number/serial number on each rmt device on the client with the path definition for the client on the library manager. rmt2 on the manager is not necessarily the same as rmt2 on the client and the path statements on the library manager have to resolve any differences. David >>> "Morris.Marshael" 3/10/2009 1:11 PM >>> I checked the drives to see what element numbers they were pointing to and checked the library to see what element they were showing for the drives, all are in sync. Thanks, Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Tuesday, March 10, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes
Re: TSM Library Manager
Also turn the SAN Discovery option ON, we have figured out that the only way SAN Discovery would work was to run TSM as Root in UNIX. If you have SAN Discovery option ON, it is supposed to fix any discrepancy. I would make a spread sheet of all devices for library manager/client and update the path definition on Library manager to reflect that. Here is any example of one, in this case the rmt number match for Library Manager and clinet. When you define a drive leave the default for "serial" option and for the path definition use "autodetect=yes" which is not default. Drive Name Frame Row Element No Manager Client DR5218 1 1 257 rmt7rmt7 DR5167 1 2 258 6 6 DR5467 1 3 259 3 3 DR5457 1 4 260 0 0 DR5460 1 5 261 2 2 DR5475 1 6 262 5 5 DR5136 1 7 263 11 11 DR5304 1 8 264 12 12 DR5316 1 9 265 13 13 DR5335 1 10 266 14 14 DR5337 1 11 267 15 15 DR5338 1 12 268 16 16 DR0074 2 1 269 8 8 DR0053 2 2 270 9 9 DR0120 2 3 271 17 17 DR9931 2 4 272 18 18 DR0049 2 5 273 10 10 DR9995 2 6 274 19 19 DR5876 2 7 275 1 1 DR5956 2 8 276 4 4 DR5342 2 9 277 20 20 DR5846 2 10 278 21 21 Thanks Abid Ilias TSM Administrator Networking Services and Information Technology The University of Chicago -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: Tuesday, March 10, 2009 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library Manager Are you comparing the element number/serial number on each rmt device on the client with the path definition for the client on the library manager. rmt2 on the manager is not necessarily the same as rmt2 on the client and the path statements on the library manager have to resolve any differences. David >>> "Morris.Marshael" 3/10/2009 1:11 PM >>> I checked the drives to see what element numbers they were pointing to and checked the library to see what element they were showing for the drives, all are in sync. Thanks, Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Tuesday, March 10, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
Re: TSM Library Manager
Are you comparing the element number/serial number on each rmt device on the client with the path definition for the client on the library manager. rmt2 on the manager is not necessarily the same as rmt2 on the client and the path statements on the library manager have to resolve any differences. David >>> "Morris.Marshael" 3/10/2009 1:11 PM >>> I checked the drives to see what element numbers they were pointing to and checked the library to see what element they were showing for the drives, all are in sync. Thanks, Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Tuesday, March 10, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-02 IBM 3584 Library Medium Changer (FCP) client tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-01 IBM 3584 Library Medium Changer (FCP) I have checked the serial numbers of the drives on the server to the client and I believe that they are correct. Can someone help me in figuring out what I have missed or what might be the problem? Thanks, Marshael mccg.org email firewall made the following annotation CONFIDENTIALITY NOTICE: The information transmitted in this e-mail message, including any attachments, is for the sole use of the intended recipient(s) or entity to which it is addressed and may contain confidential, privileged and/or proprietary information. Any unauthorized review, retransmission, use, disclosure, dissemination or other use of,or taking any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail, or by calling (478) 633-7272, and destroy the original message, attachments and all copies thereof on all computers and in any other form. Thank you. The Medical Center Of Central Georgia. http://www.mccg.org/ 03/10/09, 12:24:19
Re: TSM Library Manager
Can you see that the library is indeed hanging a tape in some drive? And if so, is it indeed the correct drive? Visual inspection of what you think is happening is what I'm suggesting. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 11:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library Manager I checked the drives to see what element numbers they were pointing to and checked the library to see what element they were showing for the drives, all are in sync. Thanks, Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Tuesday, March 10, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-02 IBM 3584 Library Medium Changer (FCP) client tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-01 IBM 3584 Library Medium Changer (FCP) I have checked the serial numbers of the drives on the server to the client and I believe that they are correct. Can someone help me in figuring out what I have missed or what might be the problem? Thanks, Marshael mccg.org email firewall made the following annotation CONFIDENTIALITY NOTICE: The information transmitted in this e-mail message, including any attachments, is for the sole use of the intended recipient(s) or entity to which it is addressed and may contain confidential, privileged and/or proprietary information. Any unauthorized review, retransmission, use, disclosure, dissemination or other use of,or taking any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail, or by calling (478) 633-7272, and destroy the original message, attachments and all copies thereof on all computers and in any other form. Thank you. The Medical Center Of Central Georgia. http://www.mccg.org/ 03/10/09, 12:24:19
Re: TSM Library Manager
I checked the drives to see what element numbers they were pointing to and checked the library to see what element they were showing for the drives, all are in sync. Thanks, Marshael -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Tuesday, March 10, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Library Manager I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-02 IBM 3584 Library Medium Changer (FCP) client tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-01 IBM 3584 Library Medium Changer (FCP) I have checked the serial numbers of the drives on the server to the client and I believe that they are correct. Can someone help me in figuring out what I have missed or what might be the problem? Thanks, Marshael mccg.org email firewall made the following annotation CONFIDENTIALITY NOTICE: The information transmitted in this e-mail message, including any attachments, is for the sole use of the intended recipient(s) or entity to which it is addressed and may contain confidential, privileged and/or proprietary information. Any unauthorized review, retransmission, use, disclosure, dissemination or other use of,or taking any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail, or by calling (478) 633-7272, and destroy the original message, attachments and all copies thereof on all computers and in any other form. Thank you. The Medical Center Of Central Georgia. http://www.mccg.org/ 03/10/09, 12:24:19
Re: TSM Library Manager
I've seen something similar in the non sharing environment if the element number to drive relationship is whacked. For instance, you suggest that the drive at /rmt0 is element 256 when in reality it's 257. The library is instructed to mount a tape in element 256 and then TSM looks for tape in /rmt0. Verify that the paths and element numbers actually line-up correctly. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Morris.Marshael Sent: Tuesday, March 10, 2009 10:24 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-02 IBM 3584 Library Medium Changer (FCP) client tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-01 IBM 3584 Library Medium Changer (FCP) I have checked the serial numbers of the drives on the server to the client and I believe that they are correct. Can someone help me in figuring out what I have missed or what might be the problem? Thanks, Marshael mccg.org email firewall made the following annotation CONFIDENTIALITY NOTICE: The information transmitted in this e-mail message, including any attachments, is for the sole use of the intended recipient(s) or entity to which it is addressed and may contain confidential, privileged and/or proprietary information. Any unauthorized review, retransmission, use, disclosure, dissemination or other use of,or taking any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail, or by calling (478) 633-7272, and destroy the original message, attachments and all copies thereof on all computers and in any other form. Thank you. The Medical Center Of Central Georgia. http://www.mccg.org/ 03/10/09, 12:24:19
TSM Library Manager
I have setup a library manager in TSM. This server is TSM 5.5.2 I am setting up a library client and it also has TSM 5.5.2. The TSM library manager is using the drives with no problem. I have setup the paths for the library client and I'm having problems with the client. The server, when requested, will mount a tape from the client and change ownership to the client name. Within the client activity log I get: ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000) (Tcp/Ip) for library sharing. ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000). ANR8779E Unable to open drive rmt2, error number=2. ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000). ANR1404W Scratch volume mount request denied - mount failed. Librarymanager tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-02 IBM 3584 Library Medium Changer (FCP) client tapes from AIX: lsdev -Cc tape rmt0 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt2 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt3 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt4 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) rmt5 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP) smc0 Available 07-08-01 IBM 3584 Library Medium Changer (FCP) I have checked the serial numbers of the drives on the server to the client and I believe that they are correct. Can someone help me in figuring out what I have missed or what might be the problem? Thanks, Marshael mccg.org email firewall made the following annotation CONFIDENTIALITY NOTICE: The information transmitted in this e-mail message, including any attachments, is for the sole use of the intended recipient(s) or entity to which it is addressed and may contain confidential, privileged and/or proprietary information. Any unauthorized review, retransmission, use, disclosure, dissemination or other use of,or taking any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail, or by calling (478) 633-7272, and destroy the original message, attachments and all copies thereof on all computers and in any other form. Thank you. The Medical Center Of Central Georgia. http://www.mccg.org/ 03/10/09, 12:24:19
Re: TSM Library manager v Gresham
On 25 nov 2008, at 02:46, Mark Stapleton wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Alex Paschal I don't know what Mark meant about inability to use the library due to resyncing TSM to Gresham. I don't recall ever syncing TSM with EDT, it wasn't necessary since ACSLS was managing the library, but I suppose there could be some other functionality I wasn't aware of. When I worked for Customer X (two STK 9310s, EDT, and 10 instances of TSM, there would be times when one or more TSM instances couldn't use a given tape drive because it couldn't sync with the EDT definition. In order to get all the instances sync'd backed up, we had to shut down all tape operations, and run a Gresham utility on each instance to get the sync back and running. A pain in the posterior... I think you're saying that after upgrading one TSM server (system) the TSM device driver had been upgraded and the drive definitions got mixed up. In previous releases EDT lacked the right tools to quickly find out which drive is which, you are right. Currently I find myself building a customer specific script that builds a elm.conf from a template and the output of `elm_match_device -d tsm -Z`, which works great. Remember that in a TSM library manager situation, you'll find yourself doing the exact same thing, but without the handy tools. Come to think of it, EDT does provide some features that are a must- have to Ian's customer that TSM just can't provide. It's a pity that they are even spending time on reevaluating the choice for EDT. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -- Remco Post [EMAIL PROTECTED] +31 6 24821 622
Re: TSM Library manager v Gresham
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Alex Paschal > I don't know what Mark meant about inability to use the library due to > resyncing TSM to Gresham. I don't recall ever syncing TSM with EDT, it > wasn't necessary since ACSLS was managing the library, but I suppose > there could be some other functionality I wasn't aware of. When I worked for Customer X (two STK 9310s, EDT, and 10 instances of TSM, there would be times when one or more TSM instances couldn't use a given tape drive because it couldn't sync with the EDT definition. In order to get all the instances sync'd backed up, we had to shut down all tape operations, and run a Gresham utility on each instance to get the sync back and running. A pain in the posterior... -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com
Re: TSM Library manager v Gresham
Last time I tried TSM -> ACSLS with a 5000 slot ACSLS-managed library, TSM was very slow doing library "stuff". Also, Q DRMEDIA and "Q LIBVOL" was very slow as well, I'm not sure why. We didn't have time to mess around with it because we had to switch back to EDT to get back to reasonable performance for production. We didn't notice this in the test environment because (I believe) we were using a small library. This was about 4 years ago, so I don't know if this is still the case. Things I liked about using EDT: - Separate scratch pools - useful for different gen media or overly uptight departments that refuse to allow "their" tapes to be reused by other departments - Not having to do TSM-based library sharing - The ability to use mixed gen media on the same drive - Not having to deal with "checkin/checkout libvol" (I had forgotten how cumbersome this process was) - Not having to stop all tape use to audit the library - Scripting ejects/imports/scratching/auditing for our operations personnel was easy with EDT I don't know what Mark meant about inability to use the library due to resyncing TSM to Gresham. I don't recall ever syncing TSM with EDT, it wasn't necessary since ACSLS was managing the library, but I suppose there could be some other functionality I wasn't aware of. I found using TSM/EDT/ACSLS to be a very nice combination. The only cons I can think of is the /slight/ learning curve and having to pay for and support another piece of software. I found Gresham support responsive and knowledgeable. To tell the truth, I wish IBM would use an external library manager as well. It's nice to have the basic built-in library management functionality in TSM, but really, breaking it out of TSM could bypass many of the shortcomings I find in TSM's library management. Alex Paschal Storage Solutions Engineer MSI Systems Integrators Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith Sent: Thursday, November 20, 2008 4:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library manager v Gresham Hi What experiences do people have of library/drive control for SL8500? I am trying to work out the pros and cons of either using TSM Library manager with ACSLS or the Gresham agents. Does anyone have any thoughts or experiences regarding performance, stability, ease of use etc? Thanks Ian Smith Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk. This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: TSM Library manager v Gresham
Accepted that the Single Point of Failure of using a single TSM Library manager instance is a risk. It seems that this is the major benefit of Gresham- its ability to distribute shared library control. This then needs to be considered against cost. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Copin, Christophe (Ext) Sent: 20 November 2008 13:29 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham Hi I disagree. Except the price tag ... Unfortunatelly, TSM built-in library manager is not smart enough for large ACSLS libraries. How do you handle multiple ACSLS scratch pools without external library manager (Gresham or whatever) ? What path optimization can be done without external library manager ? (to avoid using the pass-through) Let's say I would like TSM to choose the closest free drive (same LSM) to mount a tape ... ... TSM uses tape drives in sequential order. If your TSM Server hosts several instances, Gresham allows you not to depend on one *critical* TSM library manager instance. With an external manager, each instance is able to mount/dismount tapes as a stand alone server would do. In a nutshell, I would say the more larger is your library(ies), the worth gresham is. Actually i would say the drawback is only the price, and the fact you'll will have to get a license for each storage agent. (;_;) If you don't want to manage SL8500s and such large librairies, in that cases, forget about Gresham and use TSM builtin manager. Christophe. -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Mark Stapleton Envoyé : jeudi 20 novembre 2008 13:40 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] TSM Library manager v Gresham From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith > What experiences do people have of library/drive control for SL8500? > > I am trying to work out the pros and cons of either using TSM Library > manager with ACSLS or the Gresham agents. Does anyone have any thoughts > or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com Afin de préserver l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Please consider the environment before printing this mail. Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk.
Re: TSM Library manager v Gresham
We did same recently, we moved from LibStation/zOS to ACSLS/AIX, works well. -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Costa, Justino Envoyé : jeudi 20 novembre 2008 14:14 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] TSM Library manager v Gresham I'm currently using SL8500 like this: 1) zOS 1.1) HSC - shares 9840a,b and c drives for zOS hosts 1.2) LibStation - 1.2.1) TSM LIBM for LTO3 (no clients) - shares LTO3 for servers ans stagents 1,2...N 1.2.1) TSM LIBM for LTO4 (no clients) - shares LTO4 for servers ans stagents 1,2...N This setup works very weel with no issues at all. But, since we're decomissioning the zOS, next month I'll have 1) ACSLS 1.1) TSM LIBM for LTO3 (no clients) - shares LTO3 for servers ans stagents 1,2...N 1.2) TSM LIBM for LTO4 (no clients) - shares LTO4 for servers ans stagents 1,2...N Hope this works fine too. Could any of you share any warnings you may have regarding this setup ? Justino Miguel Costa Solution Specialist _ Logica - Releasing your potential Rua Particular EDP (à Rua Cidade de Goa), 11 2686-964 Sacavém - Portugal M: +351 936 830 259 E: [EMAIL PROTECTED] E: [EMAIL PROTECTED] W: http://www.logica.com/pt -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith Sent: quinta-feira, 20 de Novembro de 2008 12:54 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham Thanks Do you currently use TSM Library Manager with ACSLS? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: 20 November 2008 12:40 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith > What experiences do people have of library/drive control for SL8500? > > I am trying to work out the pros and cons of either using TSM Library > manager with ACSLS or the Gresham agents. Does anyone have any thoughts > or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. Afin de préserver l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Please consider the environment before printing this mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à lintention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et den avertir immédiatement lexpéditeur. Internet ne permettant pas de garantir lintégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message sil a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (the email) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whats
Re: TSM Library manager v Gresham
Hi I disagree. Except the price tag ... Unfortunatelly, TSM built-in library manager is not smart enough for large ACSLS libraries. How do you handle multiple ACSLS scratch pools without external library manager (Gresham or whatever) ? What path optimization can be done without external library manager ? (to avoid using the pass-through) Let's say I would like TSM to choose the closest free drive (same LSM) to mount a tape ... ... TSM uses tape drives in sequential order. If your TSM Server hosts several instances, Gresham allows you not to depend on one *critical* TSM library manager instance. With an external manager, each instance is able to mount/dismount tapes as a stand alone server would do. In a nutshell, I would say the more larger is your library(ies), the worth gresham is. Actually i would say the drawback is only the price, and the fact you'll will have to get a license for each storage agent. (;_;) If you don't want to manage SL8500s and such large librairies, in that cases, forget about Gresham and use TSM builtin manager. Christophe. -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Mark Stapleton Envoyé : jeudi 20 novembre 2008 13:40 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] TSM Library manager v Gresham From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith > What experiences do people have of library/drive control for SL8500? > > I am trying to work out the pros and cons of either using TSM Library > manager with ACSLS or the Gresham agents. Does anyone have any thoughts > or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com Afin de préserver l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Please consider the environment before printing this mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à lintention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et den avertir immédiatement lexpéditeur. Internet ne permettant pas de garantir lintégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message sil a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (the email) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system.
Re: TSM Library manager v Gresham
Libstation and acsls are interchangeable, moving from one to the other will not mage a difference. I'd still recommend using EDT, though I'm with Mark in the price tag On 20 nov 2008, at 14:13, Costa, Justino wrote: I'm currently using SL8500 like this: 1) zOS 1.1) HSC - shares 9840a,b and c drives for zOS hosts 1.2) LibStation - 1.2.1) TSM LIBM for LTO3 (no clients) - shares LTO3 for servers ans stagents 1,2...N 1.2.1) TSM LIBM for LTO4 (no clients) - shares LTO4 for servers ans stagents 1,2...N This setup works very weel with no issues at all. But, since we're decomissioning the zOS, next month I'll have 1) ACSLS 1.1) TSM LIBM for LTO3 (no clients) - shares LTO3 for servers ans stagents 1,2...N 1.2) TSM LIBM for LTO4 (no clients) - shares LTO4 for servers ans stagents 1,2...N Hope this works fine too. Could any of you share any warnings you may have regarding this setup ? Justino Miguel Costa Solution Specialist _ Logica - Releasing your potential Rua Particular EDP (à Rua Cidade de Goa), 11 2686-964 Sacavém - Portugal M: +351 936 830 259 E: [EMAIL PROTECTED] E: [EMAIL PROTECTED] W: http://www.logica.com/pt -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith Sent: quinta-feira, 20 de Novembro de 2008 12:54 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham Thanks Do you currently use TSM Library Manager with ACSLS? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: 20 November 2008 12:40 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith What experiences do people have of library/drive control for SL8500? I am trying to work out the pros and cons of either using TSM Library manager with ACSLS or the Gresham agents. Does anyone have any thoughts or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk . This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e- mail and any attachment and all copies and inform the sender. Thank you. -- Met vriendelijke groeten/Kind regards, Remco Post, PLCS +31624821622
Re: TSM Library manager v Gresham
On 20 nov 2008, at 13:40, Mark Stapleton wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith What experiences do people have of library/drive control for SL8500? I am trying to work out the pros and cons of either using TSM Library manager with ACSLS or the Gresham agents. Does anyone have any thoughts or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. there are a few things that gresham EDT offers that TSM doesn't. I don't get your comment on syncing, both EDT and TSM suffer from changed drive paths when you upgrade TSM. Both require a bit of administration, it's just in different places. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -- Met vriendelijke groeten/Kind regards, Remco Post, PLCS +31624821622
Re: TSM Library manager v Gresham
I'm currently using SL8500 like this: 1) zOS 1.1) HSC - shares 9840a,b and c drives for zOS hosts 1.2) LibStation - 1.2.1) TSM LIBM for LTO3 (no clients) - shares LTO3 for servers ans stagents 1,2...N 1.2.1) TSM LIBM for LTO4 (no clients) - shares LTO4 for servers ans stagents 1,2...N This setup works very weel with no issues at all. But, since we're decomissioning the zOS, next month I'll have 1) ACSLS 1.1) TSM LIBM for LTO3 (no clients) - shares LTO3 for servers ans stagents 1,2...N 1.2) TSM LIBM for LTO4 (no clients) - shares LTO4 for servers ans stagents 1,2...N Hope this works fine too. Could any of you share any warnings you may have regarding this setup ? Justino Miguel Costa Solution Specialist _ Logica - Releasing your potential Rua Particular EDP (à Rua Cidade de Goa), 11 2686-964 Sacavém - Portugal M: +351 936 830 259 E: [EMAIL PROTECTED] E: [EMAIL PROTECTED] W: http://www.logica.com/pt -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith Sent: quinta-feira, 20 de Novembro de 2008 12:54 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham Thanks Do you currently use TSM Library Manager with ACSLS? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: 20 November 2008 12:40 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith > What experiences do people have of library/drive control for SL8500? > > I am trying to work out the pros and cons of either using TSM Library > manager with ACSLS or the Gresham agents. Does anyone have any thoughts > or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Re: TSM Library manager v Gresham
I'm a consultant who works with multiple customers, and yes, some of them (those who use larger StorageTek libraries) have to use ACSLS. For details on how to do that, run help define library and take a look at the ACSLS syntax. It's not all that hard to get TSM working with an ACSLS server. -- Mark Stapleton ([EMAIL PROTECTED]) CDW System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Ian Smith > Sent: Thursday, November 20, 2008 7:54 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM Library manager v Gresham > > Thanks > > Do you currently use TSM Library Manager with ACSLS? > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of > Mark Stapleton > Sent: 20 November 2008 12:40 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM Library manager v Gresham > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Ian Smith > > What experiences do people have of library/drive control for SL8500? > > > > I am trying to work out the pros and cons of either using TSM Library > > manager with ACSLS or the Gresham agents. Does anyone have any > thoughts > > or experiences regarding performance, stability, ease of use etc? > > There isn't anything that TSM's built-in library management has that > Gresham offers. Indeed, getting multiple TSM instances resync'd with > Gresham can cause (temporary) inability to use the library during that > resync. Stability isn't usually an issue with either TSM library > management or Gresham. Gresham requires additional administration that > TSM's library management doesn't need. > > And TSM's library management doesn't have an outrageous price tag. > > (You'll still need to use ACSLS, of course.) > > -- > Mark Stapleton ([EMAIL PROTECTED]) > CDW Berbee > System engineer > 7145 Boone Avenue North, Suite 140 > Brooklyn Park MN 55428-1511 > 763-592-5963 > www.berbee.com > > Dell Corporation Limited is registered in England and Wales. Company > Registration Number: 2081369 > Registered address: Dell House, The Boulevard, Cain Road, Bracknell, > Berkshire, RG12 1LF, UK. > Company details for other Dell UK entities can be found on > www.dell.co.uk.
Re: TSM Library manager v Gresham
Thanks Do you currently use TSM Library Manager with ACSLS? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: 20 November 2008 12:40 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Library manager v Gresham From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith > What experiences do people have of library/drive control for SL8500? > > I am trying to work out the pros and cons of either using TSM Library > manager with ACSLS or the Gresham agents. Does anyone have any thoughts > or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk.
Re: TSM Library manager v Gresham
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Smith > What experiences do people have of library/drive control for SL8500? > > I am trying to work out the pros and cons of either using TSM Library > manager with ACSLS or the Gresham agents. Does anyone have any thoughts > or experiences regarding performance, stability, ease of use etc? There isn't anything that TSM's built-in library management has that Gresham offers. Indeed, getting multiple TSM instances resync'd with Gresham can cause (temporary) inability to use the library during that resync. Stability isn't usually an issue with either TSM library management or Gresham. Gresham requires additional administration that TSM's library management doesn't need. And TSM's library management doesn't have an outrageous price tag. (You'll still need to use ACSLS, of course.) -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com
TSM Library manager v Gresham
Hi What experiences do people have of library/drive control for SL8500? I am trying to work out the pros and cons of either using TSM Library manager with ACSLS or the Gresham agents. Does anyone have any thoughts or experiences regarding performance, stability, ease of use etc? Thanks Ian Smith Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for other Dell UK entities can be found on www.dell.co.uk.
Re: TSM Library Manager
On Nov 5, 2008, at 19:41 , Mark Stapleton wrote: The TSM Administrator's Guide. that and then there is this: http://www.urz.uni-heidelberg.de/UnixCluster/Hinweise/Hilfe/System/Adsm/redbooks/redp0024.pdf old but still correct. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Wednesday, November 05, 2008 10:20 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Library Manager What's the best documentation to look at to get a basic understanding on how to set up a Library Manager server? TSM servers are 5.4 and 5.5 running on AIX. David -- Met vriendelijke groeten, Remco Post [EMAIL PROTECTED] +31 6 248 21 622
Re: TSM Library Manager
The TSM Administrator's Guide. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of David E Ehresman > Sent: Wednesday, November 05, 2008 10:20 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] TSM Library Manager > > What's the best documentation to look at to get a basic understanding > on how to set up a Library Manager server? TSM servers are 5.4 and 5.5 > running on AIX. > > David
TSM Library Manager
What's the best documentation to look at to get a basic understanding on how to set up a Library Manager server? TSM servers are 5.4 and 5.5 running on AIX. David
Re: 3494 Partitioning or TSM Library Manager
The communications problem was corrected in level 4.2.2.6. Should have included that in the first message. The problem I described below will be encountered when you have enough drive usage between the sharing tsm's. Good luck. Philip A. James, Systems Software Specialist Software Services Unit Information Technology Services Division / Data Center California Public Employees' Retirement System Phone: (916) 326-3715 Fax: (916) 326-3884 Email: [EMAIL PROTECTED] -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 2:12 PM To: [EMAIL PROTECTED] Subject: Re: 3494 Partitioning or TSM Library Manager Have them take a look at PMR 02224,519 - we just upgraded from 4.2.1.15 to 4.2.30 because of an identified "internal defect". I don't have all the details in front of me, but at the 4.2.1.15 level there is apparently some communications issues. -Original Message- From: James, Phil [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 3:50 PM To: [EMAIL PROTECTED] Subject: Re: 3494 Partitioning or TSM Library Manager Importance: Low We have a similar problem with tape drive sharing. IBM summarized the problem very well below. This was the response listed in the PMR from IBM. Researched problem and found that the root cause of this problem is the same as that for pmr 04108,bre. .. The dismount command issues a dismount request the the drive, we make sure that the drive receives the command and we request a response. If we do not get an immediate response we retry the dismount 5X. .. If after the 5th retry we still cannot communicate with the drive we issue an IO error and mark the drive offline. .. In the event of library sharing and/or library fail-over a situation can occur where the drive is not available to the TSM server that issued the dismount command; in library fail-over the library is unavailable for a period of time that exceeds the amount of time it takes for the 5 retries (approximately 5 minutes), if the event of another server taking control over that drive (since we immediately release the drive after issuing the dismount request to the library) the TSM server that issued the request can no longer communicate with that drive and if this exceeds the retry period then we would mark the drive offline. .. While this is not preferred behavior it is not necessarily a defect. .. A DCR will have to be opened to request that in the case of library sharing and library fail-over the dismount request goes into indefinite polling status instead of using a retry period. .. We are currently having our IBM Marketing Rep. open the Design Change Request (DCR). for this feature defect. If anyone is experiencing this problem would you please have your IBM Marketing Rep. open a DCR for you. The more DCR's that are opened the sooner the not preferred behavior can be corrected. You can refer to our PMR # 32181. All help will be appreciated. Other than this the TSM Library Manager feature has been working fine. Philip A. James, Systems Software Specialist Software Services Unit Information Technology Services Division / Data Center California Public Employees' Retirement System Phone: (916) 326-3715 Fax: (916) 326-3884 Email: [EMAIL PROTECTED] -Original Message- From: Davidson, Becky [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Wednesday, December 04, 2002 12:27 PM To: [EMAIL PROTECTED] Subject: Re: 3494 Partitioning or TSM Library Manager I have implemented the TSM Library Manager feature. I have 14 drives shared among 4 TSM servers. When I tried the categories and use whatever was available if tsmsvr1 tried for drive 1 a couple of times and tsmsvr2 was using it then tsmsvr1 marked it offline. It made for a huge mess. Now I definitely have to keep tsmsvr2 (the server manager) up all the time unless I am booting the other servers. Occasionally I have had a check out for tsmsvr1 show successful yet the tapes don't come out because there were not enough drives. occasionally I have also had where you have to cycle the tsm software because there seems to be some communication problems. Generally that was when the operators didn't reply to the checkout and the checkout timed out. If I had a choice of whether to go back or not I wouldn't. This made things so much easier in the long run. My tsm server are running with one on an S85, two on a 6M1, and one on an S85 with all of them running aix 4.3.3 and after this weekend all of them running tsm 5.1 (two are still tsm 4.1.2) -Original Message- From: Joshua Bassi [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Wednesday, December 04, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: 3494 Partitioning or TSM Library Manager All, I am deploying 3 new TSM server on a single p690 LPAR. There is a 3494 with 32-tape drives attached to the system. I have a choice t
Re: 3494 Partitioning or TSM Library Manager
Have them take a look at PMR 02224,519 - we just upgraded from 4.2.1.15 to 4.2.30 because of an identified "internal defect". I don't have all the details in front of me, but at the 4.2.1.15 level there is apparently some communications issues. -Original Message- From: James, Phil [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 3:50 PM To: [EMAIL PROTECTED] Subject: Re: 3494 Partitioning or TSM Library Manager Importance: Low We have a similar problem with tape drive sharing. IBM summarized the problem very well below. This was the response listed in the PMR from IBM. Researched problem and found that the root cause of this problem is the same as that for pmr 04108,bre. .. The dismount command issues a dismount request the the drive, we make sure that the drive receives the command and we request a response. If we do not get an immediate response we retry the dismount 5X. .. If after the 5th retry we still cannot communicate with the drive we issue an IO error and mark the drive offline. .. In the event of library sharing and/or library fail-over a situation can occur where the drive is not available to the TSM server that issued the dismount command; in library fail-over the library is unavailable for a period of time that exceeds the amount of time it takes for the 5 retries (approximately 5 minutes), if the event of another server taking control over that drive (since we immediately release the drive after issuing the dismount request to the library) the TSM server that issued the request can no longer communicate with that drive and if this exceeds the retry period then we would mark the drive offline. .. While this is not preferred behavior it is not necessarily a defect. .. A DCR will have to be opened to request that in the case of library sharing and library fail-over the dismount request goes into indefinite polling status instead of using a retry period. .. We are currently having our IBM Marketing Rep. open the Design Change Request (DCR). for this feature defect. If anyone is experiencing this problem would you please have your IBM Marketing Rep. open a DCR for you. The more DCR's that are opened the sooner the not preferred behavior can be corrected. You can refer to our PMR # 32181. All help will be appreciated. Other than this the TSM Library Manager feature has been working fine. Philip A. James, Systems Software Specialist Software Services Unit Information Technology Services Division / Data Center California Public Employees' Retirement System Phone: (916) 326-3715 Fax: (916) 326-3884 Email: [EMAIL PROTECTED] -Original Message- From: Davidson, Becky [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Wednesday, December 04, 2002 12:27 PM To: [EMAIL PROTECTED] Subject: Re: 3494 Partitioning or TSM Library Manager I have implemented the TSM Library Manager feature. I have 14 drives shared among 4 TSM servers. When I tried the categories and use whatever was available if tsmsvr1 tried for drive 1 a couple of times and tsmsvr2 was using it then tsmsvr1 marked it offline. It made for a huge mess. Now I definitely have to keep tsmsvr2 (the server manager) up all the time unless I am booting the other servers. Occasionally I have had a check out for tsmsvr1 show successful yet the tapes don't come out because there were not enough drives. occasionally I have also had where you have to cycle the tsm software because there seems to be some communication problems. Generally that was when the operators didn't reply to the checkout and the checkout timed out. If I had a choice of whether to go back or not I wouldn't. This made things so much easier in the long run. My tsm server are running with one on an S85, two on a 6M1, and one on an S85 with all of them running aix 4.3.3 and after this weekend all of them running tsm 5.1 (two are still tsm 4.1.2) -Original Message- From: Joshua Bassi [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Wednesday, December 04, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: 3494 Partitioning or TSM Library Manager All, I am deploying 3 new TSM server on a single p690 LPAR. There is a 3494 with 32-tape drives attached to the system. I have a choice to make whether to use the old 3494 category scheme to separate my 3 TSM servers or should I use the TSM Library Manger feature to control access to all 32 tape drives? First of all, how many customers are using the Library Manager feature of TSM? What kind of caveats are there in deploying this feature? How well does the automatic tape drive allocation work? Thanks in advance. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED]
Re: 3494 Partitioning or TSM Library Manager
We have a similar problem with tape drive sharing. IBM summarized the problem very well below. This was the response listed in the PMR from IBM. Researched problem and found that the root cause of this problem is the same as that for pmr 04108,bre. .. The dismount command issues a dismount request the the drive, we make sure that the drive receives the command and we request a response. If we do not get an immediate response we retry the dismount 5X. .. If after the 5th retry we still cannot communicate with the drive we issue an IO error and mark the drive offline. .. In the event of library sharing and/or library fail-over a situation can occur where the drive is not available to the TSM server that issued the dismount command; in library fail-over the library is unavailable for a period of time that exceeds the amount of time it takes for the 5 retries (approximately 5 minutes), if the event of another server taking control over that drive (since we immediately release the drive after issuing the dismount request to the library) the TSM server that issued the request can no longer communicate with that drive and if this exceeds the retry period then we would mark the drive offline. .. While this is not preferred behavior it is not necessarily a defect. .. A DCR will have to be opened to request that in the case of library sharing and library fail-over the dismount request goes into indefinite polling status instead of using a retry period. .. We are currently having our IBM Marketing Rep. open the Design Change Request (DCR). for this feature defect. If anyone is experiencing this problem would you please have your IBM Marketing Rep. open a DCR for you. The more DCR's that are opened the sooner the not preferred behavior can be corrected. You can refer to our PMR # 32181. All help will be appreciated. Other than this the TSM Library Manager feature has been working fine. Philip A. James, Systems Software Specialist Software Services Unit Information Technology Services Division / Data Center California Public Employees' Retirement System Phone: (916) 326-3715 Fax: (916) 326-3884 Email: [EMAIL PROTECTED] -Original Message- From: Davidson, Becky [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Wednesday, December 04, 2002 12:27 PM To: [EMAIL PROTECTED] Subject: Re: 3494 Partitioning or TSM Library Manager I have implemented the TSM Library Manager feature. I have 14 drives shared among 4 TSM servers. When I tried the categories and use whatever was available if tsmsvr1 tried for drive 1 a couple of times and tsmsvr2 was using it then tsmsvr1 marked it offline. It made for a huge mess. Now I definitely have to keep tsmsvr2 (the server manager) up all the time unless I am booting the other servers. Occasionally I have had a check out for tsmsvr1 show successful yet the tapes don't come out because there were not enough drives. occasionally I have also had where you have to cycle the tsm software because there seems to be some communication problems. Generally that was when the operators didn't reply to the checkout and the checkout timed out. If I had a choice of whether to go back or not I wouldn't. This made things so much easier in the long run. My tsm server are running with one on an S85, two on a 6M1, and one on an S85 with all of them running aix 4.3.3 and after this weekend all of them running tsm 5.1 (two are still tsm 4.1.2) -Original Message- From: Joshua Bassi [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Wednesday, December 04, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: 3494 Partitioning or TSM Library Manager All, I am deploying 3 new TSM server on a single p690 LPAR. There is a 3494 with 32-tape drives attached to the system. I have a choice to make whether to use the old 3494 category scheme to separate my 3 TSM servers or should I use the TSM Library Manger feature to control access to all 32 tape drives? First of all, how many customers are using the Library Manager feature of TSM? What kind of caveats are there in deploying this feature? How well does the automatic tape drive allocation work? Thanks in advance. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED]
Re: 3494 Partitioning or TSM Library Manager
I have implemented the TSM Library Manager feature. I have 14 drives shared among 4 TSM servers. When I tried the categories and use whatever was available if tsmsvr1 tried for drive 1 a couple of times and tsmsvr2 was using it then tsmsvr1 marked it offline. It made for a huge mess. Now I definitely have to keep tsmsvr2 (the server manager) up all the time unless I am booting the other servers. Occasionally I have had a check out for tsmsvr1 show successful yet the tapes don't come out because there were not enough drives. occasionally I have also had where you have to cycle the tsm software because there seems to be some communication problems. Generally that was when the operators didn't reply to the checkout and the checkout timed out. If I had a choice of whether to go back or not I wouldn't. This made things so much easier in the long run. My tsm server are running with one on an S85, two on a 6M1, and one on an S85 with all of them running aix 4.3.3 and after this weekend all of them running tsm 5.1 (two are still tsm 4.1.2) -Original Message- From: Joshua Bassi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: 3494 Partitioning or TSM Library Manager All, I am deploying 3 new TSM server on a single p690 LPAR. There is a 3494 with 32-tape drives attached to the system. I have a choice to make whether to use the old 3494 category scheme to separate my 3 TSM servers or should I use the TSM Library Manger feature to control access to all 32 tape drives? First of all, how many customers are using the Library Manager feature of TSM? What kind of caveats are there in deploying this feature? How well does the automatic tape drive allocation work? Thanks in advance. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED]
FW: 3494 Partitioning or TSM Library Manager
Sorry, yes all these drives are Fibre Channel attached going through McData Sphereon 4500 switches. AIX 5.1 TSM 5.1.5.0 -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 8:18 AM To: '[EMAIL PROTECTED]' Subject: RE: 3494 Partitioning or TSM Library Manager I take it the drives are fiber attached... if not, you won't be able to share them between all three systems... Dwight -Original Message- From: Joshua Bassi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 10:19 AM To: [EMAIL PROTECTED] Subject: 3494 Partitioning or TSM Library Manager All, I am deploying 3 new TSM server on a single p690 LPAR. There is a 3494 with 32-tape drives attached to the system. I have a choice to make whether to use the old 3494 category scheme to separate my 3 TSM servers or should I use the TSM Library Manger feature to control access to all 32 tape drives? First of all, how many customers are using the Library Manager feature of TSM? What kind of caveats are there in deploying this feature? How well does the automatic tape drive allocation work? Thanks in advance. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED]
3494 Partitioning or TSM Library Manager
All, I am deploying 3 new TSM server on a single p690 LPAR. There is a 3494 with 32-tape drives attached to the system. I have a choice to make whether to use the old 3494 category scheme to separate my 3 TSM servers or should I use the TSM Library Manger feature to control access to all 32 tape drives? First of all, how many customers are using the Library Manager feature of TSM? What kind of caveats are there in deploying this feature? How well does the automatic tape drive allocation work? Thanks in advance. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED]
