Let's take a simple scenario. VM is stored on Node1. A Replication rule is created, so the VM is replicated on Node2. The VM is HA protected. Replication is done once at 5 minutes
Node1 gets offline so the VM is moved to Node2 by HA. After 60 minutes Node1 gets back online and is accepted back into the cluster. VM remains on Node2 and is not manually migrated back to Node1.
Here are some questions:
- after Node1 is back into the cluster, and is left there, will data from Node1 continue to be replicated (replaced) on Node2? Because in this case the VM will be "continuously overwritten" with old data from Node1 (before the outage), which is a very bad idea;
- after Node1 is back into the cluster, is there any way for the VM to be automatically replicated from Node2 to Node1? Note that there isn't any initially created rule that Replicates the VM from Node2 to Node1 (obviously), but only from Node1 to Node2. So is Proxmox "smart enough" to "speak" with the HA services and automatically "reverse direction" for the Replication rule?
Node1 gets offline so the VM is moved to Node2 by HA. After 60 minutes Node1 gets back online and is accepted back into the cluster. VM remains on Node2 and is not manually migrated back to Node1.
Here are some questions:
- after Node1 is back into the cluster, and is left there, will data from Node1 continue to be replicated (replaced) on Node2? Because in this case the VM will be "continuously overwritten" with old data from Node1 (before the outage), which is a very bad idea;
- after Node1 is back into the cluster, is there any way for the VM to be automatically replicated from Node2 to Node1? Note that there isn't any initially created rule that Replicates the VM from Node2 to Node1 (obviously), but only from Node1 to Node2. So is Proxmox "smart enough" to "speak" with the HA services and automatically "reverse direction" for the Replication rule?
Last edited: