ADSM-L

Re: Update - Tape problem after moving TSM to new server

2006-03-27 05:08:18
Subject: Re: Update - Tape problem after moving TSM to new server
From: Farren Minns <fminns AT WILEY.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 27 Mar 2006 11:02:42 +0100
Morning all

Regarding my problem with this, does anyone know what the following devices
are ? There are just two 3590s fibre attached to this new server so I don't
know where the other two came from or what they are. If it wasn't for them,
the drives would still have the same /dev/rmt/???? mappings as the original
drives on the old server and then all my problems would go away... maybe
:-)

Any ideas

These are the drives I expect to see :-

lrwxrwxrwx   1 root     root          59 Mar 15 11:43 2st ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:st
lrwxrwxrwx   1 root     root          60 Mar 15 11:43 2stb ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stb
lrwxrwxrwx   1 root     root          61 Mar 15 11:43 2stbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stbn
lrwxrwxrwx   1 root     root          60 Mar 15 11:43 2stc ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stc
lrwxrwxrwx   1 root     root          61 Mar 15 11:43 2stcb ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stcb
lrwxrwxrwx   1 root     root          62 Mar 15 11:43 2stcbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stcbn
lrwxrwxrwx   1 root     root          61 Mar 15 11:43 2stcn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stcn
lrwxrwxrwx   1 root     root          60 Mar 15 11:43 2stn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@0,0:stn
lrwxrwxrwx   1 root     root          59 Mar 15 11:43 3st ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:st
lrwxrwxrwx   1 root     root          60 Mar 15 11:43 3stb ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stb
lrwxrwxrwx   1 root     root          61 Mar 15 11:43 3stbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stbn
lrwxrwxrwx   1 root     root          60 Mar 15 11:43 3stc ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stc
lrwxrwxrwx   1 root     root          61 Mar 15 11:43 3stcb ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stcb
lrwxrwxrwx   1 root     root          62 Mar 15 11:43 3stcbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stcbn
lrwxrwxrwx   1 root     root          61 Mar 15 11:43 3stcn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stcn
lrwxrwxrwx   1 root     root          60 Mar 15 11:43 3stn ->
../../devices/pci@1e,600000/IntraServer,fc@2/IBMtape@1,0:stn

But what are these devices? Any dieas?

lrwxrwxrwx   1 root     root          52 Mar 15 11:43 0 ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0b ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:b
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0bn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:bn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0c ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:c
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0cb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:cb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 0cbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:cbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0cn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:cn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0h ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:h
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0hb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:hb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 0hbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:hbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0hn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:hn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0l ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:l
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0lb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:lb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 0lbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:lbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0ln ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:ln
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0m ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:m
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0mb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:mb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 0mbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:mbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0mn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:mn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0n ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:n
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 0u ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:u
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0ub ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:ub
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 0ubn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:ubn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 0un ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@0,0:un
lrwxrwxrwx   1 root     root          52 Mar 15 11:43 1 ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1b ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:b
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1bn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:bn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1c ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:c
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1cb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:cb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 1cbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:cbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1cn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:cn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1h ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:h
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1hb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:hb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 1hbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:hbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1hn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:hn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1l ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:l
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1lb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:lb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 1lbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:lbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1ln ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:ln
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1m ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:m
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1mb ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:mb
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 1mbn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:mbn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1mn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:mn
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1n ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:n
lrwxrwxrwx   1 root     root          53 Mar 15 11:43 1u ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:u
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1ub ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:ub
lrwxrwxrwx   1 root     root          55 Mar 15 11:43 1ubn ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:ubn
lrwxrwxrwx   1 root     root          54 Mar 15 11:43 1un ->
../../devices/pci@1e,600000/IntraServer,fc@2/st@1,0:un
|-----------------------------+-------------------------------------------|
|   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|
|                             |                                           |
|   26/03/2006 18:54          |                                    Subject|
|                             |                  Re: [ADSM-L] Update -    |
|         Please respond to   |                  Tape problem after moving|
|         "ADSM: Dist Stor    |                  TSM to new server        |
|             Manager"        |                                           |
|      <ADSM-L AT VM.MARIST DOT EDU> |                                          
 |
|                             |                                           |
|                             |                                           |
|                             |                                           |
|                             |                                           |
|-----------------------------+-------------------------------------------|








This happened to me too, when doing a similar migration. I looked up my
notes from the time.

The problem is that your Filling tapes were started on a different
drive type than you have now, and so it won't append any more data onto
them. (Even if they are the very same drives, this can still happen.)

How to deal with it:

1. Get some extra tapes, to use while you do the following steps. Before
you do anything else after the big change, LABEL LIBVOL these new tapes
so there will be something for migration and DB backup to use.

2. Mark all your Filling and Full tapes Readonly. You will still be able
to restore from them OK. If you don't already have it, set a REUSEDELAY
of a day or two.

3. The Full tapes should reclaim themselves normally. However,
reclamation will not select any tape that is still marked as Filling, so
you've got to reclaim them manually yourself with MOVE DATA. Might take
a while, which is OK as long as you don't run out of tapes.

4. As tapes are cleared, whether they had been Filling (via MOVE DATA)
or Full (via reclamation), you may need to do CHECKOUT LIBVOL on them
followed by a LABEL LIBVOL OVERWRITE=YES before it will reuse them as
scratch tapes. When you get a mixture of Pending tapes from before and
after the big change, then you can easily tell which ones you need to
relabel - they will be the ones that are both Pending and Readonly.

When this happened to me, it was a hassle, but I found that it was a
manageable hassle. I did not have to do anything as drastic as the
backout you did. Sorry to hear about that - because you are having to do
3 times the work with a migrate-backout-migrate cycle.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu



On Sat, 25 Mar 2006, Farren Minns wrote:

>OK, this is what I have now found out but had no idea what's going on.
>After completely removing and redefining the lib,drives and paths I still
>get the same errors as below. So, for example I can't audit volume 000700
>without the error below.
>
>BUT..., if I change the state of the volume from read/write to readonly, I
>can. What's that all about? I can also audit volumes that have an access
of
>read/write but that are 'full' and not 'filling'. This is very strange.
Has
>anyone else ever seen this behaviour before ?
>
>Many thanks again
>
>Farren Minns
>
>
>>Hi All
>
>>I have just moved my TSM Server 5.1.6.2 from a Solaris 7 server to a new
>Solaris 9  box. Now, everything so far has gone fine and I have tested a
>couple of >backups and also a backup of the database.
>
>>When I look at the contents of the tapepool, copypool, q libv etc I see
>what I would expect.
>
>>BUT, when I try to run migration from disk to tape there is a problem. In
>this example tape 000700 which is in a filling state is required but I see
>the following error :-
>
>>ANR1000I Migration process 4 started for storage pool BACKUPPOOL.
>>ANR8447E No drives are currently available in library 3494A.
>>ANR1401W Mount request denied for volume 000700 - mount failed.
>
>>Instead, TSM loads a new scratch tape and then continues fine. What is
>going on here? Has any body seen this before?
>
>>Thanks in advance
>
>>Farren Minns
>
>
>######################################################################
>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.
######################################################################