Media Server to Media Server

Why server-to-server syncing is fragile, when it can work, and the safety checks you need.

Media server to media server syncing is possible. It is also the fastest way to corrupt state.

When it is OK

Consider this only when:

• You understand the risks.

• Both servers have near-identical libraries.

• You have tested backup and restore on both servers.

If you can’t restore, don’t sync.

Why it is fragile

Backup and restore is required

• Back up each server database and app data before syncing.

• Test restore before enabling two-way.

• Expect overwrites when IDs shift.

  • History can be lost.

  • Ratings can be lost.

  • Watchlists can be lost.

"Same library" is rarely the same library

Libraries drift. Small differences compound over time.

Common causes:

• Different folder layout.

• Different editions or cuts.

• Partial seasons.

• Extras and specials.

• 4K vs 1080p duplicates.

ID mismatches cause silent damage

Providers use different identifiers:

• Plex GUIDs

• Jellyfin/Emby internal IDs

• TMDb/TVDB/IMDb remaps

Small mismatches can write to the wrong item. You often notice weeks later.

Mistakes cascade

One bad match on Server A copies to Server B. A later rematch makes B look wrong. Then you "fix" B and A flips back.

That loop is hard to unwind.

If you still do it

Do these before enabling two-way:

• Start one-way and validate results.

• Sync one library at a time.

• Prefer history via scrobble, not bulk history sync.

• Watch logs for rematches and unexpected deletes.

Related topics

• Best practice - safer defaults.

• Trackers vs. Media Servers - pick a source of truth.