OA STORAGE BOX · DOCUMENTATION

Backup & archive operations guide.

Practical guidance for secure access, automated backup transfer, retention, monitoring and restore workflows.

SFTP / FTPSBackup targetRetentionMonitoringRecovery
OA Storage Box interface and backup storage
01 · OVERVIEW

What OA Storage Box is

OA Storage Box is a controlled backup/archive destination for media libraries, managed servers and OACAST workloads. It is designed to keep backup data separate from the live application or broadcast server.

  • Secure transfer workflows such as SFTP / FTPS
  • API-friendly automation where configured
  • Backup and archive retention planning
  • Storage usage and health visibility
  • Restore/recovery workflows
02 · ACCESS

Use dedicated transfer credentials

Access should be provisioned per user, service or workload rather than sharing one master credential across unrelated systems.

Good practice

  • Use strong unique passwords or keys where supported.
  • Keep application/service credentials separate from human user credentials.
  • Restrict users to the folders or areas they need.
  • Remove credentials when a user/service no longer requires access.
03 · BACKUP WORKFLOW

Send data into the Storage Box

Choose the source workload

Server backup, database dump, media library, configuration archive or another approved backup set.

Choose the secure transfer method

Use the SFTP / FTPS / API method supplied for the service.

Automate where practical

Schedule backups from the source system and make failures visible rather than relying on manual copies.

Verify the backup arrived

Check size, timestamp and expected content.

Test recovery

A backup is only useful when the required files can be restored.

04 · RETENTION

Choose a backup lifecycle

Storage retention should match the importance and change rate of the workload.

  • Keep enough recent restore points to recover from common mistakes or corruption.
  • Remove expired backup sets so capacity remains predictable.
  • Preserve special long-term copies separately when a project or policy requires them.
  • Do not confuse backup retention with Vault 42’s fixed broadcast-recording use case.
05 · RECOVERY

Restore a file or backup set

Identify the required date/version

Choose the backup that predates the problem or contains the missing file.

Retrieve to a safe staging location

Avoid overwriting the current live system until the restore content has been checked.

Validate the recovered content

Check archives, database dumps or media files before restoring them into production.

Restore deliberately

Replace only the files/data required or follow the application’s full recovery procedure.

06 · OPERATIONS

Capacity and backup health

Watch both the source backup job and the destination storage.

  • Available capacity and growth rate
  • Last successful backup time
  • Unexpected changes in backup size
  • Transfer/authentication failures
  • Retention cleanup status
  • Periodic restore testing
07 · SECURITY

Protect the archive

  • Use encrypted transfer protocols.
  • Keep credentials out of public repositories and screenshots.
  • Use least-privilege access.
  • Do not expose the storage location as anonymous public file hosting.
  • Keep backup data separate from the live service where possible.
08 · SUPPORT

Troubleshooting checklist

IssueCheck
Cannot connectConfirm hostname, port/protocol, credentials and whether the source IP/network can reach the service.
Upload failsCheck permissions, free capacity, path and source file size.
Backup job says success but file missingVerify destination path and inspect the source job log/output.
Storage unexpectedly fullReview retention cleanup and large/unexpected backup sets.
Restore unusableValidate the archive/dump and confirm the source backup completed correctly.
09 · PRODUCT FIT

Storage Box vs OA Vault 42

Use Vault 42 when the requirement is continuous radio stream recording into clock-aligned hourly MP3 files with a 42-day rolling archive.

Use Storage Box when the requirement is general backup/archive storage for server files, databases, media assets, snapshots and other operational data.

Need help with OA Storage Box?

Use the project/support contact route for provisioning, migration, platform configuration or a custom deployment.

Contact OACAST ↗