On this page

For various reasons (e.g. backups, setting up a test environment) it may be necessary to clone a Linchpin instance that is in productive use. If you are running an active connection to a Linchpin Mobile Gateway on the instance to be cloned, there are some important points to consider before the instance can be cloned without undesirable side effects.

Linchpin Data Center

Please first check which version of Linchpin Intranet Suite is installed in your data center instance and follow the appropriate steps below to prepare for the cloning process.

Prepare your instance for cloning (Linchpin Intranet Suite 5.0.x and older)

Before cloning your Linchpin Data Center instance, please make sure that the instance to be cloned has 'Duplicate Instance Detection' switched off. You can check this setting as a Confluence administrator by going to the following URL and scrolling to the bottom of the page:

https://[YOUR_CONFLUENCE_BASE_URL]/admin/plugins/linchpinmobile/connection.action

On the same page, please also make sure to disable the Gateway connection for your Linchpin Data Center instance to be cloned. You can disable the connection by pressing the toggle button in the top right corner of the connection status panel. The connection status should display as DISCONNECTED afterwards:

 Please be aware that during the cloning process mobile users will not be able to connect to your Linchpin Data Center instance as long as the Gateway connection is disabled!

Prepare your instance for cloning (Linchpin Intranet Suite 5.1.0 and newer)

Clone detection is no longer available for Confluence Data Center instances with Linchpin Intranet Suite 5.1.0 since it is no longer needed. Instead, please make sure to disable (not reset!) the Gateway connection for your Linchpin Data Center instance to be cloned by going to the following URL as a Confluence administrator:

https://[YOUR_CONFLUENCE_BASE_URL]/admin/plugins/linchpinmobile/connection.action

You can disable the connection by pressing the toggle button in the top right corner of the connection status panel. The connection status should display as DISCONNECTED afterwards:

 Please be aware that during the cloning process mobile users will not be able to connect to your Linchpin Data Center instance as long as the Gateway connection is disabled!

Cloning your instance

You can now go ahead and clone your Linchpin Data Center instance.

How to proceed after cloning your instance

After cloning is completed reset the Linchpin Mobile Gateway connection on the clone instance. This prepares the cloned instance for setting up a new connection to the Linchpin Mobile Gateway if necessary.

On your original instance you can now enable the Linchpin Mobile Gateway connection again to make sure users are able to connect to your Linchpin Data Center instance when on the go. You can enable the connection by pressing the toggle button in the top right corner of the connection status panel on the following URL:

https://[YOUR_CONFLUENCE_BASE_URL]/admin/plugins/linchpinmobile/connection.action

The connection status should display as CONNECTED afterwards.

Linchpin Server

Prepare your instance for cloning

Before cloning your Linchpin Server instance, please make sure that the instance to be cloned has 'Duplicate Instance Detection' switched on. You can check this setting as a Confluence administrator by going to the following URL and scrolling to the bottom of the page:

https://[YOUR_CONFLUENCE_BASE_URL]/admin/plugins/linchpinmobile/connection.action

Cloning your instance

After making sure the 'Duplicate Instance Detection' is switched on, you can go ahead and clone your Linchpin Server instance. The 'Duplicate Instance Detection' feature makes sure that none of your clone instances connects to the Linchpin Mobile Gateway with the same Instance ID as your production system.

How to proceed after cloning your instance

After the cloning of the instance is completed, the 'Duplicate Instance Detection' can be switched off again on the original instance. Please make sure not to reset the 'Duplicate Instance Detection' but to only switch it off.

On the cloned instance, however, you should reset the 'Duplicate Instance Detection' as well as the Linchpin Mobile Gateway connection. This prepares the cloned instance for setting up a new connection to the Linchpin Mobile Gateway if necessary.