Hi folks,
I`m playing around with relax-and-recover (http://relax-and-recover.org/). I would like to make easy bare-metal-recoveries of my [cluster] boot drives.
Now the Question:
As backups always collide with open databases, how is proxmox affected with this?
I read multiple times https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs) and I imagine a rebooted proxmox-host extracts the /var/lib/pve-cluster/config.db and creates the structure under /etx/pve. Having this in mind I`m thinking it would be bad if relax-and-recover has already restored files under /etc/pve.
Maybe it would be sufficient to exclude /etc/pve/* during the backup because a halfway actual /var/lib/pve-cluster/config.db is enough to bring the node up an get an actual /var/lib/pve-cluster/config.db through corsync again.
Thanks for taking time to read my stuff,
I`m playing around with relax-and-recover (http://relax-and-recover.org/). I would like to make easy bare-metal-recoveries of my [cluster] boot drives.
Now the Question:
As backups always collide with open databases, how is proxmox affected with this?
I read multiple times https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs) and I imagine a rebooted proxmox-host extracts the /var/lib/pve-cluster/config.db and creates the structure under /etx/pve. Having this in mind I`m thinking it would be bad if relax-and-recover has already restored files under /etc/pve.
Maybe it would be sufficient to exclude /etc/pve/* during the backup because a halfway actual /var/lib/pve-cluster/config.db is enough to bring the node up an get an actual /var/lib/pve-cluster/config.db through corsync again.
Thanks for taking time to read my stuff,