IT45383: RETENTION SET COPY JOBS SKIP REPLICATED FILESPACES THAT ARE NOT CURRENT

8.1.22.000-IBM-SPSRV-WindowsX64
8.1.22.000-IBM-SPSRV-Linuxx86_64
8.1.22.000-IBM-SPSRV-Linuxs390x
8.1.22.000-IBM-SPSRV-Linuxppc64le
8.1.22.000-IBM-SPSRV-AIX

APAR status

• Closed as program error.

Error description

• Retention set copy jobs do not report that they skip replicated
  filespaces that are not current.
  
  Background:
  
  Prior to V8.1.13, Retention set copy jobs were not permitted on
  target servers. In V8.1.13, the ability to run Retention set
  copy jobs was introduced, but only the most current replicated
  copies can be copied as part of the retention set copy.
  
  As part of the retention set copy processing, a check is
  performed to see whether the replicated data is up to date or
  not. Retention set copy jobs running on a replication target
  server will skip replicated filespaces whose date of last
  replication is before the retention set's point-in-time date.
  
  
  The following observations are noticed:
  	Retset Copy PROCESS will end in a status of INCOMPLETE.
  
  	The RetSet Copy Job will return to status "SLEEPING".
  	The retention state remains "COPYING"
  	Filspaces that are deemed not current are skipped without
  indication in the activity log.
  	Finally, a trace with trace flag RETS shows that replicated
  filespaces are skipped:
  
  20:41:29.084 [181][imret.c][8849][ImUpdateRetSetStats]:Found
  member ###:## retset 81 flags 64 PIT 10/03/2023 14:10:31 size 0
  count 0
  20:41:29.085 [181][imrepl.c][12692][ImReplIsCurrent]:nodeId ###
  fsId ## got last store date 03/02/2022 00:17:43
  20:41:29.085 [181][imrepl.c][12694][ImReplIsCurrent]:nodeId ###
  fsId ## got replica date 03/04/2022 04:09:50
  20:41:29.085 [181][imrepl.c][12707][ImReplIsCurrent]:Replica for
  nodeId ### fsId ## is not current based on lastStoreDate
  03/02/2022 00:17:43
  
  IBM Spectrum Protect / Protect Plus Versions Affected: IBM
  Spectrum Protect Server V8.1.13 and later.
  20:41:29.085 [181][imrepl.c][12719][ImReplIsCurrent]:Replica for
  nodeId ### fsId ## is not current based on backReplSyncDate
  03/04/2022 04:09:50
  20:41:29.085 [181][imret.c][8879][ImUpdateRetSetStats]:Replica
  is not current id 81 member ###:## PIT 10/03/2023 14:10:31 rc 0
  

Local fix

• Rerun Replication to make the filespaces in question current and
  to allow the RetSet Copy Process to complete successfully.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Storage 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.22. Note that this is     *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.  The server will issue new message
  ANR4199I to notify administrators that it is skipping
  out-of-date replicated filespaces during retention set copy
  jobs.
  
  ANR4199I Replicated filespace <filespace name> belonging to node
  <node name>in retention set <retention set id> is not current.
  It will not be copied.
  Explanation:
  The filespace was last replicated before the point-in-time date
  of the retention set, and might not be current.  The retention
  set copy job will skip the filespace until the next time the
  filespace is replicated.
  
  System Action:
  The retention set copy job skips the filespace.
  
  User Response:
  Run replication to make the filespace current. Restart the
  retention set copy job.
  
  Affected platforms:  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