v.25.3Improvement

Backup/restore setting allow_s3_native_copy now supports value three

Official CH changelog text
Backup/restore setting allow_s3_native_copy now supports value three possible values: - False - s3 native copy will not be used; - True (old default) - ClickHouse will try s3 native copy first, if it fails then fallback to the reading+writing approach; - 'auto' (new default) - ClickHouse will compare the source and destination credentials first. If they are same, ClickHouse will try s3 native copy and then may fallback to the reading+writing approach. If they are different, ClickHouse will go directly to the reading+writing approach. #77401 (Vitaly Baranov).
The allow_s3_native_copy backup/restore setting in ClickHouse now supports three possible values: False, True, and 'auto'</> — with 'auto'</> as the new default behavior.

Why it matters

This feature improves the efficiency and reliability of backup and restore operations involving S3 storage by intelligently deciding when to use native S3 copy versus a read-and-write fallback. It reduces unnecessary data transfer by using native S3 copy only when source and destination credentials match, avoiding errors and optimizing performance.

How to use it

To enable or configure this feature, set the allow_s3_native_copy setting in your backup or restore operations to one of the following values:

- False — disables native S3 copy.
- True — attempts native S3 copy first, then falls back on read+write if that fails.
- 'auto' — (new default) compares source and destination S3 credentials to decide whether to use native copy or fallback approach.

Example usage:

SET allow_s3_native_copy = 'auto';

Related resources

PreviousNext