my_backup: Daily Backup task stale — logon-type fix + WSL wake-up

Date: 2026-07-30 Dept: IT Project: my_backup

What happened

Daily Backup Scheduled Task didn’t run at 08:00 — machine had no active interactive session (Event ID 332 confirms: LogonType: Interactive skips launch when nobody’s logged on). Talbot confirmed a power outage overnight took the desktop down.

Fixes applied

1. Immediate: manually triggered the task; full run completed, exit 0.
2. Permanent — logon type: changed task to Password logon (“run whether user is logged on or not”) so it can run unattended. S4U was considered and rejected — its token can’t authenticate to the NAS (SMB) targets this job writes to.
3. BIOS: Talbot set “Restore on AC Power Loss” → Power On, so the desktop auto-boots after a power cut (separate mitigation from the logon-type fix — Password logon alone can’t run on a machine with no power at all).
4. Second-order bug found + fixed: the Password logon change exposed that WSL doesn’t auto-start in an unattended session, breaking the WSL-Dev backup step and the wsl.exe heartbeat call (\\wsl$\Ubuntu-24.04\home\ta unreachable). Fixed by adding wsl.exe -d Ubuntu-24.04 -e true to the wrapper script (D:\FSS\Software\Utils\Windows\my_backup-daily-task.bat) before the backup step.

Verification

Two live schtasks /run cycles: first reproduced the WSL failure (exit 1), second confirmed exit 0 with all targets synced (B2, NAS Active+Static, Seagate, SanDisk, WSL-Dev).

Lesson promoted

Core/Processes/Software Dev/GlobalDevRules.md § 3.9 — general pattern: Password-logon scheduled tasks need an explicit WSL wake-up before touching \\wsl$.

Related

• Core/IT/Tasks/my_backup-no-backup.md (2026-07-26) — different failure mode, same job (venv poisoning, not logon type)
• Core/IT/Logs/2026-07-26_my_backup-no-backup.md