High Availability + Replication = Disaster

[Ashkaan Hassan]

Hi, I've configured HA and replication, but when I actually reboot a server, the failover fails stating that the volume already exists at the target node.

Some helpful info:

• I have 8x nodes
• my goal is to have replications every 15m
• when there's an event that causes a failover, either a quick delta to get the latest, or just run the 15m old version
• I have each vm set to failover and replicate to 2x other nodes (just in case)
• I have groups configured with priorities
• I separately have replications configured from Source to Destination A and Destination B

 

[gurubert]

Wouldn't it be easier to create shared storage with Ceph on the 8 nodes instead of asynchronously replicating the VM disks?
Or is that a non-local cluster with latencies too high to allow Ceph?

 

[homelabenthusiast]

@Ashkaan Hassan
1. What's the status of replicaion?
2. Are you using traditional storage replication or pve-zsync?
3. Maybe you can delete your replication tasks and remove the dangling vmdisk from the other nodes and do another clean replication

 

[Ashkaan Hassan]

Wouldn't it be easier to create shared storage with Ceph on the 8 nodes instead of asynchronously replicating the VM disks?
Or is that a non-local cluster with latencies too high to allow Ceph?

Ceph is too slow for our needs.

 

[Ashkaan Hassan]

@Ashkaan Hassan
1. What's the status of replicaion?
2. Are you using traditional storage replication or pve-zsync?
3. Maybe you can delete your replication tasks and remove the dangling vmdisk from the other nodes and do another clean replication

1. Error. "2024-03-11 08:54:04 110-0: volume 'rpool/data/vm-110-disk-0' already exists"
2. I just went to Replication under Datacenter and configured each one there.
3. Then the replication will be happy and the next time I need to failover, it will error again.