Skip to main content
Cloudstic supports multiple storage backends for maximum flexibility. All backends support encryption, compression, and content-addressed deduplication.

​
Available Backends

Local Storage

Store backups on the local filesystem

Amazon S3

S3-compatible storage (AWS, R2, MinIO)

Backblaze B2

Cost-effective cloud storage

SFTP

Remote storage over SSH

​
Choosing a Backend

​
Local Storage

Best for:
  • Local backups to external drives
  • Fast network-attached storage (NAS)
  • Testing and development

​
S3-Compatible

Best for:
  • AWS S3 for scalable cloud storage
  • Cloudflare R2 for zero-egress costs
  • MinIO for self-hosted S3 compatibility

​
Backblaze B2

Best for:
  • Cost-effective cloud storage
  • Long-term archival with low storage costs
  • Predictable pricing

​
SFTP

Best for:
  • Existing SSH-accessible servers
  • Remote Linux/Unix systems
  • Simple remote backup without cloud setup

​
Common Features

All storage backends support:
  • Encryption: AES-256-GCM with key derivation
  • Compression: Automatic zstd compression
  • Deduplication: Content-addressed storage
  • Packfiles: Bundle small objects to reduce API calls
  • Atomic writes: Temporary files with atomic rename

​
Configuration

Storage backends are configured via:
  1. Command-line flags (e.g., -store local -store-path /backup)
  2. Environment variables (e.g., CLOUDSTIC_STORE=local)
  3. Per-backend credentials (e.g., B2_KEY_ID, AWS_ACCESS_KEY_ID)
Environment variables are particularly useful for automation and CI/CD pipelines.

​
Backend Selection

Specify the storage backend with the -store flag: 
cloudstic init -store local -store-path ./backup_store
cloudstic init -store s3 -store-path my-bucket
cloudstic init -store b2 -store-path my-bucket
cloudstic init -store sftp -store-path /remote/backup

​
Next Steps

Local Storage

Set up local filesystem storage

S3 Storage

Configure S3-compatible storage

B2 Storage

Set up Backblaze B2

SFTP Storage

Configure SFTP storage