Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Gestion-PSD
Creator II
Creator II

Move QSR database to other drive in same server

Hi everyone,

We're facing disk space warnings  in our of QS virtualized servers. We'd done some procedures to liberate disk space, but we'd found than Qlik Postgres database is almost 30% of disk, and 50% os disk usage.

Reducing database weitgh nor increasing C: space are not options.

We know we can move DB to other drive in same server, but we don't know which QS config file/s we must edit in order to QS knows where the DB is after moving it.

 

Can someone help us?

Thanks in advance.

Labels (2)
1 Solution

Accepted Solutions
rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Hi,

then you should follow what is wrote here and operate completely as if the repository is on another machine: http://help.qlik.com/en-US/sense/June2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Depl...

Once the new repository is ready (populated and everything) the only thing left is modifying the Shared persistence database connections settings, which can be performed with QlikSenseUtil: https://support.qlik.com/articles/000046014
Most likely I would prepare a new server and then configure everything starting from the repository and then proceding installing QS

Riccardo

View solution in original post

6 Replies
rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Hi,

one way is to use junctions: https://support.qlik.com/articles/000007284 
Please note that Qlik's Support doesn't support those configurations...

Anyway, I would suggest to take a look at the repository and find out if it's possible to clean something: https://support.qlik.com/articles/000052404 or https://support.qlik.com/articles/000065033

Hope this helps,
Riccardo 

Gestion-PSD
Creator II
Creator II
Author

Thanks Riccardo.

As I'd said previously, we can't clean more space using "traditional" ways. There aren't _deletedentitylog tables. They did exists, but we deleted them time ago.

We think there must be another way than junctions, as there exists the possibility of install Postgres DB in other server (also not supported by Qlik).

We know if Postgres is installed in a standalone server, it is neccesary to change some options in QS configuration (one or some config files). So, if Postgres is installed in the QS server but in another drive, We think we must change those options in those files. But we don't know the files to modify and the exact changes to do in them.

We're looking for a solution in that line.

Thanks!

rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Hi,

then you should follow what is wrote here and operate completely as if the repository is on another machine: http://help.qlik.com/en-US/sense/June2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Depl...

Once the new repository is ready (populated and everything) the only thing left is modifying the Shared persistence database connections settings, which can be performed with QlikSenseUtil: https://support.qlik.com/articles/000046014
Most likely I would prepare a new server and then configure everything starting from the repository and then proceding installing QS

Riccardo

Gestion-PSD
Creator II
Creator II
Author

Thank, Riccardo.

 

We'll try it and i'll post the results.

Levi_Turner
Employee
Employee

As @rzenere_avvale has gestured to, the ultimate answer is that you will need to:

  1. Install a standalone version of PostgreSQL
    1. The latest 9.6 from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads is the route to go
    2. During the installation:
      • Specify the datadir to be another drive
      • It'd be ideal to use all the same settings from bundled Qlik Sense DB (port, superuser password)
        • If you do use the same port, obviously both cannot run at the same time.
    3. Post installation:
    4. If you did retain all the same settings, then you do not need to edit the encrypted connection string, but if you did change settings, then using QlikSenseUtil on all nodes will be needed.
    5. Ensure the PostgreSQL standalone service is running first then start Qlik Sense normally
      • Since both PostgreSQL instances will try to use the same port I'd wager the bundled one would fail to initialize fully, which is what you want
    6. Validate
    7. On the Central node if things are successful then:
      • Uninstall but do not check the Remove certs / apps / etc
        • We're just removing Program Files, basically
      • Once the uninstall is finished, move / delete C:\ProgramData\Qlik\Sense\Repository\PostgreSQL
      • Reinstall
    8. Success
Gestion-PSD
Creator II
Creator II
Author

Thanks Levi,

But we're looking for an easier way to do that not including reinstall QS nor Postgres.

Finally, we did it copying Postgres folder to D and change the path to executable of QSRDatabase service, pointing to new D folder and it works almost fine.

I said 'almost fine' because we're facing troubles with centralized logs (Loggin on QLogs database). Qlik Logging Service doesn't start, we think because users and passwords defined in

C:\ProgramData\Qlik\Sense\Log\QlikCentralizedLogging.config

don't match.

But this maybe is a not related issue. It would be failing since QS upgrade or earlier and we didn't realize.

 

Thanks all!

PS: Edited. Dammed emojis.