Choose the backup method before copying data
Jellyfin’s built-in backup can run while the server is online, with low activity and no active scan recommended. A manual backup instead requires the server to be stopped before copying its data and configuration. Applying one method’s running-state assumption to the other risks an unusable copy or an unexpected interruption for viewers.
Review version and backup contents
The publisher dates the built-in feature to version 10.11. Its backup options include the database and optional metadata, extracted subtitles and separately stored Trickplay data. The guide also explains that database migrations prevent simply downgrading a started newer installation to an old version. Restoring a matching backup is part of the rollback plan, rather than reinstalling an older executable over already migrated data.
Prepare a specific maintenance window
For an administrator upgrading their own server, record the current version and choose the supported backup method before the change. Confirm which data categories are included and where the archive or copied directories are stored; do not assume that a configuration backup is a backup of every original film file. Make sure the destination has sufficient free space and preserve the original backup separately from the active instance. A built-in restore restarts the server, so plan the interruption. After a deliberate restore, verify the expected users, library metadata and a lawful sample rather than judging recovery from the login page alone.
Questions, answered
Does a manual backup use the built-in feature’s online assumption?
No. Jellyfin instructs administrators to stop the server before a manual data-and-configuration copy.