IT42202: AZURECONFLICTHTTPERROR: THE UNCOMMITTED BLOCK COUNT CANNOT EXCEED THE MAXIMUM LIMIT OF 100,000 BLOCKS

APAR status

• Closed as program error.

Error description

• In IBM Spectrum Protect Plus, when an archive job is performed
  and the target is Microsoft Azure cloud storage provider, the
  job can fail with:
  
  ERROR,<timestamp>,CTGGA0309,Copy failed for snapshot (ID: XXX)
  from source <server_volume_snapshot_info> to target
  <server_volume_info>. Error: AzureConflictHttpError: The
  uncommitted block count cannot exceed the maximum limit of 100
  000 blocks. ErrorCode: BlockCountExceedsLimit
  <?xml version="1.0" encoding="utf-8"?><Error><Code>BlockCountEx
  ceedsLimit</Code><Message>Theuncommitted block count cannot exce
  000 blocks.
  
  IBM Spectrum Protect Versions Affected:
  IBM Spectrum Protect Plus 10.1.4 and later
  
  Additional Keywords: SPP, SPPLUS, TS009528750,
  AzureConflictHttpError
  

Local fix

• Change the "archiveObjectSize" preference by running the
  following command on vSnap command line:
  vsnap system pref set --name archiveObjectSize -value
  107374182400
  After modifying the preference, wait 7 days without running any
  archive jobs to allow existing uncommitted blocks to expire
  automatically.
  

Problem summary

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

Problem conclusion

• Implemented a code fix to use a separate smaller value for
  maximum object size for Azure archives, because Azure requires a
  different value from all other cloud provider types.
  

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