For whatever reason, at some point you may need or want to move or transfer your Statelake system and/or configuration files onto a different server, individual stand-alone computer, or even just another environment on the same server.

There are multiple steps that need to be undertaken to do this successfully. But don’t worry - it actually quite easy.

But before any steps are taken, the first and perhaps most important thing is to understand what you want to achieve and then determine exactly what needs to copied, backed up, or moved, and what set-up will be the best.

You may be moving from one of the following scenarios as a source, to a different scenario as your target set-up, so there may be different components required depending on the target scenario selected.

A series of possible scenarios is presented below.

  • Scenario A - The standard default set-up would be a single installation of Statelake, and a single instance of the configuration database holding all of the Statelake components (Connections, Maps etc).

  • Scenario B - Statelake on one application server, with multiple configuration databases on one database server.

  • Scenario C - Statelake on one application server, with multiple configuration databases, each on their own database server.

  • Scenario D - Another scenario is to have a Statelake system and configuration database on two separate servers.

  • Scenario E - Multiple Statelake installations that access their own configuration databases on the same server through the use of Appdata.cfg. Please refer to Configuration Files - The Power of AppData.cfg.

Please refer to Planning The Installation for additional help and advice.

When dealing with live or production data, it is most important that the appropriate precautions are being taken to ensure data integrity.

Before proceeding further, please involve the appropriate system administrators or technical experts who have the correct system privileges, as required.