2024-02-08, 06:18 AM
(This post was last modified: 2024-02-08, 06:19 AM by abpjf. Edited 2 times in total.)
I have this exact same scenario (2 Jellyfin servers using the exact same NAS libraries, 1 server for "outside" use and another for "inside" use) and have never run into a problem, with syncing data or watch times or what have you. Basic config:
1. As most have already stated, designate one server as the "master" - ALL data management is done via this server
2. The "slave" server should have ALL scraping/update functions DISABLED (as in, it should never automatically update libraries on media detection, no metadata scrapers set up EXCEPT for "use local metadata" only, etc), all user accounts (except your own) on that slave server should be not-Admin ("read only" as others have stated)
3. Whenever you add / remove / otherwise update library content, do so via the Master server; make any info/matching/corrections BEFORE even thinking about the Slave server
4. WAIT as long as needed (honestly, if you have no reason to do an 'immediate' update sync on the Slave, then don't) for any scans/refreshes/etc to complete on the Master - at least 10 mins minimum
5. ONLY THEN do you have the Slave server "scan for new" - it will correctly 'sync' content with the Master
ALL my users on the Slave server have no problem with watch progress, continue-from, etc
1. As most have already stated, designate one server as the "master" - ALL data management is done via this server
2. The "slave" server should have ALL scraping/update functions DISABLED (as in, it should never automatically update libraries on media detection, no metadata scrapers set up EXCEPT for "use local metadata" only, etc), all user accounts (except your own) on that slave server should be not-Admin ("read only" as others have stated)
3. Whenever you add / remove / otherwise update library content, do so via the Master server; make any info/matching/corrections BEFORE even thinking about the Slave server
4. WAIT as long as needed (honestly, if you have no reason to do an 'immediate' update sync on the Slave, then don't) for any scans/refreshes/etc to complete on the Master - at least 10 mins minimum
5. ONLY THEN do you have the Slave server "scan for new" - it will correctly 'sync' content with the Master
ALL my users on the Slave server have no problem with watch progress, continue-from, etc