2025-04-17, 03:11 PM
Depending on how you're doing backups, its possible this file existed when the contents of /var/lib/jellyfin were enumerated but was no longer present when the backup went to actually copy the file.
Additionally, this implies you are backing up Jellyfin while it is running. 99% of the time this is probably ok, but we do recommend you shutdown Jellyfin during a backup to ensure that database commits are, at least, written to the database WAL/SHM files.
If you happen to capture the database while a commit was pending in memory or mid-commit, the resulting restore may be corrupt.
You can use rsync to do differential backups, which would massively cut down on backup times. My daily backups are quick enough that clients have enough buffer to not notice the disruption. Usually under 20 seconds from initiating shutdown to becoming fully available again. Though I run the backup in the middle of the night to ensure this goes unnoticed.
Additionally, this implies you are backing up Jellyfin while it is running. 99% of the time this is probably ok, but we do recommend you shutdown Jellyfin during a backup to ensure that database commits are, at least, written to the database WAL/SHM files.
If you happen to capture the database while a commit was pending in memory or mid-commit, the resulting restore may be corrupt.
You can use rsync to do differential backups, which would massively cut down on backup times. My daily backups are quick enough that clients have enough buffer to not notice the disruption. Usually under 20 seconds from initiating shutdown to becoming fully available again. Though I run the backup in the middle of the night to ensure this goes unnoticed.