A Backup That Depends on n8n Is Not an Independent Control
After an update damaged both automation workflows and their internal backup path, I moved exports outside n8n. The failure exposed gaps in separation, secret handling, and restore testing.

After an update damaged both automation workflows and their internal backup path, I moved exports outside n8n. The failure exposed gaps in separation, secret handling, and restore testing.

An operator can automate an AWX upgrade, but it cannot decide whether your backups, capacity, compatibility, and recovery path are good enough.

The ESXi command is the smallest part of a safe update. Maintenance mode, rollback planning, compatibility review, and post-change evidence are the real controls.

Old kernels can fill a small boot volume, but cleanup should preserve a known-good fallback and use the package manager’s own dependency decisions.
