Identify the goal of the second installation
A second Kodi device may need the same server libraries, but that does not mean its local integration state should be copied from the first. Begin by naming the new client, intended viewer and libraries. Keep the original device working as the comparison.
Use the actual Kodi and add-on versions in the notes. A general same-platform backup plan and an integration’s client identity are different concerns. Do not assume that because a database file can be copied, the server will treat the resulting clients independently.
Follow the documented client-identity boundary
Do not clone client database files; Jellyfin documents synchronization conflicts. Use the supported independent setup route for the receiving installation. Keep its own device identity and intended viewer recorded before comparing the result with the existing player.
Preserve a recoverable configuration copy for the receiving device before changing its integration. Keep the old device’s data as a backup, not as an unexplained shortcut into the new client. A partially populated movie list is not proof that cloned synchronization state is healthy.
Verify one known update on each client
After the independent setup has completed its supported initial process, inspect one known server item on both devices under the intended accounts. Record identity, metadata and playback separately. A client using another viewer can legitimately have a different watched state.
For an original comparison, add or correct one harmless server item through the server’s normal workflow, then observe the two clients’ documented update behavior. Keep the time and selected libraries in the record. Do not change several client databases while assessing a single delayed item.
Retain an integration-specific support case
If an update fails, preserve the affected client’s version, selected libraries and first failed stage. Use the add-on’s documented log route and review private source details before sharing. A generic library screenshot can omit the client identity that explains the conflict.
The expected outcome is two independently configured clients with checked server data. It does not claim every item was tested or that a cloned database can be repaired by a simple refresh. Keep integration rules attached to the actual add-on instead of applying a general file-copy rule to all Kodi state.
Questions answered
Why is a copied movie list not enough proof that cloning worked?
The visible entries do not establish healthy independent synchronization state. Follow the integration’s explicit client-copy restriction.
What should be compared after an independent setup?
Use the intended user and one known server item, then observe identity, update behavior and playback separately.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.