APAR status
Closed as documentation error.
Error description
The Spectrum Protect server REPLICATE NODE functionality requires expiration processing on the target replication server to process expired data replicated from the source server. Documentation regarding this requirement is conflicting. The first link below indicates that expiration processing is required, while the second contradicts this, and says this is not required. https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.1/com. ibm.itsm.srv.doc/c_repl.html >>>>> If Tivoli Storage Manager, Version 7.1.1 or later, is installed on the source and target servers, client node data is marked for deletion during replication processing but it is not deleted until expiration processing runs on the target server. Tip To ensure that you have available storage, delete client node data by regularly running file expiration processing. <<<<< https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm .itsm.srv.doc/c_repl_policy.html >>>>> Expiration processing on the target replication server is disabled for replicated data. The file on the target replication server is deleted by the source replication server after the file is expired and deleted on the source. <<<<< Knowledge Center documentation will be updated to clearly explain that expiration processing is required on both the source and target servers. Spectrum Protect Versions affected: IBM Spectrum Protect server 7.1 or higher on all platforms Additional Keywords: TS002333430; server; expire inventory; replication; bloat Customer/Support Diagnostics (If Applicable) Ensure that EXPIRE INVENTORY processes all nodes on the target server to completion. If the target server stores more files or data than expected, and expiration is not running or completing, this APAR applies. Initial Impact: Medium
Local fix
Run "expire inventory" on a replication target server.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Update documentation as needed. * ****************************************************************
Problem conclusion
In IBM Knowledge Center, in the "File expiration and expiration processing" topic, the ?Restrictions on expiration processing? section was updated to specify that expiration processing must run on both the source and target replication servers: "During replication processing, client node data that is deleted from the source replication server is eventually deleted from the target replication server. However, the data that is marked for deletion on the target replication server is not actually deleted until expiration processing runs. On the target replication server, if files are marked as expired, they are deleted when the target replication server runs expiration processing. To help ensure that you have sufficient storage, you must delete client node data by regularly running file expiration processing on both the source and target replication servers."
Temporary fix
Comments
APAR Information
APAR number
IT30093
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71L
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-08-27
Closed date
2019-12-16
Last modified date
2019-12-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
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:
14 February 2021