Storage Backends
A profile can push each finished archive to one or more remote destinations, managed per profile in the profile's Remote Destinations panel. Each destination is stored as one row (with its settings as JSON) in #__mokosuitebackup_remotes.
| Backend | Features |
|---|---|
| SFTP | Password or SSH-key auth (paste or upload a key file), configurable port and remote path |
| FTP/FTPS | Passive mode, SSL, recursive dir creation, size verification |
| Google Drive | OAuth2 refresh tokens, resumable upload, no SDK |
| Amazon S3 | AWS Signature V4, multipart upload, custom endpoints |
SFTP, S3 and Google Drive appear in the Add/Edit modal's Type selector; FTP is a fully supported backend used by existing/imported destinations. All uploaders are pure PHP with cURL — no SDK dependencies.
S3-Compatible Services
- AWS S3:
https://s3.amazonaws.com - Wasabi:
https://s3.wasabisys.com - Backblaze B2:
https://s3.us-west-001.backblazeb2.com - MinIO: your server URL
Keep Local Copy
Each destination has a Keep local copy toggle (default on). When off, the local archive is removed once it has uploaded to every enabled remote without any upload failure.
Remote Retention Pruning
RetentionManager is the single retention authority and prunes remote copies as well as the local one. When a record is pruned by age or count it deletes the DB row, unlinks the local archive and its log, and deletes the archive from every currently enabled remote destination for that profile. Remote deletion is idempotent and best-effort — a failure is logged but never blocks local pruning. The shared standalone restore.php is intentionally never pruned from remotes.