IT17591: "DELETE VOLHIST" WITH TYPE=DBB WILL DELETE A FULL DB BACKUP EVEN IF THE INCREMENTALS DEPENDENT ON IT CANNOT BE DELETED

8.1.1.000-IBM-SPSRV-Linuxx86_64
8.1.1.000-IBM-SPSRV-AIX
8.1.1.000-IBM-SPSRV-Linuxs390x
8.1.1.000-IBM-SPSRV-WindowsX64
8.1.1.100-IBM-SPOC-AIX
8.1.1.100-IBM-SPOC-Linuxs390x
8.1.1.100-IBM-SPOC-Linuxx86_64
8.1.1.100-IBM-SPOC-WindowsX64
7.1.8.000-TIV-TSMSRV-AIX
7.1.8.000-TIV-TSMSRV-HP-UX
7.1.8.000-TIV-TSMSRV-Linuxppc64
7.1.8.000-TIV-TSMSRV-Linuxs390x
7.1.8.000-TIV-TSMSRV-Linuxx86_64
7.1.8.000-TIV-TSMSRV-SolarisSPARC
7.1.8.000-TIV-TSMSRV-WIN
7.1.8.000-TIV-TSMOC-AIX
7.1.8.000-TIV-TSMOC-Linuxx64
7.1.8.000-TIV-TSMOC-Windows
7.1.8.000-TIV-TSMOC-LinuxPPC64
7.1.8.000-TIV-TSMOC-LinuxPPC64le
7.1.8.000-TIV-TSMOC-LinuxS390
IBM Spectrum Protect Server V8.1 Fix Pack 1 (V8.1.1) Downloads

APAR status

• Closed as program error.

Error description

• Currently, if incremental database backups are taken on
  different days to the full backup db that they
  depend on, they will not be deleted when only the full can be
  deleted.
  
  For example:
   q volhist type=dbb
  
  10/06/16   11:00:17      BACKUPFULL              8             0
  1,001
  10/06/16   11:00:17      BACKUPFULL              8             0
  100,00
  10/12/16   04:07:52      BACKUPINCR              8             1
  100,00
  10/12/16   04:09:55      BACKUPFULL              9             0
  100,00
  
  
  So there is a full backup db taken on 6th October 2016
  and an incremental backup db taken on 12th October 2016
  dependent on the full
  backup from the 6th.
  
  Running "delete volhist type=dbb" on the 12th October, for
  entries older than 8th October, results in 2 entries being
  deleted
  for the full backup:
  
  10/12/16   04:22:51      ANR2017I Administrator ADMIN issued
  command:
  DELETE VOLHISTORY type=dbb todate=today-4
  10/12/16   04:22:52      ANR2467I DELETE VOLHISTORY:
  2 sequential volume history entries were successfully deleted.
  
  
  So from "q volhist type=dbb", it can be seen that only the full
  db backup entries were deleted
  and the incremental backup is left behind, with no associated
  full backup.
  
  10/12/16   04:07:52      BACKUPINCR              8             1
  100,00
  10/12/16   04:09:55      BACKUPFULL              9             0
  100,00
  
  
  
  Tivoli Storage Manager versions affected:
  Server 6.3.x and 7.1.x on supported platforms
  
  
  
  
  Initial Impact: Low
  
  Additional Keywords:  TSM IBM Spectrum Protect delete volhist
  database backups incremental
  

Local fix

• Do not delete a full db backup until able to delete the
  last incremental db backup in the sequence.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.1. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms for reported release:  AIX, HP-UX, Solaris,
  Linux, and Windows.
  Platforms fixed:  AIX, Linux, and Windows.
  

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:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels