There's nothing built in to Artemis at this point specifically for the DR use case. However, I believe the "data" directory (where persistent data is stored by default) can be replicated (e.g. via a block-level storage replication solution) or "shipped" via an external process (e.g. rsync) to a DR backup.
Justin On Wed, Nov 29, 2017 at 5:45 AM, JohnBeeBee <john.bund...@ipfin.co.uk> wrote: > I am looking at options for handling local failover and disaster recovery. > Our existing primary and secondary data centre hosted services run mainly > active-passive and have SAN storage but do not support SAN replication. > There is a dedicated network between the two DC's so we have fast, reliable > connectivity. > > For local single node failure in the primary we would failover to a local > backup server configured to use shared storage, however I'm not sure what > the best options are for handling a complete primary DC failure so that we > can failover to the secondary DC. As I said we don't have SAN replication. > Is there anything similar to SQL log shipping that can be performed? We > currently use BizTalk which uses SQL log shipping and so we already accept > a > certain amount of message loss in the case of a DR. Even better is there > an > option which would remove all data loss from Artemis in the case of a full > DR scenario? > > Thanks > > John > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
