Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Please share the document,If you made any such type of setup.
Thanks,
Lakshmikandh
Hi @prashanthi_gn
Is it shared persistence? (I am presuming it is). If it is then I will look to do the following. Move the PostgreSQL to its' own dedicated environment (move it away from central node). You can set up replication of that DB to a slave node.
Official Documentation on the replication streaming - https://www.postgresql.org/docs/9.6/protocol-replication.html
A great blog on how to achieve it - https://blog.raveland.org/post/postgresql_sr/.
Also move your file share to a dedicated file storage (if its not already set up that way). If you are on public cloud such as Azure - you can use Azure File Share, which allows you to create and automate backup of the storage in relatively simple steps . Idea is to isolate the File Storage and the DB so you can keep them in isolation of your central nodes, in case any issues with central node, you still have access to them.
This will move the headache of importing the application to the rim nodes manually.
Hope this helps you with you setup.
So basically the datasources to backup are:
Is that correct?
@witty - Yes, The PostgreSQL DB and the File share. Data source is not usually part of the Qlik Sense site backup process, but if they are in your environment (QVD, Flat Files etc) then yes you can back them up at the same time.