Restoring a site manually

This section describes how to restore a Qlik Sense site in a default installation where a PostgreSQL database is used as the repository database.

The procedure described in this section can also be performed using the Repository Snapshot Manager (RSM).

See: Using the Repository Snapshot Manager

Items to restore

The following items need to be considered when restoring a site:

• Qlik Sense software

• Repository database: The database contains all configuration data for the site.
• Certificates for the Qlik Sense services: The certificates are used to encrypt the traffic between the services and the users. Make sure to backup the certificates in order not to lose any encrypted data (for example, passwords for data connections).
• Log data
• Application data: The data models in the Qlik Sense apps.
• Any content that supports the apps (for example, QVD files)

Restore procedure

Proceed as follows to restore a Qlik Sense site:

1. Install the Qlik Sense software on the machine targeted for the restore.

See: Installing and upgrading Qlik Sense

Warning noteA restore can occur onto a machine with a different name than the one from which the data was backed up. However, if the machine is a central node in a multi-node site, changing the machine name requires all rim nodes to be reset, which means that the nodes will have to be re-added.
Warning noteMake sure to deselect Start the Qlik Sense services when the installation has completed during the installation setup. If the services are started, new certificates and a new repository database are created and they must be removed before proceeding with the restore procedure.
2. Restore the certificates used to secure the Qlik Sense services.

See: Restoring certificates

Warning noteDo not start the Qlik Sense services at the end of the Restoring certificates procedure.
3. Start the Qlik Sense Repository Database (QRD).
4. Restore the repository database:
   1. Place the backed up repository database on the machine targeted for the restore.

   2. Open the Command Prompt in Microsoft Windows.

   3. Run the following commands to restore the repository database (adjust the paths as needed):

      1. cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\<database version>\bin"

      2. createdb -h localhost -p 4432 -U postgres -T template0 QSR

      If the command fails because a database already exists, run the following command and then repeat the createdb command:

      dropdb -h localhost -p 4432 -U postgres QSR

      3. pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\QSR_backup.tar"

5. Restore the content to the following folders folder:
• %ProgramData%\Qlik\Sense\Apps
• %ProgramData%\Qlik\Sense\Repository\Content
• %ProgramData%\Qlik\Sense\Repository\Extensions
• %ProgramData%\Qlik\Sense\Log
6. Restore any supporting content to its original location as required.
7. If you are restoring a multi-node site, ensure the integrity of the site.
Information noteThis step is only applicable to multi-node sites.

This is needed as any new content on the rim nodes is not synchronized back to the central node upon restore, which may result in an inconsistent site.

There are two ways to ensure the integrity of the site:

• Without resetting the rim nodes: On every rim node, connect to the QRS API and call the POST /qrs/sync/snapshot/restore endpoint without any parameters or body.

Connection examples

• By resetting the rim nodes: Wipe all rim nodes completely and re-add them back into your multi-node environment. The rim nodes will be up to date with your latest restore after the synchronization is complete.
8. Start the Qlik Sense services. If the services are started manually, start them in the following order:
Information noteThe user that installs and runs the Qlik Sense services must be local administrator on the machine.
1. Qlik Sense Repository Service (QRS)
2. Qlik Sense Proxy Service (QPS), Qlik Sense Engine Service (QES), Qlik Sense Scheduler Service (QSS), Qlik Sense Printing Service (QPR), and Qlik Sense Service Dispatcher (QSD) in no specific order

The order is important because the QRS is dependent on the QRD and the rest of the services are dependent on the QRS.