1
Remote Storage
Jonathan Miller edited this page 2026-06-02 19:02:26 -05:00

Remote Storage

MokoJoomBackup can upload backup archives to remote storage after creation. Configured per-profile in the Remote Storage tab.

Storage Options

Option Description
None (local only) Keep backups on the local server
FTP / FTPS Upload to an FTP server
Google Drive Upload to Google Drive
Amazon S3 / S3-Compatible Upload to S3, Wasabi, Backblaze B2, MinIO

Keep Local Copy

Keep Local Copy toggle:

  • Yes (default): Both local and remote copies exist
  • No: Local copy deleted after successful upload. If upload fails, local copy is preserved.

FTP / FTPS

Field Description
FTP Host Server hostname or IP
FTP Port Default: 21
FTP Username Login username
FTP Password Login password
Remote Path Directory on FTP server
Passive Mode Recommended for firewalls
Use FTPS (SSL) FTP over SSL/TLS

Features: recursive directory creation, post-upload size verification, passive mode, FTPS support.


Google Drive

Field Description
Google Client ID OAuth 2.0 Client ID
Google Client Secret OAuth 2.0 Client Secret
Refresh Token Offline refresh token
Drive Folder ID Target folder ID from URL

Features: OAuth2 with refresh token, resumable upload with 5 MB chunks, no SDK dependency.

Setup Steps

  1. Create project in Google Cloud Console
  2. Enable Google Drive API
  3. Create OAuth 2.0 Client ID
  4. Get refresh token via OAuth2 Playground

Amazon S3 / S3-Compatible

Field Description
S3 Endpoint Blank for AWS; custom URL for Wasabi/MinIO/B2
Region e.g. us-east-1
Access Key IAM access key
Secret Key IAM secret key
Bucket S3 bucket name
Path Prefix e.g. /backups/mysite

Features: AWS Signature V4, single PUT for files <= 100 MB, multipart upload (10 MB parts) for larger files, automatic abort on failure.

Compatible Services

  • AWS S3 — leave endpoint blank
  • Wasabi — endpoint: https://s3.wasabisys.com
  • Backblaze B2 — endpoint: https://s3.us-west-001.backblazeb2.com
  • MinIO — your MinIO server URL