High-Availability is allowed in combination with storage replication, but it
has the following implications:
-* redistributing services after a more preferred node comes online will lead
- to errors.
+* as live-migrations are currently not possible, redistributing services after
+ a more preferred node comes online does not work. Keep that in mind when
+ configuring your HA groups and their priorities for replicated guests.
* recovery works, but there may be some data loss between the last synced
time and the time a node failed.
WARNING: If expected votes are set avoid changes which affect the cluster
(for example adding/removing nodes, storages, virtual guests) at all costs.
-Only use it to get vital guests up and running again or to resolve to quorum
+Only use it to get vital guests up and running again or to resolve the quorum
issue itself.
- move both guest configuration files form the origin node A to node B: