2024-08-22, 06:27 PM
(This post was last modified: 2024-08-22, 06:28 PM by TheDreadPirate. Edited 1 time in total.)
(2024-08-22, 06:21 PM)Efficient_Good_5784 Wrote: From what I see, everything appears good.
The only bit of advice I would give is to add a bit more to make a copy of the config folder and store it in a separate location on the NAS so that if the new Jellyfin update breaks something, you have a backup from just before the update. Just make sure the container is shut down before starting the copy task so the database doesn't have a chance of being copied during and operation and getting your backup in a corrupted state.
To refine on this point, you should use rsync instead of plain copy. Copy will do a sufficient job of making a backup, but will never cleanup files that are no longer present at the source. If you rename, delete, or re-identify media the associated metadata (like images) will change. Copy will not touch the now obsolete metadata. This can cause the backup to bloat over time as old images, subtitles, etc., are not cleaned up.
Rsync CAN cleanup the destination when files are deleted at the source.
Code:
rsync -a -p --progress /volume1/docker/jellyfin/config /path/to/backup/directory/ --delete
The --delete option is what cleans up the destination folder when files are no longer present at the source.