Yep, config folder is shared and AFAIK format of config files hasn't changed. Well you can simply tar /etc/pve directory just in case.
Reinstall and reconnect probably will do, but there may be problems with SSH keys since reinstalled node will get new one, i does not know how proxmox handles this case. I have both 2.3 and 3.0 nodes in my cluster. No problems detected, everything works (including live migration), but still this is unsupported. On Mon, Jul 1, 2013, at 11:16 AM, Fábio Rabelo wrote: Ho to all ... And thanks in advance for any help .. I have a running 5 node pve 2.3 cluster . To upgrade to 3.0, the how-to advises to make a backup of all config beforehand . But, in a cluster, all config files are replicated in all nodes, correct ? So, if something goes wrong in upgrade, all I need to do is reinstall that node from scratch and reconnect to the running cluster ... Am I wright ??? And. if something indeed goes wrong, I can install PVE 3.0 and reconnect to running 2.3 cluster, or I MUST reinstall 2.3 ? Just looking for best practices .... Fábio Rabelo _______________________________________________ pve-user mailing list [1][email protected] [2]http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user References 1. mailto:[email protected] 2. http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
