Skip to content

Configure Filestore

Filestore is the abstraction UnifiedBX uses for storage destinations — used by Backup, recordings export, and module log shipping. Configure once, then reference in other modules.

Steps

Add a Local Filestore

For backups stored on the same host:

  1. Go to System Admin → Filestore.
  2. + Add Instance → Local.
  3. Fill in:
    • Name — e.g. Local Backups.
    • Path — /var/spool/asterisk/backup/ (default backup path).
  4. Submit.

Add an SSH/SCP Filestore

For pushing backups to another server:

  1. + Add Instance → SSH.
  2. Fill in:
    • Name — e.g. Offsite Backup.
    • Hostname — destination server.
    • Port — 22.
    • Username — backup user on the destination.
    • Authentication — Password or Key. Key is more secure; paste private key.
    • Path — destination directory, e.g. /backups/unifiedbx/.
  3. Submit.

Add an FTP Filestore

  1. + Add Instance → FTP.
  2. Fill in: hostname, port (21), username, password, path.
  3. Submit.

Add an S3 Filestore

For AWS S3 or S3-compatible (MinIO, Wasabi, Backblaze B2 with API):

  1. + Add Instance → S3 (or Amazon S3).
  2. Fill in:
    • Access Key / Secret Key.
    • Region — e.g. us-east-1.
    • Bucket — pre-created bucket name.
    • Path Prefix — folder within bucket.
  3. Submit.

Use a Filestore in Backup

Once a Filestore is configured, it appears in System Admin → Backup & Restore → Backup template → Storage Locations dropdown. Add the Filestore as a destination.

Verify

After configuring an SSH/FTP/S3 Filestore:

  1. Run a small test backup that targets only this Filestore.
  2. Check the destination — backup file should appear.

Common Issues

  • SSH Filestore fails: "permission denied." Wrong username, wrong key, or destination directory not writable.
  • S3 Filestore fails: "AccessDenied." IAM user lacks PutObject on the bucket. Update IAM policy.
  • FTP Filestore: "passive mode required." Some FTP servers need passive; set in advanced options.
  • Local Filestore: "permission denied." /var/spool/asterisk/backup/ not owned by asterisk: chown -R asterisk:asterisk /var/spool/asterisk/backup.
  • Backup uses old path. Backup template still pointing at the old Filestore. Update the backup template's Storage Locations.