Hi me again
>From the points on the list (below) is says to delete and redefine the
lib,drives etc because of possible changed scsi-id's, but the library is
referred to by it's alias in the ibmatl.conf file, and this alias will be
the same on the new server. I know this works as I can use the mtlib
command to speak to it. So I really can't see a reason to redefine, and
thus I wont have to checkin the vols again.
I may be missing something here of course.
15. delete all paths, drives and libraries
16. define all paths, libraries and drives again
you must do step 15. and 16. because of possible changed scsi-id's
17. checkin libv <library> search=yes status=scratch checklabel=barcode
18. checkin libv <library> search=yes status=private checklabel=barcode
Many thanks
Farren
|-----------------------------+-------------------------------------------|
| Roger Deschner | |
| <rogerd AT UIC DOT EDU> |
|
| Sent by: "ADSM: Dist Stor | To|
| Manager" | ADSM-L AT VM.MARIST DOT EDU
|
| <ADSM-L AT VM.MARIST DOT EDU> |
cc|
| | |
| 17/03/2006 16:01 | Subject|
| | Re: [ADSM-L] New TSM |
| Please respond to | Server, DB and STG |
| "ADSM: Dist Stor | POOL question |
| Manager" | |
| <ADSM-L AT VM.MARIST DOT EDU> |
|
| | |
| | |
| | |
| | |
|-----------------------------+-------------------------------------------|
Prior to TSM 5 you could get away with just an inventory, but now it has
become necessary to delete and redefine the paths, which will wipe out
all your libvols. (TSM 4 didn't even have paths.) It is critical to do
the two checkin libvol commands in the order in your list - scratch
first, and then private - otherwise you will lose all your scratch
tapes.
TEST the checkin libvol step FIRST! I have been bitten badly, twice, by
failures in the driver or the library itself preventing checkin libv
from working. This has caused us long milti-day downtimes twice during
the past year. This happened to us with a simple tape library upgrade,
adding more slots to the same Quantum P7000 library.
The danger you run is that with new versions of both Solaris and TSM,
you are running different drivers, which could make library operations
fail. Make sure this is going to work before you get into a situation
where you can't back out. If things go wrong in this area you face a
LONG downtime with a LOT of finger-pointing between IBM/Tivoli, Sun, and
your tape library maker. They will each blame somebody else. It will get
very ugly.
Other than that, you are changing too many things at once for comfort.
Last time I made a server change, I took great pains to insure that the
TSM and AIX versions on the old and new servers were identical. At least
this way, you can limit the scope of what went wrong.
Roger Deschner University of Illinois at Chicago rogerd AT uic DOT edu
Anything you try to fix will take longer and cost more than you thought.
On Thu, 16 Mar 2006, Farren Minns wrote:
>TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9
>
>Hi all
>
>Regarding Anton's check list below, I have a couple of questions.
>
>1) Do I really need to delete and redefine the drives,libray,paths etc? I
>understand that I will need to update the /dev/rmt/??? entry for the
drives
>to make sure they reflect how the drives are viewed on the new system. But
>apart from that things should in my mind be exactly the same as before. As
>far as the library is concerned, it's just an alias in the ibmatl.conf
file
>anyway and I know that works as I can use the mtlib command to interrogate
>it. Am I missing something?
>
>and...
>
>2) Do I really need to run the 'checkin libv' commands. Looking at the
>newly restored system I can see that TSM knows all the vols in the
TAPEPOOL
>and also the qlibv command shows me the volumes I also see on the still
>live server. Again, am I missing something?
>
>Many thanks again for this list Anton, much appreciated.
>
>All the best
>
>Farren Minns
>|-----------------------------+-------------------------------------------|
>| anton walde |
|
>| <nummer5lebt AT GMX DOT DE> |
|
>| Sent by: "ADSM: Dist Stor |
To|
>| Manager" |
ADSM-L AT VM.MARIST DOT EDU |
>| <ADSM-L AT VM.MARIST DOT EDU> |
cc|
>| |
|
>| 15/03/2006
15:44 | Subject|
>| | Re: [ADSM-L] New
TSM |
>| Please respond to | Server, DB and
STG |
>| "ADSM: Dist Stor | POOL question
|
>| Manager" |
|
>| <ADSM-L AT VM.MARIST DOT EDU> |
|
>| |
|
>| |
|
>| |
|
>| |
|
>|-----------------------------+-------------------------------------------|
>
>
>
>
>
>
>
>
>Hallo.
>
>
>We changed our Hardware a year ago. We asked support to help us and got a
>good hand-out with all the steps to make.
>
>Here is the 'cook book':
>
>1. you must have the samt TSM-Version on the old and new server.
>2. migrate all diskpools to tape
>3. backup the TSM-DB on the old server maybe to a file-devclass
> ( better for restore )
>4. stop the old server
>5. save all the config-files from the old server
> ( dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock )
>6. connect the libraryies to the new server
>7. install the tsm device driver on the new server
> all the following steps are on the new server
>8. copy the config-files from step 5. to the new server, over
> the existing!
>9. create log-files and db-files with dsmserv format
>10. check the config-files! for example the devconfig.out
> for devclass,devices,pathes,etc.
>11. restore the db from step 3.
>12. change dsm.opt:
> nomigrrecl
> expinterval =
> disablescheds yes
>13. start the tsm-server in foreground ( dsmserv )
>14. disable sessions
>15. delete all paths, drives and libraries
>16. define all paths, libraries and drives again
>you must do step 15. and 16. because of possible changed scsi-id's
>17. checkin libv <library> search=yes status=scratch checklabel=barcode
>18. checkin libv <library> search=yes status=private checklabel=barcode
>19. create the diskpools. If you have another directory-name for
> the volumes, you must delete the old ones and define new ones.
>20. If everything runs fine, stop the server ( halt server ), remove
> the options you defined in step 12 from dsm.opt and start the
> tsm-server as a service like you did on the old hardware
>
>THAT'S IT!
>
>Hope that helps you.
>
>
>
>Kind regards
>
>Robert Fijan
>
>
>--
>Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer!
>Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer
>
>
>######################################################################
>The information contained in this e-mail and any subsequent
>correspondence is private and confidential and intended solely
>for the named recipient(s). If you are not a named recipient,
>you must not copy, distribute, or disseminate the information,
>open any attachment, or take any action in reliance on it. If you
>have received the e-mail in error, please notify the sender and delete
>the e-mail.
>
>Any views or opinions expressed in this e-mail are those of the
>individual sender, unless otherwise stated. Although this e-mail has
>been scanned for viruses you should rely on your own virus check, as
>the sender accepts no liability for any damage arising out of any bug
>or virus infection.
>######################################################################
>
######################################################################
The information contained in this e-mail and any subsequent
correspondence is private and confidential and intended solely
for the named recipient(s). If you are not a named recipient,
you must not copy, distribute, or disseminate the information,
open any attachment, or take any action in reliance on it. If you
have received the e-mail in error, please notify the sender and delete
the e-mail.
Any views or opinions expressed in this e-mail are those of the
individual sender, unless otherwise stated. Although this e-mail has
been scanned for viruses you should rely on your own virus check, as
the sender accepts no liability for any damage arising out of any bug
or virus infection.
######################################################################
|
