Separate server state from media originals
Before replacing an Emby server, write down the information you need to recover. Server settings, users, watched state, metadata, recordings and movie files are different assets. Emby’s Backup & Restore plug-in covers defined server-state categories; its documentation explicitly says it does not back up the library’s media contents.
Keep a separate inventory of the actual media roots, camera-upload location and recording directory. If a folder sits inside the server’s data area, do not assume it is included merely because the server configuration is backed up. A complete migration plan needs evidence for those files as well as a successful plug-in task.
Verify the backup feature and destination
Emby documents Backup & Restore as a Premiere plug-in. Confirm its current installation and any restart-required update before planning a recovery around it. Open its settings and inspect the actual absolute destination path. An undefined path does not produce usable backups.
Check that the server process can write to that destination. On a Windows service installation, the guide calls for a local path or a suitable UNC share rather than a desktop mapped-drive letter. Keep the destination and access account private. A drive visible in an interactive session does not prove the background service can use it.
Create a known backup and inspect its coverage
Review the metadata options and available destination space before running a backup. A larger metadata selection can change the time and storage needed. Run the documented Emby Server Backup task deliberately and inspect its completion and resulting backup information rather than waiting for an assumed overnight run.
Retain a record of the server version and plug-ins. Emby notes that saved plug-in configuration does not mean every plug-in binary or plug-in database is included. Keep the separate installation and data requirements in the migration notes. An apparently complete server backup should not hide a missing dependency that only becomes visible after replacement.
Plan recovery before retiring the original
Check the developer’s compatibility and migration guidance for the old and proposed new server versions. Preserve an independent copy of the backup and protect the actual media through your own file-backup process. Do not retire the original server merely because a backup file exists with a recent timestamp.
Prepare a verification list for the restored system: one ordinary viewer, a known movie, watched state, a recording and any custom upload folder you use. This guide ends with a reviewable backup and coverage plan. It does not claim a restoration test has occurred or that a plug-in backup alone protects every file on the host.
Questions answered
Does Emby’s server backup include my films?
The plug-in documentation says library media contents are not included. Protect those files through a separate media-backup process.
Can a Windows service rely on my desktop mapped backup drive?
Emby’s guide calls for a local path or a suitable UNC path for a service. Verify the service account’s actual access to the destination.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.