IT35865: CATALOG RESTORE POINTS RESIDING IN THE CLOUD ARE NOT AVAILABLE FOR RESTORE

APAR status

• Closed as program error.

Error description

• When trying to perform a catalog restore from 'Object Storage'
  or 'Repository Server', the restore points are not available
  for restore.
  Trying a catalog restore from one of these cloud
  destinations, the User Interface takes a long time (> 15
  minutes) to load the list of available restore points.
  When it
  finally loads, it does not display the cloud restore
  points.
  Restore points on vSnap are displayed correctly.
  
  The
  Virgo log will show the following after the restore points
  failed to load:
  
  [<time>] INFO ... VSnap Call POST
  https://<vsnaphostname>:8900/api/partner?partner_type=cloud
  time Taken 896261 ms
  [<time>] INFO ... reason :
  org.springframework.web.client.HttpServerErrorException: 502
  Bad Gateway
  [<time>] INFO ... Status: :: 502
  
  Around the same
  time, the vSnap uwsgi log will show the API call being killed
  because it did not complete for 15 minutes:
  
  <time> - ***
  HARAKIRI ON WORKER 1 (pid: <PID_1>, try: 1) ***
  <time> -
  HARAKIRI !!! worker 1 status !!!
  <time> - HARAKIRI [core 0]
  <spp IP> - POST /api/partner?partner_type=cloud since <EPOCH
  timestamp>
  <time> - HARAKIRI !!! end of worker 1 status
  !!!
  DAMN ! worker 1 (pid: <PID_1>) died, killed by signal 9 :(
  trying respawn ...
  Respawned uWSGI worker 1 (new pid:
  <PID_2>)
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM
  Spectrum Protect Plus 10.1.x
  
  Initial Impact:
  Medium
  
  Additional Keywords: SPP, SPPlus, TS004591653
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.4, 10.1.5, 10.1.6 and  *
  * 10.1.7.                                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the fixing level when available. This problem is       *
  * projected to be fixed in IBM Spectrum Protect Plus level     *
  * 10.1.8. Note that this is subject to change at the           *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• The vSnap API responsible for listing catalog restore points in
  the cloud was inefficient and took too long to respond because
  of stale entries in vSnap?s configuration database. The stale
  entries are associated with old catalog backup volumes
  associated with non-existent SLAs. The problem has been resolved
  by making the API more efficient as well as by ensuring stale
  entries are removed from the configuration database when catalog
  backup SLAs are deleted. As a result of these fixes, the API
  responds in a timely manner and the user interface can correctly
  display the available catalog restore points in the cloud.
  

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

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels