IT09016: TIVOLI STORAGE MANAGER IMAGE BACKUPS CREATE MULTIPLE ACTIVE TEMPORARY OBJECTS IF THE BACKUP IS INTERRUPTED AND RETRIED.

IBM Spectrum Protectâ„¢ Client 7.1.4 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• When running an image backup of a filespace to the Tivoli
  Storage Manager server, if the backup is interrupted and
  restarted there is a timing window in which this will result in
  multiple active temporary objects being created. Unlike normal
  objects these objects will not be marked as inactive when the
  backup finishes or the next backup is run and will remain active
   on the server. Because of the active status they will never
  expire.
  
  Customer/L2 Diagnostics:
  From dsmadmc run the following command to check the DB for
  multiple active objects. Temporary objects will have a temporary
  filespace name of TSM_TEMP_GROUPLEADER followed by the date
  
  select * from backups where node_name='NODE1' and type='IMAGE'
  
        NODE_NAME: NODE1
   FILESPACE_NAME: \\NODE1\d$
     FILESPACE_ID: 11
            STATE: ACTIVE_VERSION
             TYPE: IMAGE
          HL_NAME:
  \TSMIMAGE-WINNT\\\TSM_TEMP_GROUP_LEADER10/16/2014 13 38:07\
          LL_NAME: FULL
        OBJECT_ID: 12961842
      BACKUP_DATE: 2014-10-16 13:38:13.000000
  DEACTIVATE_DATE:
            OWNER:
       CLASS_NAME: DEFAULT
  
        NODE_NAME: NODE1
   FILESPACE_NAME: \\NODE1\d$
     FILESPACE_ID: 11
            STATE: ACTIVE_VERSION
             TYPE: IMAGE
          HL_NAME:
  \TSMIMAGE-WINNT\\\TSM_TEMP_GROUP_LEADER10/21/2014 09 00:00\
          LL_NAME: FULL
        OBJECT_ID: 12962817
      BACKUP_DATE: 2014-10-21 09:00:06.000000
  DEACTIVATE_DATE:
            OWNER:
       CLASS_NAME: DEFAULT
  
        NODE_NAME: NODE1
   FILESPACE_NAME: \\NODE1\d$
     FILESPACE_ID: 11
            STATE: ACTIVE_VERSION
             TYPE: IMAGE
          HL_NAME: \TSMIMAGE-WINNT\
          LL_NAME: FULL
        OBJECT_ID: 12962820
      BACKUP_DATE: 2014-10-21 09:11:55.000000
  DEACTIVATE_DATE:
            OWNER:
       CLASS_NAME: DEFAULT
  
        NODE_NAME: NODE1
   FILESPACE_NAME: \\NODE1\d$
     FILESPACE_ID: 11
            STATE: INACTIVE_VERSION
             TYPE: IMAGE
          HL_NAME: \TSMIMAGE-WINNT\
          LL_NAME: FULL
        OBJECT_ID: 12961839
      BACKUP_DATE: 2014-10-16 13:16:15.000000
  DEACTIVATE_DATE: 2014-10-16 15:30:25.000000
            OWNER:
       CLASS_NAME: DEFAULT
  
        NODE_NAME: NODE1
   FILESPACE_NAME: \\NODE1\d$
     FILESPACE_ID: 11
            STATE: INACTIVE_VERSION
             TYPE: IMAGE
          HL_NAME: \TSMIMAGE-WINNT\
          LL_NAME: FULL
        OBJECT_ID: 12961845
      BACKUP_DATE: 2014-10-16 15:30:25.000000
  DEACTIVATE_DATE: 2014-10-21 09:11:55.000000
            OWNER:
       CLASS_NAME: DEFAULT
  
  
  Note that this example shows two active temporary objects along
  with the active and inactive real objects existing on the
  server. Each of the two backups were interrupted while running
  and this caused a new temporary object for the backup to be
  created when the backup was restarted. Once a running backup
  finishes, the HL name will change to reflect that it is no
  longer temporary. The backup from 10/16/2014 has correctly
  changed to inactive when the new active backup was taken on
  10/21/2014, however the old temporary objects were not removed
  or marked as inactive so that they can expire.
  
  Tivoli Storage Manager Versions Affected:
  6.2,6.3,6.4,7.1
  
  
  Initial Impact: (high/med/low)
  Low
  
  Additional Keywords:
  interrupt, automatic, delete, remove, temp
  

Local fix

• Manually remove the objects from the server using the delete
  object command. Once the objects have been identified with the
  select command above, the object id number from the output can
  be used to remove the objects from the server.
  
  example,
  delete object 12962817
  
  Warning: Be aware that the delete onbject command directly
  changes the database. Providing the wrong object number with
  this command will permanently remove that object from the server
  database. Be sure the correct object id is used from the select
  output.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Tivoli Storage Manager versions 6.4 and 7.1 running on all   *
  * platforms                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * This issue is projected to be fixed in the Tivoli Storage    *
  * Manager Client on all platforms in 7.1.4 version.            *
  ****************************************************************
  *
  

Problem conclusion

• After the fix TSM client will be able to delete all temporary
  active objects.
  

Temporary fix

Comments

APAR Information

• 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

• R71W PSY

     UP

• R71S PSY

     UP

• R71L PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP