minor change not worth adressing

2026-04-21 19:17:10 -04:00
parent d4bf31a5f4
commit 107b9d99fe
3 changed files with 19 additions and 13 deletions
@@ -140,7 +140,7 @@ The same share lists are used by `failover.sh` for Tier 4 writeback — but in t
 Runs a clean nightly sync for Emby and the auth stack (Critical-Data) with containers stopped. This is the companion to the hourly dirty sync — it provides a fully consistent state on HOST2 once per night.

 ```bash
-# Scheduled as: 30 2 * * *  (2:30am daily — after daily_sync.sh finishes)
+# Scheduled as: 30 2 * * 0  (2:30am Sunday — weekly clean sync)
 /mnt/user/appdata/unraid_scripts/Orchestrators/nightly_critical_full_sync.sh
 ```

@@ -303,10 +303,10 @@ This pattern means:
 */3 * * * *   transcode_management.sh    # cleanup then manager — every 3 minutes
 0 1 * * *     daily_sync.sh             # 1am — media shares to remote
 0 2 * * *     media_management.sh       # 2am — permissions, cleaners, arr cleanup
-30 2 * * *    nightly_critical_full_sync.sh           # 2:30am — clean Emby + auth stack sync
+30 2 * * 0    nightly_critical_full_sync.sh  # 2:30am Sunday — clean Emby + auth stack
 ```

-The gaps are intentional. `daily_sync.sh` can take 30-60 minutes on a large library. `media_management.sh` starts at 2am giving daily_sync an hour to finish. `nightly_critical_full_sync.sh` starts at 2:30am giving media_management time to complete its permission and cleanup pass before Emby is stopped for the clean sync.
+`daily_sync.sh` and `media_management.sh` run nightly — media shares and maintenance. `nightly_critical_full_sync.sh` runs weekly on Sunday — it stops Emby and the auth stack for a clean consistent sync. Running it weekly instead of nightly lets Emby's image cache stay warm on HOST2 throughout the week. The emby-failover dirty sync handles watch states, library structure, and auth every 30-60 minutes — the weekly clean sync covers metadata, plugins, and a full database flush.

 ---