|
Re: [ADSM-L] Library Manager and Migration question
2008-10-17 11:40:50
Thanks to everyone for all of the advice. My vendor has now assigned a new TSM
technician that knows about the Library Manager. Now, another issue has come
up about this.
I have 6 LAN-free clients, one of them is running on AIX in an HA environment.
I am assuming that all of the drives will need to be reconfigured once the
Library Manager is online and the server to server communication is redone on
the Manager and Clients. For now, the LAN-free clients will belong to the
original server and the library communication will of course be to the Library
Manager. Any gotchas in changing these clients, especially the HA client?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard Rhodes
Sent: Thursday, October 16, 2008 11:31 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Library Manager and Migration question
some more comments . . .
> > 228GB. We have finally received approval to move this to a new server,
> > upgrade to 5.5 and split the clients up to reduce the DB size.
We created new instances, then started assigning all new clients to the new
instances. Then, we went back and cherry picked the handfull of worse
clients and moved them to the new instances (some by occupance, some by
number
of files). To move them, some we
exported/imported while others we just created new nodes on the new
instance and retired the node on the origional TSM server.
> > Our current library configuration
> > has the library shared but it is not a library manager since we only
had one
> > server.
So, did you have multiple tsm instances on the server, each with their own
3584 partition and dedicated drives?
> > I sent him documentation and they also found
> > an IBM redbook on the subject but now says that it is too complicated
since
> > our server is so large and that I will need to partition the library,
with
> > some data loss!! I am strongly against this setup and would like to
know if
> > I am wrong.
No, you are NOT wrong! (or, is that "yes, you are NOT wrong!")
A library manger is the way to go.
> > How difficult would it be to create a library manager and
> > client setup for an existing environment?
Not very hard. The procedure CAN seem complicated, but when
you work through the steps it's not bad. The only trick
in the procedure is making sure the library manager assigns
the volume ownerships to the clients correctly. This is all
in the procedures.
First, make sure you understand how library sharing works
(see the Admin guide), then the redbook on converting to it.
I spent a fair amount of time working through the examples.
I then wrote a detailed procedure for the conversion
(sorry, I looked for it but can't find it), then got the
outage and performed the conversion. Understand, plan/plan/plan,
ask questions, then do it.
If you can think of a way to test out
a small library sharing environment first, then do it. We were
able to do this since we had new 3584 libraries onsite that were
waiting for library sharing to go in to use them. We used them to setup a
small library sharing environment to play with.
> > I currently have over 1000 tapes
> > onsite and as many offsite and naturally do not want to lose any data.
You won't! We had over 6-8thousand tapes in 2 3494 libraries and 2 3584's
with 300-400 tapes. We didn't loose a single tape when we converted!
The library manager environment has it's own issues you will need to
get your arms around. We spent some time balancing the batch schedules
between instances so as to not have one instance hog the drives. It
also becomes fun trying to get a big picture of what all the
instances are doing. I finally wrote a script to give a overall
picture of tape drive usage across the instances, and what
processes/sessions were using them (see below).
Here is the output of my status script . . .
rsfebkup1p.fenetwork.com:/tsmdata/tsm_scripts==>./q_tape_drive_status.ksh
== 200810161214
== library drive online paths(total/online/offline) state allocated_to
volume_name process/session
3584GO 3584GO-F01R01 YES 6/6/0 EMPTY
3584GO 3584GO-F01R02 YES 6/6/0 EMPTY
3584GO 3584GO-F01R03 YES 6/6/0 EMPTY
3584GO 3584GO-F01R04 YES 6/6/0 LOADED TSM1 J04183 PROCESS= 3921
Migration
3584GO 3584GO-F01R05 YES 6/6/0 EMPTY
3584GO 3584GO-F01R06 YES 6/6/0 LOADED TSM4 J04227 PROCESS= 1920 Backup
Storage Pool
3584GO 3584GO-F01R07 YES 6/6/0 EMPTY
3584GO 3584GO-F01R08 YES 6/6/0 EMPTY
3584GO 3584GO-F01R09 YES 6/6/0 EMPTY
3584GO 3584GO-F01R0A YES 6/6/0 EMPTY
3584GO 3584GO-F01R0B YES 6/6/0 LOADED TSM1 J04030 PROCESS= 3918
Migration
3584GO 3584GO-F01R0C YES 6/6/0 LOADED TSM1 J02729 PROCESS= 3917
Migration
3584GO 3584GO-F03R01 YES 22/22/0 EMPTY
3584GO 3584GO-F03R02 YES 22/22/0 EMPTY
3584GO 3584GO-F03R03 YES 22/22/0 EMPTY
3584GO 3584GO-F03R04 YES 22/22/0 EMPTY
3584GO 3584GO-F03R05 YES 22/22/0 LOADED STASAPEI1D1 J04507 SESSION=
38572 SAPEI1D1_DB
3584GO 3584GO-F03R06 YES 22/22/0 EMPTY
3584GO 3584GO-F03R07 YES 22/22/0 EMPTY
3584GO 3584GO-F03R08 YES 22/22/0 EMPTY
3584GO 3584GO-F03R09 YES 22/22/0 EMPTY
3584GO 3584GO-F03R0A YES 22/22/0 EMPTY
3584GO 3584GO-F03R0B YES 22/22/0 EMPTY
3584GO 3584GO-F03R0C YES 22/22/0 EMPTY
3584GO 3584GO-F04R01 YES 22/22/0 EMPTY
3584GO 3584GO-F05R01 YES 6/6/0 EMPTY
3584GO 3584GO-F05R02 YES 6/6/0 LOADED TSM1 J02733 PROCESS= 3919
Migration
3584GO 3584GO-F05R03 YES 6/6/0 LOADED TSM3 J04195 PROCESS= 2552
Migration
3584GO 3584GO-F05R04 YES 6/6/0 LOADED TSM4 J04410
3584GO 3584GO-F05R05 YES 6/6/0 EMPTY
3584GO 3584GO-F05R06 YES 6/6/0 LOADED TSM1 J04078 PROCESS= 3920
Migration
3584GO 3584GO-F05R07 YES 6/6/0 EMPTY
3584GO 3584GO-F05R08 YES 6/6/0 EMPTY
3584GO 3584GO-F05R09 YES 6/6/0 EMPTY
3584GO 3584GO-F05R0A YES 6/6/0 LOADED TSM3 J04525 PROCESS= 2550
Migration
3584GO 3584GO-F05R0B YES 6/6/0 EMPTY
3584GO 3584GO-F05R0C YES 6/6/0 EMPTY
3584GO 3584GO-F06R01 YES 6/6/0 EMPTY
3584GO 3584GO-F06R02 YES 6/6/0 EMPTY
3584GO 3584GO-F06R03 YES 6/6/0 EMPTY
3584GO 3584GO-F06R04 YES 6/6/0 EMPTY
3584GO 3584GO-F06R05 YES 6/6/0 EMPTY
3584GO 3584GO-F06R06 YES 6/6/0 LOADED TSM3 J02734 PROCESS= 2551
Migration
3584GO 3584GO-F06R07 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F01R01 YES 6/6/0 LOADED TSM2 J03295 PROCESS= 4912
Migration
3584ISOC 3584ISOC-F01R02 YES 6/6/0 LOADED TSM4 J02067 PROCESS= 1923
Migration
3584ISOC 3584ISOC-F01R03 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F01R04 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F01R05 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F01R06 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F01R07 YES 6/6/0 LOADED TSM2 J01032 PROCESS= 4915
Migration
3584ISOC 3584ISOC-F01R08 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F01R09 YES 6/6/0 LOADED TSM2 J03167 PROCESS= 4916
Migration
3584ISOC 3584ISOC-F01R0A YES 6/6/0 LOADED TSM4 J03567 PROCESS= 1922
Migration
3584ISOC 3584ISOC-F01R0B YES 6/6/0 LOADED TSM4 J02105 PROCESS= 1924
Migration
3584ISOC 3584ISOC-F01R0C YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F03R01 YES 22/22/0 LOADED STASAPEQ2D1 J03446 SESSION=
3237 SAPEQ2D1_DB
3584ISOC 3584ISOC-F03R02 YES 22/22/0 EMPTY
3584ISOC 3584ISOC-F03R03 YES 22/22/0 EMPTY
3584ISOC 3584ISOC-F03R04 YES 22/22/0 EMPTY
3584ISOC 3584ISOC-F03R05 YES 22/22/0 LOADED STASAPBWPC2 J02529 SESSION=
6228 SAPBWPC2_SSP_DB
3584ISOC 3584ISOC-F03R06 YES 22/22/0 LOADED STASAPEQ3D1 J03517 SESSION=
2417 SAPEQ3D1_DB
3584ISOC 3584ISOC-F03R07 YES 22/22/0 LOADED TSMSAP2 J03537 PROCESS= 467
Migration
3584ISOC 3584ISOC-F03R08 YES 22/22/0 LOADED STASAPEQ1D1 J03238 SESSION=
4303 SAPEQ1D1_DB
3584ISOC 3584ISOC-F03R09 YES 22/22/0 EMPTY
3584ISOC 3584ISOC-F03R0A YES 22/22/0 LOADED TSMSAP2 J03580 PROCESS= 466
Migration
3584ISOC 3584ISOC-F03R0B YES 22/22/0 LOADED TSMSAP2 J00002 PROCESS= 465
Migration
3584ISOC 3584ISOC-F03R0C YES 22/22/0 LOADED STASAPBWPC2 J03624 SESSION=
6223 SAPBWPC2_SSP_DB
3584ISOC 3584ISOC-F04R01 YES 6/6/0 LOADED TSM4 J02233 PROCESS= 1920
Backup Storage Pool
3584ISOC 3584ISOC-F04R02 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F04R03 YES 6/6/0 LOADED TSM2 J03666 PROCESS= 4914
Migration
3584ISOC 3584ISOC-F04R04 YES 6/6/0 LOADED TSM2 J02165
3584ISOC 3584ISOC-F04R05 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F04R06 YES 6/6/0 LOADED TSM4 J00823 SESSION= 1150727
WISR06P
3584ISOC 3584ISOC-F04R07 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F04R08 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F04R09 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F04R0A YES 6/6/0 LOADED TSM2 J03391 PROCESS= 4913
Migration
3584ISOC 3584ISOC-F04R0B YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F04R0C YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R01 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R02 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R03 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R04 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R05 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R06 YES 6/6/0 EMPTY
3584ISOC 3584ISOC-F05R07 YES 6/6/0 LOADED TSMLM2 J00234
3584ISOC 3584ISOC-F05R08 YES 6/6/0 LOADED TSM2 J03308 SESSION= 3472699
ISOC-MAIL01
3584ISOC 3584ISOC-F05R09 YES 6/6/0 EMPTY
=== lib drives_loaded drives_not_loaded
=== 200810161214 3584isoc 13 20 3584isocSAP 8 4 3584go 10 21
3584goSAP 1 12 unknown 0
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
|
|
|
