← LogEntry 025
Major
2025 – present
A four-node, 41-machine Proxmox cluster taken over and documented
IT services provider, RO
Proxmox VEProxmox Backup ServerNFSZFS
- Physical nodes
- 4
- Virtual machines
- 41
- Downtime during rename
- 0
Record
Context
A cluster grown organically over years: four physical nodes, forty-one virtual machines, several administrators along the way and no current documentation.
Problem
The audit surfaced duplicate MAC addresses across machines, missing backup jobs for production systems, a high availability configuration still pinned to a decommissioned node, and storage allocated with no record of it.
What I did
- 01Full inventory: node by node, machine by machine, with owner and purpose identified
- 02Fixed the duplicate identifiers that were causing intermittent network conflicts
- 03Brought every production system under backup, on a dedicated backup server
- 04Renamed a node live, without stopping the machines hosted on it
- 05Standardised administrative access with dedicated accounts and controlled privileges
Result
A documented cluster under monthly management, with verified backups and an activity report. The intermittent network problems, present for months, disappeared along with the duplicate identifiers.