Setting up cold-standby instance

[Yusuke Izumi]

We're having a bit of an issue while we were setting up the Cold-standby instance of Confluence.

We've first installed the Active instance, with the production license corresponding to our Server ID.

Additionally, we've installed the Cold-standby, intending to run with the developer license (as I was told by the Atlassian sales-person), and configured the database settings.

(The database is same as the Active server.)

During the database settings, we came across a dialog telling us that everything is going to be overwritten, but that's not what we want to do.

Is there some instructions for setting up a cold-standby instance?

We've read this carefully, but doesn't seem to give us any good hints:

https://confluence.atlassian.com/pages/viewpage.action?pageId=154633658

Is it because we're supposed to shutdown the Active instance before setting up the cold-standby instance?

Regards,

[Septa Cahyadiputra · Accepted solution]

Hi Yusuke,

As describe on the ticket. the mentioned message means you are trying to update an existed database that already has contain on it. If you wish to build a staging environment of your Confluence production instance in a nutshell you would need to do the following steps:

1. Create a cloned database and HOME directory of your production instance
2. Modified confluence.cfg.xml on the cloned HOME directory to point Confluence to the cloned database
3. Point the new installation directory to the cloned HOME directory
4. Start it up
5. Modified the license to your developer license

Hope it helps.

Cheers,
Septa Cahyadiputra

[Andy Brook [Plugin People]]

Hey there, Clustering and cold DR is not the same, that page should not be used for what you describe.

In this scenario the 'install' consists of backing up your production instance (specifically your Confluence HOME dir) and restoring it to the DR box but NOT running an actual installation, as that would indeed try to 'initialise' the database.

The above is nearly no different to:

a) create a database backup

b) zip the Confluence home folder

c) restore database to a new 'dev/offline' instance

d) unpack confluence backup, setup application to point to new home dir, fix the database details in your confluence.cfg.xml.

By doing that, you have a duplicate instance. The same process would work for the cold DR, minus the database restoration....