mirror of
https://github.com/Awuqing/BackupX.git
synced 2026-08-28 19:47:27 +08:00
Awuqing
cc50637b4b
为 Master 本地磁盘增加可选流式中转，远程 Agent 可直接把产物写入中央存储并通过反向通道恢复。 持久化并校验传输模式，兼容既有 Agent 本机磁盘目标，补齐鉴权、完整性、配额、访问保护、前端配置及双向链路测试。 Closes #101
41 lines
1.9 KiB
Markdown
41 lines
1.9 KiB
Markdown
---
|
|
sidebar_position: 2
|
|
title: Storage Backends
|
|
description: 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](https://rclone.org/overview/) 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).
|