vh
852896120a
Read-only companion to server_inspect.sh. Runs over ssh via stdin the
same way:
ssh root@pfi-pve 'bash -s' < scripts/proxmox_inspect.sh \\
> servers/pfi-pve/proxmox-details.txt
Captures what the generic inspect misses on PVE nodes:
- Cluster + node resources (pvesh get /cluster/resources)
- VM list + per-vmid config highlights (qm list, qm config)
- LXC list + per-ctid config highlights (pct list, pct config)
- Storage pools (pvesm status, zpool, storage.cfg, NFS mounts)
- Backup jobs table parsed from /etc/pve/jobs.cfg (no jq needed)
- Per-guest backup coverage verdict: YES/NO with reason
- Most-recent actual backup per VMID on each local dump storage
- PBS targets, replication jobs, listening ports, subscription status
Coverage analysis surfaces the real gap: on pfi-pve, VMIDs 106, 107,
109, 112, 113 have no scheduled backup; VMID 106 (PFI-Tailscale) has
not been backed up since 2024-05-31. nh3-pve uses "all" job and covers
everything. esh-pve + esh-pve-nas share the tank-vmbu dump storage via
NFS; coverage splits cleanly across the two nodes.
First snapshots committed for each PVE host.
pfi-pve
Proxmox VE hypervisor for the Anaheim colo (pve.phasefinal.com). Hosts every VM in the PFI-ANA cluster.
Network
- LAN IP: 10.250.250.31
- FQDN:
pve.phasefinal.com - Web UI:
https://10.250.250.31:8006 - SSH:
root@pfi-pve(key auth;ssh-targetfile uses the hostname)
Hardware
- CPU: Intel Xeon Silver 4310 @ 2.10 GHz
- RAM: 188 GB
- Kernel:
6.8.12-8-pve(Proxmox 8.x) - Storage: local
pve-rootat 65G (49% used) +pveLVM pool for VM disks
What it runs
The VMs in docs/pfi/proxmox-vms.md live here — VM 100 (PFI-ANA-TRUENAS, now Debian NFS/SMB), VM 101 (DC), VM 102 (PFI-ANA-Docker = ana-docker), 103–111 (Mongo, Postgres, Tailscale, Pteradactyl, Webhost, tacticalrmm, etc.).
ana-ml2 (10.250.50.54) is a separate bare-metal box, not on this hypervisor.
Refresh state
scripts/refresh-server-info.sh pfi-pve
The snapshot captures host/hardware/filesystem/network/ports but not VM-level detail (server_inspect.sh targets Docker hosts). Running qm list, pvesh get /cluster/resources, and zpool list -v manually is the current way to audit VMs and storage. A Proxmox-flavored inspect script is a future improvement.
Placement rule
This is a hypervisor, not a target for Docker stacks. Add new workloads by standing up VMs here (or on ana-docker / ana-ml2, whichever fits) rather than deploying containers directly on the PVE host.