Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video demonstrates how to restore the Qlik Sense Repository Database or QRS from a backup.
Here is a link to more information in the Support Knowledge Base:
How to backup or restore the PostgreSQL database in Qlik Sense
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
#QlikSupport
Video Transcript:
Hi and welcome to Qlik Fix.
This video will demonstrate how to restore the Qlik Sense Repository database or QRS from a backup.
First, verify that only the Qlik Sense Repository database service is running on the machine.
The existing database will need to be removed prior to restoring the QRS backup.
This can be done using PG Admin – a standard database utility.
Open up PG Admin
Create a connection to the server machine hosting the Qlik Sense Repository database.
Port 4432
Postgres user and password.
Here you can see all of the tables where Qlik Sense stores data in the current database that will be dropped.
In PG Admin you could do this with the Delete/Drop option.
I’ll be using these commands copied from the Qlik help site.
Open a command prompt with Administrator privileges from the PostgreSQL 9.6 bin folder.
Copy and paste in the command
Connecting locally,
On port 4432
With the postgres user defined while installing
And dropping the current QSR database.
No other tasks should be running in parallel, so I’ll disconnect PG Admin.
Enter the password
And back to PG Admin to verify that the database has been removed.
You can see that QSR is gone.
Now, copy the Create DataBase command from the Documentation.
The Template0 will create a basic schema, but there will be no tables.
Copy
Paste and run the command
Done.
Back to PG Admin to illustrate.
The QSR has been created with a public schema, but with no tables.
Now we’re finally to the step of restoring from the backup.
This could be done in PG Admin via the Restore command,
Point to the backup tarball, hit restore,
But again, this is a demo of the manual method.
Copy the restore command.
You can see a variable here to the path to the backup file
Copy everything up to that point
Navigate to the QSR backup on an accessible shared drive folder.
Copy the backup locally.
This folder has been created on the local C drive called QSRBackup
An easy way to get the file path is to press Shift and right click,
then select “Copy as path”
Paste it at the end of the command
I recommend adding a “-V” to the command line so that you can actually see some more verbosity to what is happening.
Again, close any tasks or open connections to the database.
Enter the password
And there it goes.
To verify that the data is actually there,
Back to PG Admin one more time.
In the QSR database under tables, now there is all the content.
The QSR has been fully restored.
I hope this helped.
If you'd like more information
Search for answers using the Unified Search
tool on the Support Portal.
it searches across the Support Knowledge Base,
Qlik Community, Qlik Help site and Qlik YouTube channels.
Take advantage of the expertise of peers, product experts and technical support engineers
by asking a question in a Qlik product forum on Qlik Community
And don't forget to subscribe to the Support Updates Blog.
Thanks for watching!
Nailed it!
Hi,
Can someone help me DB backup, when i'm trying to take backup i'm just getting 2kb of data.
What was the issue and how to resolve it?
Thanks in Advance!!!
Hello @Admin3 !
We have this article that hopefully can help you walk through the backup process: How to backup or restore the PostgreSQL database in Qlik Sense
If that does not help resolve the issue, I recommend posting the issue you are facing in the Qlik Sense Deployment forum to leverage our active community.
Hi @Sonja_Bauernfeind ,
Sorry for the delay reply, now steps works properly and i'm able to take QSR backup.
Thanks!!!
Hello, before doing the above please ensure that you have the ability to roll back to a previous production instance. This process is not without risk, and nor should it be used as a reliable process. There are lots of variables at play and anything could go wrong. If you have any concerns at all it is best to ask for the support of experts.