A second instance of Confluence as backup and fallback system.

[Peter Merkel _mgm-tp_]

Hello together,

i had a pretty interesting discussion about Backups and Fallbacks in case of availiability issues of a main Confluence-Instance with one of my clients.

My Clients Question:

During this conversation i was asked, whether it was possible to run 2 instances of Confluence, lets call them Live and Fallback, and have only some dedicated, business critical content in the form of pages, sub pages and attachments of those in the Live Instance synchronised automatically to the Fallback Instance. My client pointed out that besides the common methods in data security like redundancy and backups, this would be a very requested feature and good to have on top, since critical processes would have to go on-hold while resores or error diagnostics are conducted.

My Question:

Is there any feasible way to realize such an approach, out-of-the-box, via scripting, or add-ons? To date i could not find any other topics in the community discussing such an approach.

I'd be grateful for any advise or experiences on this topic.

Regards!

Edit:

for integrity and as my recherche is still wip; i have been pointed in those 2 directions:

• https://wiki.comalatech.com/display/CWL/Remote-space%20publishing
• https://marketplace.atlassian.com/apps/284/confluence-command-line-interface-cli?hosting=cloud&tab=overview

Any experiences with those?

[Zak Laughton · Accepted solution]

Hi Peter,

There isn't a way to set up this type of fallback natively on a Confluence standalone instance.

For high-availability and fallback in case of application failure, the only natively supported option is to use a Data Center installation (see also: How can I achieve HA in Confluence?)

And for backups, we recommend regularly backing up the database and Confluence home directory according to the steps on Production Backup Strategy (this can be done on standalone or data center instances).

I hope this helps!