bucket consistency level (CL) with read-after-new-write Various errors reported in Commvault logs such as: The destination encountered an error while processing the data from the source. SendRequest()...bucket consistency level (CL) with read-after-new-write Various errors reported in Commvault logs such as: The destination encountered an error while processing the data from the source. SendRequest() - Error: Message: We encountered an internal error. [PIPELAYER ] Error in flushing the current buffer. [Reader_5] Failed to write the data to the pipeline [Reader_5] Cannot process data for the chunk. [Cloud] There is an internal error Error occurred while processing chunk
Available (eventual consistency for HEAD operations) Behaves the same as the Read-after-new-write consistency level, but only provides eventual consistency for HEAD operations. Note: From 11.5.0.3, no...Available (eventual consistency for HEAD operations) Behaves the same as the Read-after-new-write consistency level, but only provides eventual consistency for HEAD operations. Note: From 11.5.0.3, non-existent GET matches to HEAD to return 404 when bucket consistency is set to Available Behaves the same as the Read-after-new-write consistency level, but provides eventual consistency for HEAD and GET operations.