IT42868: CLOUD OR REPOSITORY COPY MAY FAIL WITH ERROR: READTIMEOUT: HTTPCONNECTIONPOOL

APAR status

• Closed as program error.

Error description

• During copy data to any cloud providers or repository server
  with
  a throttled connection or that the slowdown occurred, the IBM
  Spectrum Protect Plus can hit timeouts,resulting in the failure
  of the copy.
  
  
  In the job log the failure seen is the "ReadTimeout" error for
  localhost port 8901, as follows:
  
  
  ERROR,<TimeStamp>,CTGGA0309,Copy failed for snapshot (ID: 1392)
  
  from source [server: <vsnap_name>  volume: <volume_name>
  snapshot: <snapshot_name> to target [server:
  https://core.windows.net:443  Error: ReadTimeout:
  HTTPConnectionPool(host='localhost'  port=8901): Read timed out.
  
  (read timeout=1800)
  
  
  
  The repl.log corresponding shows the following error:
  
  
  WARNING vsnap.cloud.mover Timed out with <amount> objects still
  
  present in objects dir, will proceed with the offload
  
  
  
  IBM Spectrum Protect Plus Versions Affected:
  
  IBM Spectrum Protect Plus 10.1.3 and later
  
  
  Additional Keywords: SPP, SPPLUS,TS010558580
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.3 to 10.1.13           *
  ****************************************************************
  * 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.13.1 and 10.1.14. Note that this is subject to change   *
  * at the discretion of IBM.                                    *
  ****************************************************************
  

Problem conclusion

• The issue occurred because the vSnap cloud copy process did not
  wait long enough in the final stage of the process for the
  remaining cached data to be uploaded to the cloud. The problem
  has been resolved by implementing a code fix to use a larger
  timeout in the final stage. The timeout is also configurable via
  existing vSnap CLI preferences named cloudStallCount and
  cloudStallInterval which are used to control how long a cloud
  copy operation can wait before it is considered as stalled.
  

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:

Modules/Macros

• vSnap
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels