A fix is available
APAR status
Closed as program error.
Error description
CUSTOMER/L2 DIAGNOSTICS: In this section "target server" means the following: 1. The first target server in a configuration where data is protected, by using the PROTECT STGPOOL command, from a target server to a second target server. 2. The target server that is specified by the PROTECT STGPOOL command in a configuration where data is protected, by using the PROTECT STGPOOL command, from a target server to a container-copy storage pool. To determine whether skipped data extents exist in your server environment, complete the following steps: 1. From the first target server, issue the following command to identify the pool ID that must be checked for skipped data extents:db2 "select poolid from tsmdb1.ss_pools where poolname=upper('Pool1')" 2. Then, use the pool ID that is displayed in the output of step 1 and issue the following command: db2 "select 1 from tsmdb1.sd_non_dedup_locations where poolid=<poolID> and refcount>1 for read only with ur" If the number 1 is displayed in the output of step 2, the REPAIR STGPOOL command is not repairing all of the data extents. Any other result indicates that data extents are repaired. INITIAL IMPACT: The PROTECT STGPOOL command might not protect all data extents in the following circumstances: 1. When you issue the REPLICATE NODE command and the PROTECT STGPOOL command from a source server to a target server, and then issue only the PROTECT STGPOOL command from that target server to another target server. In this instance, data extents on the target server might not be protected to the second target server. 2. When you issue the REPLICATE NODE command and the PROTECT STGPOOL command from a source server to a target server, and then issue the PROTECT STGPOOL command from that target server to a local container-copy storage pool. In this instance, data extents on the target server might not be protected to the container-copy storage pool. No error message is displayed until you attempt to restore the damaged objects. Then, ANR0548W error message is displayed on the server, or the ANS4035W error message is displayed on the client. RECOMMENDATION: If you use the PROTECT STGPOOL command from a target server to another target server, you must also use the REPLICATE NODE command to protect all data extents to the second target server until the fixing level is applied. If you use the PROTECT STGPOOL command from a target server to a container-copy storage pool, there is no workaround available. Apply the fixing level when available.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Tivoli Storage Manager and IBM Spectrum Protect server * * users of REPLICATE NODE and PROTECT STGPOOL commands that * * use a second target server or a container-copy storage pool * * on a target server. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
This problem is projected to be resolved in IBM Spectrum Protect server levels 7.1.7.200, 7.1.8, and 8.1.2. This is subject to change at the discretion of IBM.
Temporary fix
Comments
APAR Information
APAR number
IT20527
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-09
Closed date
2017-05-09
Last modified date
2017-05-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
[{"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":"7.1.3"}]
Document Information
Modified date:
13 February 2021