IBM Support

IT20619: BACKUP OF A NON-ROOT SNAPSHOT USES DEFAULT MANAGEMENT CLASS INSTEAD OF THE ONE SPECIFIED BY INCLUDE STATEMENT

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When taking a backup of a snapshot of a fileset using mmbackup,
    with management class binding
    via "include" statement in place, the management class binding
    does not work,
    other then for a root snapshot.
    
    For example:
    
    Include looks like:
    
       include            /gpfs_filesystem_name/fs00/vtl/.../*
    MC_VTL
    
    
    Snapshot looks like this:
    
     mmlssnapshot  fs00   <enter>
    
     Snapshots in file system fs00:
     Directory                SnapId    Status  Created
     Fileset
     two                     13        Valid   Mon Apr  3 12:38:15
    2017
    
    When management class binding is successful, it will
    show the backup using Mgmt Class MC_VTL.
    
    mmbackup command to backup the root snapshot is:
    
       mmbackup /gpfs_filesystem_name/fs00/vtl -N rb-gpfs-01
    --tsm-servers=tsm-gpfs
     --scope=inodespace -t full
    
    Then checking with:
    
    dsmc q backup "/gpfs_filesystem_name/fs00/vtl/d/*" -se=tsm-gpfs
    
    
    
     Accessing as node: NODE_NAME
                Size        Backup Date                Mgmt Class
     A/I File
                ----        -----------                ----------
     --- ----
                  0  B  04/03/2017 12:59:06              MC_VTL
     A  /gpfs_filesystem_name/fs00/vtl/d/two.d
                  0  B  04/03/2017 12:59:06              MC_VTL
     A  /gpfs_filesystem_name/dir_name/vtl/d/two.d.txt
    
    As soon as a non-root snapshot is used the management class
    binding fails,
    mand binds to the default management class instead of "MC_VTL".
    
    mmbackup command to back up the non-root snapshot:
    
    mmbackup /gpfs/fs01/vtl -N rb-gpfs-01
     --tsm-servers=tsm-gpfs -S two --scope=inodespace -t full
    
    (notice "-S two" indicates it is a non-root snapshot)
    
    Checking again with:
    dsmc q backup "/gpfs_filesystem_name/fs00/vtl/d/*" -se=tsm-gpfs
    
     Node Name: NODE_NAME-01
    
    
     Accessing as node: NODE_NAME
                Size        Backup Date                Mgmt Class
     A/I File
                ----        -----------                ----------
     --- ----
                  0  B  04/03/2017 12:58:19             DEFAULT
     A  /gpfs_filesystem_name/fs00/vtl/d/two.d
                  0  B  04/03/2017 12:58:19             DEFAULT
     A  /gpfs_filesystem_name/fs00/vtl/d/two.d.txt
    
     now shows the backup data bound to default management class.
    
    
    
    
    Tivoli Storage Manager and IBM Spectrum Protect versions
    affected:
    Client 6.4.x,  7.1.x and 8.1.x and higher on all supported
    platforms
    
    
    
    Initial Impact: Medium
    
    Additional Keywords:  TSM IBM Spectrum Protect snapshot
    mgmtclass rebind include mmbackup
    

Local fix

  • If able, change the default mgmtclass to be the desired
    managment class needing to be used by
    non-root snapshot backup.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Spectrum Protect backup-archive client versions 7.1.0-7.1.6  *
    * and 8.1.0 on AIX and Linux platforms.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is projected *
    * to be fixed in level 7.1.8 and 8.1.2. Note that this is      *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • After the fix files under fileset directory are bound to
    specified in dsm.sys management class.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT20619

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    81L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-17

  • Closed date

    2017-06-20

  • Last modified date

    2017-06-20

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

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

Modules/Macros

  • dsmc
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R81L PSY

       UP

  • R81A PSY

       UP

  • R71L PSY

       UP

  • R71A PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 81L

Reference #: IT20619

Modified date: 20 June 2017