A date alone leaves an important question
A folder labelled before upgrade tells you when it was created, but not which server can use it. Jellyfin warns that database migrations affect downgrade options. Record the originating software version alongside the date rather than relying on memory or the version currently installed on the machine.
Use a recovery label with meaningful fields
Add the installation method, backup method, actual data/configuration locations and media mappings. Include whether the server was stopped for a manual copy. Do not put passwords or secret keys into a label that could be shared in a support request; keep sensitive recovery material protected separately.
An authored label might describe a local test server, version recorded from its dashboard, a stopped manual copy and a dated path worksheet. Its value is the explicit relationship between software and data. It does not certify that the files have been restored successfully.
Keep the evidence through the review period
During a recovery rehearsal, add the version used, which copy was restored and which checks passed. Preserve the untouched original backup. After an upgrade, retain the old label until the agreed review window ends so a later issue can still be traced to the intended recovery point.
Questions answered
Is an older installer enough for a rollback?
No. Retain the corresponding server data and the instructions appropriate to the backup method.
Should the archive label contain account passwords?
No. Keep useful version and path context without exposing secrets in filenames or shareable notes.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.