In addition to using synchronized persistence in a multi-node installation, in Qlik Sense 3.1 SR2 there is now an option to use shared persistence. This means that nodes share a single repository database and a network folder for the application files. You can either share the central node repository and application storage, or setup dedicated machines for repository and application storage.
More details about advantages and limitations of Shared Persistence are available in the documentation "Qlik Sense Shared Persistence" attached to this article along with instructions on how to install and configure a new environment and move from an existing deployment.When should shared persistence be used?
In Qlik Sense 3.1 SR2 Shared Persistence is available along-side multi-node sync and while it is recommended to begin any new multi-server installs on shared persistence it is not mandatory to migrate existing deployments at this time (although this may change in the future).
If you are planning a new multi-server deployment or already have one in a prior version then consider the following:
Shared Persistence and Single Nodes.
- If you have an existing deployment and want to remain on sync then you can simply run an in-place upgrade which will retain the existing sync configuration with no additional work
- If you are planning/deploying a new multi-node deployment, then it is recommended to use shared persistence from the start
- If you have an existing multi-node sync deployment and are experiencing issues with performance or reliability, then it is recommended to consider moving to Shared Persistence
Shared Persistence is a solution for using multiple machines in a site, while it is not as relevant to single machine installs, you will be asked for the settings related to this feature during a clean installation of a single machine to be prepared for any future expansion. An upgrade of an existing single node will not enable this feature and so shared persistence can be ignored.
The attached documentation includes steps on how to set up Shared Persistence for the following scenarios:
- Set up a new Qlik Sense 3.1 SR2 environment with database and shared folder on one of the nodes.
- Set up a new Qlik Sense 3.1 SR2 environment with database and shared folder on a separate machine.
- Upgrading an existing Qlik Sense multi-node environment 3.1 and older* using synchronized persistence to Shared Persistence (Upgrading from a version older than 2.0.x is not a tested scenario and it is recommended to upgrade first to Qlik Sense 2.x to migrate the repository and then to move to Shared Persistence following instructions)
- Migrating an existing Qlik Sense 3.1 SR2 environment using synchronized persistence to Shared Persistence
- Upgrading an existing Qlik Sense 3.1/3.1 SR1 already using Shared Persistence (Shared persistence was available as a hidden feature in those versions)
Please also read Tips when using shared persistence
for things to keep in mind when setting up/using Shared Persistence.