media server logo
Product user guide

Storages

Connect an S3-compatible or Backblaze destination and prove that Callaba can write and read media before production recording begins.

Find it in CallabaQuick start → Storages
What this module does

A storage record is the reusable destination for files and recordings. Test credentials with a small object first; a saved form does not prove bucket access.

Before you start

  • A bucket created in the intended region.

  • Credentials limited to the required bucket and object operations.

  • A retention and lifecycle policy owned by your organization.

Settings explained

These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.

Connection

Identify the external object store.

Storage name

A clear operator label such as Archive EU or VOD Primary.

Storage type

Choose the S3-compatible or Backblaze connection expected by the bucket.

Bucket or endpoint

The bucket address used by this storage connection.

Access key

Credential identifier permitted to access the bucket.

Secret key

Write-only secret paired with the access key.

Never place it in screenshots or support messages.

Optional metadata

External metadata storage for workflows that require it.

Metadata database URL

Optional Redis-compatible URL used by supported metadata workflows.

Leave it empty unless the workflow explicitly requires it.

Safe first workflow

  1. 01

    Create a storage record with an operator-friendly name and the correct provider type.

  2. 02

    Enter the bucket endpoint and least-privilege credentials.

  3. 03

    Save the storage, then copy a small non-sensitive test file into it from File manager.

  4. 04

    Confirm the object exists in the bucket and can be read through the expected workflow.

Workflow examples

Use this when

Send live recordings to external retention

Local disk should not own the only copy of a live program.

Live sourceSRT / RTMP / WebRTC
RecordingSegment or finalize
File managerVerify asset
Object storageRetention copy
Animated workflow diagram: Send live recordings to external retention

How to build it

  1. 1

    Connect and test the destination storage with a small file.

  2. 2

    Create the recording using the required output and segmentation policy.

  3. 3

    Verify the finalized file in File manager before copying it.

  4. 4

    Copy the asset to the tested storage and monitor copy progress to completion.

Verify the result

  • A test copy reaches the intended bucket and can be read back.
  • The storage list identifies the correct provider and operator label.
  • Failed credentials do not expose their secret value in the UI.

Troubleshooting

A storage saves but copy fails

Check
  • Check bucket endpoint and region.
  • Verify object write permission and credential validity.
Then do this

Correct the bucket policy or credentials and repeat with the same small test file.