APAR status
Closed as program error.
Error description
IBM Spectrum Protect Plus vSnap replication can fail to replicat e with the following errors in the SLA job log: GET request for "https://mymachine:8900/api/snapshot?name= spp_1004_2125_37" resulted in 404 (NOT FOUND); invoking error ha ndler Storage snapshot with id : spp_1004_2125_37 not found null Replication Failed (Unable to replicate volume) On the second replication attempt, it will fail with: Replication Failed (Failed to start Storage Replication Failed to get Storage replication sessions on the Server myserver.com replication Session id b549c0753d11a1134ed926ab9471ace6 message :"Snapshot 37 has already been synced for this relations hip"type :"SnapshotAlreadySyncedError") The vsnap.log will contain messages similar to the following: vsnap.common.errors.SnapshotNotFoundError: Snapshot 39 not found vsnap.api API request failed with internal server error vsnap.api API request started: GET /snapshot?name= spp_1004_2125_37 | Body: Nonevsnap.common.util Authorized user: vsnap vsnap.config Cannot find DB entry for snapshot named spp_1004_2125_37vsnap.api Traceback (most recent call last): File "/opt/vsnap/lib/flask/app.py", line 1612, in full_dispatch_ requestl rv = self.dispatch_request() File "/opt/vsnap/lib/flask/app.py", line 1598, in dispatch_reque st return self.view_functions[rule.endpoint](**req.view_args) File "/src/workspace/vsnap/api/rest.py", line 70, in decorated File "/src/workspace/vsnap/api/rest.py", line 542, in api_snapshot_get_allFile "/src/workspace/vsnap/core.py", line 1 023, in snapshot_get File "/src/workspace/vsnap/config.py", line 954, in get_snapshot_by_name vsnap.common.errors. SnapshotNotFoundError: Snapshot spp_1004_2125_37 not found vsnap.api API request failed with internal server error vsnap.api API request started: GET /volume/3/snapshot? | Body: N one
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * IBM Spectrum Protect Plus levels 10.1.1.* * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in level 10.1.1 patch 1. Note that * * this is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
vSnap replication status was being set as "completed" before some post-sync cleanup tasks were done, and if a second sync request came in during that narrow window (few seconds), it can result in that second snapshot "disappearing" from the replica server. A fix on vSnap build was done to ensure that status is set to "completed" only after the post-sync tasks are completed.
Temporary fix
Comments
APAR Information
APAR number
IT25167
Reported component name
SP PLUS
Reported component ID
5737SPLUS
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-25
Closed date
2018-05-25
Last modified date
2018-05-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
VSNAP
Fix information
Fixed component name
SP PLUS
Fixed component ID
5737SPLUS
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
30 January 2024