Keeping Your Qlik Sense Installation CurrentArticle Number: 000045075 | Last Modified: 2018/06/08
- Discuss Best Practices for upgrading Qlik Sense
- Demo installing and rolling back patches
- Troubleshooting common upgrade issues
- System Requirements: http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Introduction/system-requirements
- Backup: http://help.qlik.com/en-US/sense/November2017 /Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Backing-up-a-site.htm
- Upgrade Process: http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Upgrading.htm
- Migrate from Sync to Shared: http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Migrating-from-synchronized-to-shared-persistence.htm
- Installing Patch: http://help.qlik.com/en-US/sense/November2017 /Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Patching-qlik-sense.htm
- Restore: http://help.qlik.com/en-US/sense/November2017 /Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Restoring-a-site.htm
- STT – Moving to Shared Persistence: https://www.youtube.com/watch?v=qfDfwpSMLHs
Q&A - Keeping Your Qlik Sense Installation Current
Q: What is Qlik Logging database?
A: More information about Qlik Logging database can be found here:
Q: If I want to install patch 2, do I have to manually remove patch 1? Can I not go directly to patch 2, which I would assume can uninstall the older patch?
A: No, you do not have to. The installer can remove the previous patch. Removing the patch manually is a recommendation as we have seen cases where the installer could not remove it.
Q: Is there a possibility to get an information when a new patch is availabel?
A: Yes, each time a patch is released, there is a post on our support blog https://community.qlik.com/blogs/supportupdates
Q: Questions about making a backup in multinode env with shared persistence: RIM node with Engine role only does not have postgresql database running or any application files . What should I back up from such a RIM node?
A: On the rim node you can generally backup the certificates as well as the current Qlik Sense logs.
Q: we have an environment with 2 nodes on Sense 3.0.0. The second node services keep stopping without any reason, is this a known issue? should we upgrade even if we have this issues with node 2?
A: This is not a known issue and there might be several root causes. I would advise to log a support case to investigate the issue before upgrading to a new release.
Q: Is there any order to follow in stopping services? Sometimes Repository Services comes up again without our notice, what to do in that case?
A: The recommendation to stop is documented here (bottom of the page) http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Services.htm. If the Repository Services comes up again this generally means that one of those services Qlik Sense Engine, Proxy, Scheduler, Printing did not stop properly and windows tried to start them back automatically. Considering the Windows Event logs might be useful in this case
Q: Why should be the dispatcher stopped as the last service?
A: Please check this link (bottom of the page) http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Services.htm
Q: When patching a clustered environment, is there a prefered order of nodes?
A: You should always start with the central node. For the rim node there is no specific order.
Q: Should we stop services on Rim nodes as well, in multinode environment before Applying Patches to Central node?
A: Yes. Every node need to be stopped before starting the patch process
Q: We are running June 2017. Can we go directly to November 2017 patch 3?
A: You will need to first upgrade to Qlik Sense November 2017 and then install Patch 3
Q: During the backup process, i observed if there are issues and the Admin is not familiar with postgreSQL it will be a problem. How can we avoid such things?
A: The repository backup process is based on Postgres command. If any issue occurs during this process you can first consider our knowledge base or postgres documentation to see if the error message you got is documented.
Q: could a .bat or something be created to stop the services in the correct order?
A: Yes. Make sure you run this batch with Admin Privileges.
Q: Should I run patch installation under the same account as Qlik services are running under or any administrator account will be OK?
A: Any Administrator account should work. It's better with the Qlik Sense Service account but not mandatory
Q: How to know if actual installation run on synchronized or shared persistence?
A: I would advise to look into this article from our knowledge base: 000033855: How to identify Synchronized and Shared Persistence installation
Q: How to deal with Qlik Services failed to stop?
A: There might be several reasons for this behavior. Suggestion would be to check the Windows Event logs as well as the Qlik Sense logs for the specific service failing to stop. This should give you an error or reason.
Q: Hi, could you please point out the exact list of backup folders?
A: This list can be found here. http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Backing-up-a-site.htm
Q: Do we need to run sense cleaner script before starting the upgrade?
A: If you are running Qlik Sense 3.2.x or earlier yes you can run. This script is not working anymore from Qlik Sense June 2017 and later so no need to run if you are running on of those versions of Qlik Sense.
Q: should we always uninstall previous patch before new one?
A: This is not mandatory but recommended. The installer of the new patch will do it itself if it detects any previous patch installed on the system.
Q: Is there a silent mode for updating form the command line?
A: You can silently upgrade to a new release following: http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Upgrading-Major-Silent.htm. For patch it's not yet available.
Q: Is it possible to migrate a repository from an older version (3.1 SR2) to a newer (Sep17)?
A: If you are talking about applying the restore process to a Qlik Sense September 2017 environment from a backup taken on a Qlik Sense 3.1.2 environment, answer is NO. Backup/Restore needs to be done on the same version.
Q: what are the best practices concerning service accounts? Just one per instance? One per node? Other combinations?
A: We would recommend having the same service account for every node because it's simpler to administer NTFS permissions and Shared permissions.
However, is required you can run the different service account on each node as long as those account have full control permission on the shared folder
Q: We have a very old installation (3.0). Is it better to go the way "Upgrading to Qlik Sense June 2017 or later from Qlik Sense versions earlier than 3.1 SR2" from the help.qlik.com site or do a complete uninstallation of Qlik Sense incl. Postgres DB?
A: If you apply the second option you will lose everything (Apps, Server object, configuration,... so I would recommend to follow our guide "Upgrading to Qlik Sense June 2017 or later from Qlik Sense versions earlier than 3.1 SR2"
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.