Skip to content
Server
Database and Recovery

Database and Recovery

Database backups protect Engine records. Installer recovery points protect local program files. Keep an off-server copy before upgrades, restores, bulk edits, or migrations.

Create a Backup

  1. Open Settings → Database Backup.
  2. Create a backup and wait for completion.
  3. Download the file to protected off-server storage.

Local backups are stored in /opt/xaccel-engine/storage/backup/. Configure the schedule and local retention under Settings → System Settings → Database.

Optimize a Table

  1. Open Settings → Database Tables.
  2. Sort by Total Size and select one table.
  3. Download a current backup.
  4. Run Optimize during low traffic and verify disk space afterward.

Optimization may rebuild and lock a table, require temporary disk space, and may not reduce its size.

Restore

  1. Download a backup of the current database and stop configuration changes.
  2. Upload or select the intended compatible backup.
  3. Confirm the restart.
  4. Verify login, License, Servers, Streams, DVB, Users, VOD, and playback.

Restore accepts Engine .gz database backups. Engine checks the backup type and compressed file integrity before scheduling a restart and again before restoring. Older Engine backups without a format marker are checked by their contents. Codec, unrecognized, and damaged backups are rejected; use Tools → Import for Codec backups.

Changed in Engine 1.0.1+

The Master upgrades an older database before starting normal services. If migration fails, fix the reported error and restart. A database from a newer Engine version requires compatible software or a matching backup. Upgrade the Master before LB servers.

Engine 1.0.1+

Recover Program Files 

sudo bash ./xaccel-engine-<version>.sh --recovery

Use installer recovery for a failed software upgrade and a database backup for database restoration.

Migrate

  1. Install a compatible Engine release on the target.
  2. Back up and restore the source database.
  3. Copy media, certificates, and operator-owned files with their permissions.
  4. Reissue or activate the target license.
  5. Update addresses, interfaces, DNS, TLS, SSH, and media paths.
  6. Test all required functions before moving traffic.

Do not run two machines with one license.