https://issues.jboss.org/browse/WFLY-3418 I realize this is likely to late for inclusion in 6.3 but would like to ask anyhow. Otherwise, we kindly request this for a CP. Install node 1 remove all local servers start it in domain mode, so it runs as the DC use the CLI to deploy an application => the application will end up in the domain/data/content folder as expected. Install node 2 on another machine remove all local servers point it to the DC on node 1 start in domain mode, so it runs as a HC wait a little... stop the node 2, and inspect the local domain/data/content => empty start node 2 again on node 1, with the CLI, deploy a second application inspect node 2 local domain/data/content => the new / 2nd application will have been copied but the original first is still not copied. Whether you start node 2 with or without "--backup" makes no difference. Problem: due to the HC not receiving a full copy of the "content" folder, it is not possible to promote the HC to a DC (when the original DC is down)
workaround: Do not promote an HC. Instead have a backup of the DC and restore when needed.
workaround2: use rsync or similar to keep the "content" directory of an HC synced with the DC
Verified on EAP 6.3.0.ER7. Starting a node 2 with the "--backup" force synchronization of domain/data/content folder with node 1.