IBM Support

IC75518: BACKUP STGPOOL OF NAS TYPE DATA CAN CAUSE RESERVATION CONFLICT ON DRIVE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a Backup Stgpool (of NAS type data ONLY) is running during
    the same time period as another server process using volumes
    with NAS type data, the Backup Stgpool may have to wait for
    access to an input volume. While the process is waiting, the
    TCP/IP session to the NAS device will be idle. If the session is
    disconnected (due to a firewall timeout or other situation
    outside of Tivoli Storage Manager), the NAS device will hold a
    reservation on a drive in the library. Since the server is
    unable to remove this reservation (and we believe the filer will
    clean up the reservation on it's end), it will later attempt to
    access the drive and fail with an error similar to the
    following:
    
    ANR8844E Unable to open remote drive DRIVE1  (rst4a), error
    code=13
    Error code=13 is a Tivoli Storage Manager translation of NDMPrc
    2, which means DEVICE_BUSY
    

Local fix

  • Reset the drives to release the reservation conflict. In order
    to prevent the problem:
    1) Do not run other NAS processes simultaneously with BACKUP
    STGPOOL.
    2) Increase the idle timeout for TCP/IP sessions on the firewall
    (or other device ending the sessions)
    3) Use the NO (Network Options) command on AIX in order to
    modify the TCP_KEEPIDLE option (to a value lower than the
    firewall timeout value)
    NOTE: This command will be slighty different on other operating
    systems
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager Server users of   *
    *                 NDMP backup                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: This fix enables TCP KEEP_ALIVE         *
    *                      packets on NDMP control connections.    *
    *                      However users with servers running      *
    *                      on Solaris, HP-UX or Linux must         *
    *                      set the "idle-time" interval at the     *
    *                      Operating system level. This value      *
    *                      should be less than any idle timeout    *
    *                      setting in a firewall between the       *
    *                      server and NAS device. For example      *
    *                      to set the idle time for KEEP_ALIVES    *
    *                      on Solaris to 15 minutes use the        *
    *                      following command:                      *
    *                        ndd -set                              *
    *                          /dev/tcp tcp_keepalive_interval     *
    *                           900000                             *
    *                      The number 900000 is the number of      *
    *                      milliseconds of idle time that          *
    *                      TCP/IP will wait before sending the     *
    *                      first KEEP_ALIVE packet.                *
    ****************************************************************
    * RECOMMENDATION:  Apply fixing level when available. This     *
    *                 problem is currently projected to be         *
    *                  fixed in levels 5.5.6, and 6.2.4.  *
    *                 Note  that this is subject to change at the  *
    *                 discretion of IBM.                           *
    ****************************************************************
    *
    

Problem conclusion

  • Affected platforms: AIX, HP-UX, Solaris, Linux and Windows
    The TSM server now enables TCP KEEP_ALIVE packets on NDMP
    control connections to prevent firewalls from timing out
    these connections during periods of inactivity.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC75518

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-01

  • Closed date

    2011-08-30

  • Last modified date

    2013-08-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R55A PSY

       UP

  • R55H PSY

       UP

  • R55L PSY

       UP

  • R55S PSY

       UP

  • R55W PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61L PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R62A PSY

       UP

  • R62H PSY

       UP

  • R62L PSY

       UP

  • R62S PSY

       UP

  • R62W PSY

       UP

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"61A"}]

Document Information

Modified date:
18 September 2021