Write down what would need to return
Start with the installed server version, deployment type and actual data and configuration locations. Custom paths matter; a default directory in a tutorial does not establish where this server keeps its state. Keep the intended recovery version beside the backup rather than only writing the date.
For an illustrative home server, the desired fallback is yesterday’s working installation, including its library organisation and accounts. A folder containing the new installer alone does not meet that goal. The recovery record must connect the previous version to the corresponding saved state and deployment details.
Choose the documented backup method
Jellyfin’s built-in backup feature was added in version 10.11. Its dashboard workflow offers a database backup and optional metadata, extracted subtitles and eligible trickplay data. Review the selected contents instead of treating the presence of a ZIP file as proof that every related file was copied.
The built-in process can run online, though the guide recommends a quiet period without an active scan. Manual backup follows a different procedure: the server is stopped before its actual data and configuration directories are copied. Do not mix the online built-in instructions with an improvised live database-folder copy.
Protect the separate media collection
The documented built-in choices concern server state and associated generated material. They do not establish that original films, recordings or music stored in separate library folders have been copied. Keep a separate inventory and suitable backup for those irreplaceable files.
Imagine the server’s state is on one disk while family videos are on another. Saving only the server archive may help restore library information but does not replace a failed media disk. Conversely, saving the videos alone does not demonstrate that account configuration and organised server state can be recovered.
Check capacity and the recovery window
Jellyfin warns that its initial free-space check may still be insufficient when large optional material is included. Check the archive destination, final completion and retained copy before upgrading. A backup stored only on the disk being replaced offers a different recovery prospect from a separately retained copy.
The official guide explains that downgraded operation requires restoring an appropriate backup, because migrated data cannot simply be used by the old release. Built-in restore also interrupts availability. Arrange that recovery window with viewers and validate the documented version-specific process; this article does not perform an upgrade or claim a tested restore.
Questions about this guide
Can an older server simply use already migrated data?
Jellyfin says it has no downgrade mechanism; recovery to an older version requires an appropriate backup.
Does a server-state archive prove the original video files were backed up?
No. Check those separate library files and their own backup explicitly.