ADSM-L

[ADSM-L] New Tape Library

2008-06-18 03:13:10
Subject: [ADSM-L] New Tape Library
From: Adrian Compton <acompton AT ASPENPHARMA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 18 Jun 2008 09:11:35 +0200
Hi all 

 

My favorite forum is required once again for its invaluable knowledge.

I am upgrading my tape library (3583) to a TS3200.

Runs on Linux (small satellite site) SUSE 4 on an IBM xServer i686. TSM
5.5

I have a 2 port FC HBA card in it.

 

I really want confirmation on the best method to switch over to the new
library.

 

Should I perform the following?

 

1.       Halt TSM

2.       Connect New Library

3.       Confirm Connection to OS

4.       Create new device class to new library

5.       Start TSM

6.       Configure new paths to drives and library

7.       delete old library and its paths

8.       checkin all tapes from old library as private

 

I remember somewhere there is a problem linking the copy pool tapes to
the new library.

 

Any help/suggestions would be appreciated.

 

 

Adrian Compton

IT Baan Operation/ Group IBM Tivoli Admin

Pharmacare Limited trading as Aspen Pharmacare

P O Box 4002

Korsten

Port Elizabeth

6014

Switchboard Tel No: +27 (0) 41 407 2111

Tel No: +27 (0) 41 407 2855

Fax: +27 (0) 41 453 7452

Cell: +27 (0) 82 320 4495

Email : acompton AT aspenpharma DOT com   This email is solely for the named
addressee.   Any unauthorised use or interception of this email, or the
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon the contents of this email, by persons or
entities other than the intended recipient, is prohibited. If you are
not the named addressee please notify us immediately by way of a reply
e-mail, and also delete this email and any attached files.

Disclaimer:  You must scan this email and any attached files for viruses
and/or any other defects.  Pharmacare Limited accepts no liability for
any loss, damages or consequence, whether direct, indirect,
consequential or economic, however caused, and whether by negligence or
otherwise, which may result directly or indirectly from this
communication or of any attached files.  

 

 

<Prev in Thread] Current Thread [Next in Thread>