FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated user scripts

Browse Source
This commit is contained in:
FailedProxy
2026-04-18 15:58:02 -04:00
parent 8c5667b1df
commit f48752afb9
2 changed files with 84 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Failover/README-Failover.md
+17 -3
View File
@@ -12,16 +12,30 @@ Two fully independent unRAID servers connected via Tailscale:
```
HOST1 — unRAID-Gmer4Lfe (Primary)
Location: Local
Hardware: Threadripper 1950X, 128GB RAM
Owns: Gmer4Lfe.com DDNS
Runs: Full service stack
HOST2 — unRAID-Jayred365 (Secondary / Buddy server)
Hardware: Intel i5 10th gen — completely different hardware
Location: Remote — 50 miles away
Owns: Gmer4Lfe.us DDNS
Runs: Its own service stack + mirrors HOST1 data
Runs: Its own service stack + mirrors HOST1 critical data
```
**Hardware doesn't need to match.** Everything is accessed through `/mnt/user/` — unRAID's fused share layer. HOST1 has a Threadripper with multiple ZFS pools. HOST2 has a completely different CPU, fewer drives, different layout. The failover containers on HOST2 mount `/mnt/user/Movies` and see the same data because the share names match and the data is mirrored. The hardware underneath is irrelevant.
**What needs to match between servers:**
- Share names (`/mnt/user/Movies` = `/mnt/user/Movies`)
- Container names for shared failover services
- Docker custom network names (so NPM can reach containers by name, not IP)
**Normal operation — HOST2 is essentially passive:**
HOST1 is the source of truth. It runs everything — all arrs, all downloads, all active services. HOST2 keeps its media mirror current via nightly rsync and waits. All media is mirrored so when Emby starts on HOST2 during failover it has the exact same library, same metadata, same watch history. No separate library, no separate database, no user-visible difference.
Don't run arrs on both servers simultaneously — two instances writing to the same share causes conflicts and duplicate downloads. HOST2's arrs only start at Tier 4 (18hr+ outage) when genuine workflow continuity is needed.
Both servers run `failover.sh` as a background task continuously. Neither server knows what the other is doing — they only know what they can ping from their own network perspective.
---