Files
BackupX/docs-site/docs/features/storage-backends.md
Wu Qing 00151e466c feat: 解决 CDC 去重、集中备份与首次初始化问题 (#105)
实现 CDC 内容寻址仓库、远程 Agent 中央中转备份与首次初始化体验,并补充安全校验、测试及双语文档。

Closes #94
Closes #101
Closes #104
2026-08-07 23:01:29 +08:00

1.9 KiB

sidebar_position, title, description
sidebar_position title description
2 Storage Backends 70+ storage backends — built-in cloud providers plus any rclone backend.

Storage Backends

BackupX aims to accept any place you'd want to drop a backup file.

Built-in providers

Type Required fields
Alibaba OSS Region + AccessKey ID/Secret + Bucket (endpoint auto-assembled)
Tencent COS Region + SecretId/SecretKey + Bucket (format name-appid)
Qiniu Kodo Region + AccessKey/SecretKey + Bucket
S3-compatible Endpoint + AccessKey + Bucket
Google Drive Client ID/Secret + OAuth authorization
WebDAV URL + username/password
FTP / FTPS Host + port + username/password
Local disk Target directory (absolute path) + optional Master relay for remote Agents

New local-disk targets enable Relay remote backups through Master by default. This makes the configured path belong to the Master, so a storage server mounted there can collect backups from many source Agents. Turn the switch off when the path intentionally belongs to each Agent. Existing targets retain their previous Agent-local behavior until explicitly changed.

Rclone backends

Every rclone backend is exposed as a first-class storage type — SFTP, Azure Blob, Dropbox, OneDrive, Backblaze B2, Wasabi, pCloud, HDFS, and many more.

  • The form groups fields into required and advanced (advanced collapsed by default)
  • Validation and connection tests reuse rclone's built-in probe

Multiple targets per task

A backup task can fan out to multiple targets in parallel. All targets receive the same artifact; a per-target status is recorded:

  • Success: storage path + size
  • Failed: error message

If any target fails after retries, the record status is failed but successful targets are preserved (no rollback).