2.0 KiB
2.0 KiB
OTIVM — Offline Archive InventoryOffline archives are vzdump snapshots of LXC container 1105 (otivm-dev) on srv-a.Each archive is stored in /var/lib/vz/dump/ on srv-a and copied to USB after creation.Before restoring any archive, read the state description carefully.Restoring will overwrite everything on the container — all code, all data, all PM2 state.
The Gitea repo is always the SSOT for code. Archives cover the OS, stack, and configuration.
Archive log
vzdump-lxc-1105-2026_04_25-04_10_53.tar.zst
| Property | Value |
|---|---|
| File | vzdump-lxc-1105-2026_04_25-04_10_53.tar.zst |
| Date | 2026-04-25 04:10 UTC |
| Size | 552 MB |
| Container | LXC 1105 — otivm-dev |
| Host | srv-a (10.0.0.11) |
| Storage | /var/lib/vz/dump/ + USB copy |
Container state at time of archive:
- Debian 12, unprivileged LXC
- 2 cores, 512 MB RAM, 8 GB disk
- LAN IP: 10.0.0.23, WireGuard: 10.110.0.18
- Node.js v22 installed (system)
- Python venv at /home/otivm/venv
serveinstalled globally at /home/otivm/.npm-global/bin/serve- Nginx on wg-pk configured and proxying otium.civicus.us → 10.110.0.18:3000
- SSL active on otium.civicus.us
- otivm user created, bashrc configured,
workalias present - Gitea repo cloned to /home/otivm/OTIVM
- PM2 NOT yet configured at time of this archive
- Vite + React scaffold NOT yet present at time of this archive
What this archive is good for:
Restoring the base OS and software stack if the container is lost or corrupted.
After restore, you must: clone the repo, run npm install, run npm run build,
install serve globally, and start PM2 manually.
Restore command (run on srv-a as root):
pct restore 1105 /var/lib/vz/dump/vzdump-lxc-1105-2026_04_25-04_10_53.tar.zst --force
Convention
Archive filenames follow Proxmox default: vzdump-lxc-{CTID}-{YYYY_MM_DD-HH_MM_SS}.tar.zst
Add a new entry to this file every time an archive is created and copied to USB.
Always note exactly what is and is not present in the container at time of archive.