renstur@coopnet:~/blog$ ls -lt ./topics/proxmox-storage/
proxmox-storage/
Proxmox clusters, ZFS layouts and what the backups really cover.
-
Getting a single node Proxmox cluster ready for a second site
My corosync edit kept reverting because I changed the local copy. Edit /etc/pve/corosync.conf with copy, edit, move and bump config_version. A single node cluster opens no UDP on 5405, so the overlay link can't be tested until node two, and quorum needs a plan first.
-
How I laid out ZFS pools on a Proxmox host
I picked mirrors for every pool on my Proxmox host because rebuild time and growing by two disks matter more than RAIDZ1's extra space. Importing an old pool mounted a dataset over /var/lib/vz and hid a running VM's disk. Run zpool import -N and check mountpoints first.
-
My Proxmox backups covered less than I thought
My Proxmox backups covered less than I thought: weekly jobs with keep-last=3 only reach back three weeks, the dump folder held another host's files, one host had no job at all, and root mail had gone nowhere for over a year. A real restore drill is next, and I haven't run it yet.