Qlik Sense: Backup With Minimum End-User Impact

As described in Qlik Sense Help on Backing up and restoring a site, the key requirement for successful backup is to stop all services. This means that the environment is forced to a short period of down time when back up is executed. 

It is theoretically possible to take backup of the repository (PostgreSQL) database without stopping the service. It is not possible to ensure that app files and static content are in the same state as the database, if Qlik Sense services are not stopped prior to backup.

All Qlik Sense services must be stopped to ensure that database, app files and static content are in the same state in backup. Important, on a multi node environment all services on all nodes must be stopped prior to backup. 

The only way to accomplish this is to stop all Qlik Sense related services prior to backup.

It is recommended to plan backup window for a time of day when end-users are impacted as little as possible. Backup of repository service typically takes a few minutes, while backup of the Qlik Sense folders takes more time depending on the file size and speed of backup process. 

Environment:

• Qlik Sense Enterprise all versions

See Reference Articles:
Migrating Qlik Sense 3.x.x Shared Persistence to a new server
Migrating Qlik Sense 3.x.x Synchronized Persistence to a new server