Thanks Justin. Do you know what sort of considerations I would need to make if doing shipping, e.g.
1) What config, if any, would the node in the secondary DC need to have in common with the nodes in the primary DC? e.g. see the warning box regarding copying data directories and unique node id here <http://activemq.apache.org/artemis/docs/latest/clusters.html> . I assume my secondary DC node would have to have the same node id so that it can treat the journals as its own? 2) I assume the node in the secondary DC would not need to be/must not be in a cluster the primary DC's nodes? 3) I assume there would need to be a node per data directory being copied, e.g. if I have two active nodes in the primary DC then I will need to standby nodes in the secondary DC. 4) What if any file/directory management would need to be done on the secondary DC file structure if doing a straight file copy. I wouldn't want to copy the whole directory every 15 minutes for example, but rather just reflect the changes. 5) I assume the secondary DC nodes should be cold until required and then be manually activated? If anyone else has experience of doing this (DR requirements aren't rare :)) then I'd be very keen to understand your experiences. Another option I totally forgot about would be to use a core bridge to push messages across to a cluster in the secondary DC. The problem with this I guess is that as messages are removed from the primary DC queues they will remain in the secondary DC queues. Not sure if there is a TTL that can be configured to provide some pruning of messages from the secondary DC queues. However if this TTL is set too large then a large amount of duplicate messages would be delivered, or if it is set too low and the failover doesn't occur in time then there will be message loss. What would be ideal I think would be the option to use shared storage for local HA, but be able to combine this with the replication option for remote DR to a cold backup node. So rather than live-backup being a one to one relationship, a live node could have 1 shared storage backup and 1 replication backup, but only one of which can be auto failed to. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
