Direct links to fixes
8.1.15.100-IBM-SPSRV-WindowsX64
8.1.15.100-IBM-SPSRV-Linuxx86_64
8.1.15.100-IBM-SPSRV-Linuxs390x
8.1.15.100-IBM-SPSRV-Linuxppc64le
8.1.15.100-IBM-SPSRV-AIX
8.1.16.000-IBM-SPCMS-WindowsX64
8.1.16.000-IBM-SPCMS-WindowsI32
8.1.16.000-IBM-SPCMS-Linuxx86_64
8.1.16.000-IBM-SPOC-WindowsX64
8.1.16.000-IBM-SPOC-Linuxx86_64
8.1.16.000-IBM-SPOC-Linuxs390x
8.1.16.000-IBM-SPOC-LinuxPPC64le
8.1.16.000-IBM-SPOC-AIX
8.1.16.000-IBM-SPSRV-WindowsX64
8.1.16.000-IBM-SPSRV-Linuxx86_64
8.1.16.000-IBM-SPSRV-Linuxs390x
8.1.16.000-IBM-SPSRV-Linuxppc64le
8.1.16.000-IBM-SPSRV-AIX
APAR status
Closed as program error.
Error description
On IBM Spectrum Protect 8.1.15, when using MOVE CONTAINER on a cloud container in a storage pool with cloud data lock enabled, the new container will not have a cloud lock expiration date recorded for the new container. This will lead to the data lock eventually expiring and not being extended if there are valid extents remaining in the container. Customer/L2 Diagnostics: After using MOVE CONTAINER, viewing the Cloud Lock Expiration field of QUERY CONTAINER will show no date in the column. If the Cloud Data Lock is enabled for the storage pool there should be a date recorded in this field. IBM Spectrum Protect Versions Affected: 8.1.15 Initial Impact: MOVE CONTAINER will create a new container and when that container is sent to the object storage it will be uploaded with a lock expiration date. However, since that date is not recorded in the database, IBM Spectrum Protect will not continue to increase the lock date if there are still valid extents remaining in the container. This will lead to the container eventually becoming unlocked. When a container is not protected by the lock on the object storage, the object could be modified or deleted by a third party. Additional Keywords: Cloud Data Lock, AWS Object Lock, MOVE CONTAINER
Local fix
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 levels 8.1.15.100 and 8.1.16. Note * * that this is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Affected platforms for reported release: AIX, Linux, and Windows. Platforms fixed: AIX, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT41717
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
81L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-08-08
Closed date
2022-08-09
Last modified date
2022-08-09
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
Document Information
Modified date:
01 November 2022