APAR status
Closed as program error.
Error description
Error Description: After Disaster Recovery of SPP appliance and vSnap, restore points in Spectrum Protect repository server are not seen The following steps will produce the problem: 1) Backed up a Vm and the SPP catalog to the vsnap 2) Copy this data to the Spectrum Protect repository server 3) Verified in the Spp appliance UI that catalog and Vm restore points are available 4) To simulate a Disaster Recovery scenario, turn off or delete the Spp appliance and vsnap 5) Install and configure new SPP appliance and vSnap, register the new vSnap server into SPP, and register the same Spectrum Protect repository server previously used in step 2. The problem occurs because the bucket added to the Vsnap is incorrectly added as an Archive partner rather than an Offload bucket. This prevents the catalog/vm from being seen In the Spp appliance UI Spectrm Protect Plus Versions Affected: 10.1.5 Customer/L2 Diagnostics N/A Initial Impact: Medium Additional Keywords: Dr Disaster Recovery Restore Point UI Gui Bucket Archive Partner Offload Local Fix: N/A
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * IBM Spectrum Protect Plus level 10.1.4 and 10.1.5. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in IBM Spectrum Protect Plus level * * 10.1.5.2204 and 10.1.6. Note that this is subject to change * * at the discretion of IBM. * ****************************************************************
Problem conclusion
In a DR scenario when a brand new SPP and vSnap are set up and then an existing SP repository server is registered, SPP attempts to discover the existing filespaces (buckets) and use them. The goal is to allow users to browse the catalog backups present in the existing buckets so that the SPP catalog can be restored. Due to errors in the discovery logic, SPP could not distinguish between offload and archive buckets. SPP often detected existing offload buckets but assumed they were archive buckets. As a result, the offloaded catalog restore points could not be found. The problem has been resolved by improving the bucket discovery logic. When an SP server is registered, SPP first looks for existing buckets and examines their contents to determine whether it has previously been used for offload or archive. If an existing offload bucket is found, it is used, otherwise a new one is created. Similarly, if an existing archive bucket is found, it is used, otherwise a new one is created
Temporary fix
Comments
APAR Information
APAR number
IT32452
Reported component name
SP PLUS
Reported component ID
5737SPLUS
Reported release
A15
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-04-05
Closed date
2020-04-09
Last modified date
2020-04-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
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":"A15","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
31 January 2024