Re: Can't see the library, Slightly off topic TSM question

Fred.Bateman_at_usdoj.gov
Date: 06/29/05

  • Next message: True V. Jack: "How to compute free space on Physical Disks?"
    Date:         Wed, 29 Jun 2005 06:20:18 -0400
    To: aix-l@Princeton.EDU
    
    

    Andrew,

    Have you resolved this problem?

    Some things to try:
    1) ADSM-L@VM.MARIST.EDU - tsm mailing list
    2) With a 3584 you should have rmtX devices (atape) not
            mtX devices (TSM). Did you upgrade your atape software
            when you upgraded AIX?
            2.1) Check atape software.
            2.2) Delete mt devices
            2.3) Delete rmt devices
            2.4) Run cfgmgr.
    3) Check TSM paths. In a SAN environment, the same
            tape drive will not always be the same rmt device
            on the different machines.
    4) The smc device is not needed on the StorageAgent - you
            do not need to worry about that.

    Fred

    -----Original Message-----
    From: aix-l@Princeton.EDU [mailto:aix-l@Princeton.EDU]
    Sent: Wednesday, June 22, 2005 5:07 PM
    To: aix-l@Princeton.EDU
    Subject: Re: Can't see the library, Slightly off topic TSM question
    Importance: Low

    Thanks Simon.

    I actually did do that. I did an

    "rmdev -Rdl fsdcsi1"

    Which deleted the four drives attached to the fiber device and the fiber
    device.

    Here is the wierd thing. The first drive in the library (3584)is NOT
    zoned
    to this node but four other drives (out of 8) are. I am under the
    impression that the library communicates over the same fiber line as the
    first tape drive (the first tape drive in the library which again is not
    connected to the node having the issues).

    When this used to work before the AIX upgrade (although I am not 100%
    the
    upgrade broke it but it seems timely), we used a Storage Agent to
    restore
    the data. Now, we can't seem to use the Storage Agent because it can't
    see
    the library. Our current work around has been to disable the Storage
    Agent
    and perform backups over the network rather then directly from tape
    using
    the Storage Manager (much slower).

    What am I missing?

     

                          "Green, Simon"

                          <Simon.Green@EU.A To:
    aix-l@Princeton.EDU

                          LTRIA.COM> cc:

                          Sent by: IBM AIX Subject: Re: Can't see
    the library, Slightly off topic TSM question
                          Discussion List

                          <aix-l@Princeton.

                          EDU>

     

     

                          06/22/2005 04:52

                          AM

                          Please respond to

                          IBM AIX

                          Discussion List

     

    I would probably start by deleting your tape drives - completely: rmdev
    -d
    -
    and associated devices, and re-defining them.

    --
    Simon Green
    Altria ITSC Europe s.a.r.l.
    AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
    New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
    N.B. Unsolicited email from vendors will not be appreciated.
    Please post all follow-ups to the list.
    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
    Drew
    T
    Sent: 21 June 2005 18:29
    To: aix-l@Princeton.EDU
    Subject: Can't see the library, Slightly off topic TSM question
    Well I think I found the problem.
    It appears that the TSM client, which uses a Storage Agent for Lan Free
    backups does not have the library defined.
    Here some output from our dev box:
    [root ] /dev >>lsdev -Cc tape
    rmt0 Available 4Y-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    rmt1 Available 4Y-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    rmt2 Available 4Y-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    rmt3 Available 4Y-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    Here is the outupt from a lab box from which we can successfully restore
    the same exact files to:
    # lsdev -Cc tape
    rmt0 Available 47-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    rmt1 Available 47-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    rmt2 Available 47-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    rmt3 Available 47-08-01 IBM 3580 Ultrium Tape Drive (FCP)
    smc0 Available 47-08-01 IBM 3584 Library Medium Changer (FCP)
    As you can see I do not have smc0 defined or available on the top TSM
    client.
    when I run cfgmgr, I am getting:
    ------------------------------------------------------------------------
    ---
    [root] /dev >>cfgmgr
    Method error (/etc/methods/cfgtsmdd -l mt0 ):
            0514-051 Device to be configured does not match the physical
                     device at the specified connection location.
    Method error (/etc/methods/cfgtsmdd -l mt1 ):
            0514-051 Device to be configured does not match the physical
                     device at the specified connection location.
    Method error (/etc/methods/cfgtsmdd -l mt2 ):
            0514-051 Device to be configured does not match the physical
                     device at the specified connection location.
    Method error (/etc/methods/cfgtsmdd -l mt3 ):
            0514-051 Device to be configured does not match the physical
                     device at the specified connection location.
    Method error (/usr/lib/methods/scsimap >> /var/adm/essmap.out):
            0514-023 The specified device does not exist in the
                     customized device configuration database.
    ------------------------------------------------------------------------
    ----
    Any other thoughts?
    

  • Next message: True V. Jack: "How to compute free space on Physical Disks?"