9.3. Error Handling

If a replication job encounters problems, it is placed in an error state. In this state, the configured replication intervals get suspended temporarily. The failed replication is repeatedly tried again in a 30 minute interval. Once this succeeds, the original schedule gets activated again.

Some of the most common issues are in the following list. Depending on your setup there may be another cause.

In the case of a grave error, a virtual guest may get stuck on a failed node. You then need to move it manually to a working node again.

Let’s assume that you have two guests (VM 100 and CT 200) running on node A and replicate to node B. Node A failed and can not get back online. Now you have to migrate the guest to Node B manually.

Remember to replace the VMIDs and node names with your respective values.