Yes,

object_storage_request_timeout_ms

is related to operations involving object storage (like AWS S3, Google GCS, or MinIO), which includes DB Backup if you are using object storage as your backup repository. However, its role is specific and should be distinguished from other backup-related timeout parameters: 1. What

object_storage_request_timeout_ms

does: * Function: It controls the timeout duration for establishing HTTP connections and sending/receiving requests via the object storage SDK. * Scope: It is a Backend (BE) configuration parameter. It was introduced in v3.0.9 and is primarily used when the BE interacts directly with object storage (e.g., in shared-data architecture or when using broker-less storage access). * Default:

-1

(uses the default timeout of the underlying SDK). * Relevance to Backup: If your

BACKUP

or

RESTORE

jobs fail due to network-level HTTP timeouts (e.g., "Timeout was reached" or "curlCode: 28"), increasing this value can help. 2. Other parameters related to DB Backup: If you are troubleshooting a backup timeout, you should also consider these parameters which are more directly tied to the backup process: *

broker_write_timeout_seconds

(BE Config): This is the most direct BE parameter for backup data transfer. It is explicitly documented to affect snapshot upload/download (the core of the backup/restore process). It defaults to 30 seconds. *

backup_job_default_timeout_ms

(FE Config): This controls the overall time allowed for a backup job to complete. If the job takes longer than this (default is 24 hours), the FE will mark it as failed. *

timeout

property (SQL syntax): When you run the

BACKUP

command, you can specify a

timeout

in the

PROPERTIES

(e.g.,

PROPERTIES ("timeout" = "3600")

) to override the default for that specific job. Summary While

object_storage_request_timeout_ms

is related (it affects the low-level connection to S3/GCS), it is generally considered a "Query Engine" or "Storage" parameter. For most backup timeout issues, you should first check the

timeout

property in your

BACKUP

command or the

broker_write_timeout_seconds

on the BE. References • sql-reference/sql-statements/backup_restore/CREATE_REPOSITORY.md • loading/s3.md • administration/management/BE_configuration.md • quick_start/shared-data.md • faq/shared_data_faq.md • faq/loading/Routine_load_faq.md