This dependence mainly on what storage you use.
If you have shared storage or distributed you can move the VM config in proxmox cluster fs.
If not then you must restore a backup, because you need the VM image to run the VM.
Your nodes are on the same release so an upgrade is no big thing.
PVEbld15 is up to date.
then update one by one.
Stop or migrate all VM from the node that you like to update.
If it is clean run the upgrade process.
Then reboot the node.
Then move on to the next node.
What is the exact usecase?
If just the cluster (corosync) there is no need for it.
But as VM has always a time drift you should have a local NTP server and use this.
Also, it depends on the application if you need the correct time or just an identically time?
Does the VSS in the VMs triggers if the backup starts?
I don't know Exchange but I guess it is the freeze of the fs that produce the Error.
Disable the qemu-guest-agent and test again.
Keep in mind if qemu-guest-agent is disabled the OS does not flush the caches and the Backup may not consistent.
Hi,
I guess there will no problem.
I the worst case the services can't start, but they will not send evil packages ;-)
But you must finish the upgrade on this node.
How this works depends on where the upgrade stopped.
Hi,
DNS and also HA-Proxy are not always clustered. And if not you have on this stack a single point of failure.
Assume you have DNS and HA-Proxy redundant the I would prefer HA-Proxy(the config is simple and can be found in may Blogs). Second DNS. If this is not the case you could use e.g...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.