Qlik Community

Ask a Question

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
LINKEDIN LIVE: Democratizing data to enhance customer-centricity. JULY 29TH REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
Shagil
Contributor
Contributor

Qlik Sense - Which PostgreSQL Databases need to be backed up

We are looking to back up the PostgreSQL databases for recovery in case of a database crash. I have referred to the following (and a few other) links for backup and restore:

https://help.qlik.com/en-US/sense/June2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Dep... 

This article mentions backing up QSR and QLogs databases, but there are a few other databases on the Server, namely, Licenses, QSMQ, and SenseServices. So, I have two queries in relation to this:

1. Do we need to backup all of these databases (Licenses, QSMQ, and SenseServices) for a successful restore of the required databases to have Qlik Sense services and Apps up and running as before the database crash?  

2. Is it important to backup the logs in QLogs database, considering this database is very large? We are thinking to backup only the schema for this database. If something does go wrong then we are okay to lose the logs (or part of it), unless if losing the logs leads to any type of inconsistency affecting user experience. 

Labels (3)
1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

The QSR is the minimum viable DB for a restoration procedure. The other ones are generally not needed. To understand when they are needed you need to know where they are used. Whether their uses are important is up to the administrator:

  • Licenses: Used to store a trail of license allocations when using a Signed License Key. Can be recreated.
  • QLogs: Logs stored via the Qlik Logging Service. Fundamentally duplicative of the log files on disk. May be required in sites where this data is ingested by other systems
  • QSMQ: Used as a message queue between micro-services. Message queues are transient. Can be recreated.
  • SenseServices: Stores persistent data from
    • app_distribution_service, hybrid_deployment_service: used in hybrid scenarios where the site is distributing to Qlik SaaS. If not present, then recreation of deployments will be needed in the MSC.
    • precedents_service: Used by the Insight Advisor. If not present, persistent history of insights generated will need to be re-generated.
    • qlik_mobility_registrar_service, qlik_notifier_service: Used by the System Notifications capability to send alerts to registered devices running the Qlik Sense iOS / Android app.

View solution in original post

1 Reply
Levi_Turner
Employee
Employee

The QSR is the minimum viable DB for a restoration procedure. The other ones are generally not needed. To understand when they are needed you need to know where they are used. Whether their uses are important is up to the administrator:

  • Licenses: Used to store a trail of license allocations when using a Signed License Key. Can be recreated.
  • QLogs: Logs stored via the Qlik Logging Service. Fundamentally duplicative of the log files on disk. May be required in sites where this data is ingested by other systems
  • QSMQ: Used as a message queue between micro-services. Message queues are transient. Can be recreated.
  • SenseServices: Stores persistent data from
    • app_distribution_service, hybrid_deployment_service: used in hybrid scenarios where the site is distributing to Qlik SaaS. If not present, then recreation of deployments will be needed in the MSC.
    • precedents_service: Used by the Insight Advisor. If not present, persistent history of insights generated will need to be re-generated.
    • qlik_mobility_registrar_service, qlik_notifier_service: Used by the System Notifications capability to send alerts to registered devices running the Qlik Sense iOS / Android app.

View solution in original post