update stale media ownership language across all docs

arr_sync.sh bidirectional union replaced the old split-ownership model.
Old: HOST1 owns Movies/TV/Music, HOST2 owns Anime — each arr manages
different shares to avoid conflicts.
New: arr_sync.sh keeps all arr databases in union. Either server can
download to any share at any time. The union is the source of truth.

Auth stack references left intact — HOST1 still owns auth config
(one-way sync to HOST2). Only media library ownership language updated.

Files changed:
  README.md                          — server block + share annotations
  Fallback/README-Fallback.md        — role line + Split Source of Truth section
  Orchestrators/README-Orchestrators — daily sync share comments
  Rsync/Manual-Rsync.md              — DEFAULT_RSYNC_OPTS comment block
  Media/README-Media.md              — HOST AWARENESS section
This commit is contained in:
Gmer4Lfe
2026-05-22 21:35:45 -04:00
parent 29eb722057
commit 8d8a4fd637
5 changed files with 30 additions and 32 deletions
+11 -10
View File
@@ -59,7 +59,7 @@ HOST1 — unRAID-Gmer4Lfe
Hardware: Threadripper 1950X, 128GB RAM, ZFS cache pools
Location: Primary site
DDNS: Gmer4Lfe.com
Role: Primary — full service stack + source of truth for Movies/Shows/Music
Role: Primary — full service stack, arr_sync union for all media shares
HOST2 — unRAID-Jayred365
Hardware: Intel i5 10th gen, 64GB RAM
@@ -81,21 +81,22 @@ Container names "Emby" on HOST2 must be the container HOST2 starts for HOST1
Network names Docker custom networks must match for NPM routing to work
```
### Split Source of Truth — No Conflicts
### Union Library — arr_sync.sh Is the Source of Truth
Both servers run arr instances simultaneously with zero conflict — they manage completely
different shares:
Both servers run arr instances simultaneously. arr_sync.sh keeps all databases in
bidirectional union before every rsync cycle — either server can download anything
and it propagates to the other:
```
HOST1 owns: Movies (Radarr), Tv_Shows (Sonarr), Music (Lidarr)
HOST2 owns: Anime_Movies (his Radarr), Anime_Shows (his Sonarr)
HOST1 runs: Radarr (Movies), Sonarr (Tv_Shows), Lidarr (Music)
HOST2 runs: Radarr (Anime_Movies), Sonarr (Anime_Shows)
Each server mirrors the other's shares continuously via rsync.
All arr databases merged via arr_sync. rsync spreads files additively.
Either server downloads to any share — the other catches up on the next cycle.
```
The rule: never run two arr instances against the same share simultaneously. Different arrs
managing different shares is fine. When HOST2 runs HOST1's arrs during a Tier 4 fallback,
HOST1's Tdarr is not running (HOST1 is down) — no conflict.
When HOST2 runs HOST1's arr containers during a Tier 4 fallback, those arrs already
know the full library — arr_sync kept them in union while both servers were online.
### Auth Stack — Warm on Both Servers