Direct links to fixes
8.1.9.000-IBM-SPSRV-WindowsX64
8.1.9.000-IBM-SPSRV-Linuxx86_64
8.1.9.000-IBM-SPOC-WindowsX64
8.1.9.000-IBM-SPCMS-WindowsX64
8.1.9.000-IBM-SPSRV-Linuxs390x
8.1.9.000-IBM-SPCMS-WindowsI32
8.1.9.000-IBM-SPOC-Linuxx86_64
8.1.9.000-IBM-SPCMS-Linuxx86_64
8.1.9.000-IBM-SPSRV-Linuxppc64le
8.1.9.000-IBM-SPOC-Linuxs390x
8.1.9.000-IBM-SPOC-LinuxPPC64le
8.1.9.000-IBM-SPSRV-AIX
8.1.9.000-IBM-SPOC-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 8 (V8.1.9) Downloads
APAR status
Closed as program error.
Error description
The Spectrum Protect server may incorrectly show multiple active versions when a client restore is performed. This symptom can occur when all of the following conditions are true: - Client restore is run from a replication target server - The replication target server uses dissimilar policies - The data being restored is part of a logical file group Note: Some IBM Spectrum Protect clients store data on the server using a logical file grouping protocol that relates several individual objects together. Each logical group has a group leader. If the group leader is deleted, the group is deleted. You cannot delete a member that is part of a group. Expiration of all members in a group is dependent on the group leader. For example, if a member is marked for expiration, the member does not expire unless the group leader expires. However, if a member is not marked for expiration, and the group leader is expired, then all members are expired. This grouping is commonly used with Windows system state backups and IBM Spectrum Protect for Virtual Environments. IBM Spectrum Protect Versions Affected: Tivoli Storage Manager and IBM Spectrum Protect server version 7.1.1 and higher Initial Impact: Medium Keywords: TSM SET DISSIMILARPOLICIES Query REPLServer Dissimilar Policies:
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 level 8.1.9. Note that this is * * subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
The problem was fixed. Affected platforms: AIX, Linux, and Windows. A new command will detect and fix objects for which there is more than 1 active version. The command syntax is: >>--REPAir OBJECTVersions-------------------------------------------------- --> >----node_name-------------------------------------------------- -------------> .-*--------------. >--+----------------+------------------------------------------- -------------> `-filespace_name-' .-NAMEType--=--SERVER------. >--+--------------------------+--------------------------------- -------------> `-NAMEType--=--+-SERVER--+-' +-UNIcode-+ '-FSID----' .-Wait--=--No------. >--+------------------+----------------------------------------- -------------> `-Wait--=--+-No--+-' '-Yes-' This command will start a background (wait=no) or foreground (wait=yes) process to perform the repair. While the process is running, a QUERY PROCESS command will reports results such as this: Process Process Description Process Status Number -------- -------------------- ------------------------------------------------- 1 REPAIR OBJECTVERSIO- Processed 1 file spaces out of 2. Repaired 2 NS objects. Elapsed time: 0 Days, 0 Hours, 3 Minutes. Only one REPAIR OBJECTVERSIONS may be run at a time. If you attempt to run a REPAIR OBJECTVERSIONS is already running, the following message will be issued: ANR4303E 'Command': The command was not processed because an operation to repair object versions is already running. Explanation: You cannot run two instances of the REPAIR OBJECTVERSIONS command simultaneously. SystemAction: System operations continue, but the server does not process the command. UserResponse: Wait for the operation to repair object versions to finish, or cancel the operation. Then, reissue the REPAIR OBJECTVERSIONS command.
Temporary fix
Comments
APAR Information
APAR number
IT25325
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-06-11
Closed date
2019-06-10
Last modified date
2019-06-10
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