Prepare a Jellyfin built-in backup before an upgrade

The useful distinctions

• The built-in backup facility was introduced in Jellyfin 10.11.
• Dashboard Backups provides Create Backup with selectable archive components.
• The database is always included; metadata, subtitles and trickplay are selectable.
• Restoring through the interface restarts the server; downgrading a migrated installation requires an appropriate backup.

Define what recovery means

A useful checkpoint has a stated purpose. Before upgrading, decide whether you need only database state or also the generated and downloaded assets that support the catalogue experience. Write those choices beside the archive name. This small note prevents an archive from becoming a mystery file whose age is known but whose contents and intended recovery point are uncertain.

Keep media and state distinct

The built-in options describe server-state components. Maintain a separate plan for original media files and anything stored elsewhere. A successful archive creation should not be interpreted as proof that every film or album has another copy. The example lists a fictional version label and two component decisions so the recovery note can be reviewed without disclosing a real server name or user database.

Make rollback concrete

An upgrade can migrate stored state, so simply reinstalling an older executable is not a complete recovery strategy. Retain the matching checkpoint and installation context before proceeding. Schedule a quiet interval for restoration and tell regular users when the service will be unavailable if you administer a shared server. Verify the recovered catalogue against a short known-item list before treating the recovery process as complete.

A focused way to proceed

1. Open Dashboard, Backups and Create Backup during a quiet period.
2. Review the selected components and available disk space.
3. Create the archive and record the source server version and chosen components.
4. Keep the archive accessible outside the installation being upgraded.
5. Plan a restore window because the interface restore restarts the server.

Worked example · synthetic

Archive note: workshop-pre-upgrade.zip
Source build: record actual installed version here
Database: included
Metadata: selected
Subtitles: selected
Trickplay: not selected
Original media backup: separate process

Read the comparison

An archive is a versioned recovery asset; creation alone does not verify restoration or media coverage.

When to stop or ask for help

For a failed restore, retain the untouched archive and exact version information for official support.