I’m evaluating restic at work to backup data to amazon S3. Backup works fine, but restore failed with messages : " read: connection reset by peer" to Amazon S3.
The process finish with a lot of missing files :
Summary: Restored 1807738 / 1812848 files/dirs (148.188 GiB / 148.205 GiB) in 40:13
Fatal: There were 348663 errors
Do you know if there is any way to debug or tune restic ?
Adjust restics retry settings --s3.connections, --s3.max-retries, --s3.retry-delay to enhance network resilience during restores from Amazon S3.
Example
The current list of S3 options according to restic options:
s3.bucket-lookup bucket lookup style: 'auto', 'dns', or 'path'
s3.connections set a limit for the number of concurrent connections (default: 5)
s3.layout use this backend layout (default: auto-detect)
s3.list-objects-v1 use deprecated V1 api for ListObjects calls
s3.region set region
s3.retries set the number of retries attempted
s3.storage-class set S3 storage class (STANDARD, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING or REDUCED_REDUNDANCY)