Qlik Community

Ask a Question

Support Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Qlik Highlights 2020 Giveaway! Watch, reply and have a chance to win a $200 Amazon Gift Card! Watch Video

Qlik Sense Share Storage options and requirements

Digital Support
Digital Support

Qlik Sense Share Storage options and requirements

Qlik Sense Enterprise on Windows is reliant on the availability and performance of its server cluster share, where the Qlik Sense apps are stored. 

In some instances, the file storage maybe not be compatible with the requirements of Qlik Sense, and this can lead to app corruption.

An example of this may be a Distributed File System (DFS) managed share with replication enabled, which can have side effects such as app corruption, apps being removed from disk, and/or not correctly replicated.

Environment:

Qlik Sense Enterprise on Windows, all versions
 
 

In a Qlik Sense Enterprise on Windows site, a file share is used to store the binary app data including the data models and dashboard sheets. It can be located on one of the nodes in the Sense site or located on a dedicated file server for better resilience and performance. 

Note: Each Qlik Sense Enterprise on Windows site require its own file share with its own set of binaries, archives, extensions, etc. If two mirrored environments are configured to use the same files in only one share, besides potentially experiencing file locking issues, the Qlik Sense database will not have the correct references (metadata) pertaining to the information stored in the share. So you will have two Qlik Sense environments updating files on the shares and which are not aware of updates performed by the other environment(s). Performing such action is highly unsupported and will cause malfunction.

See Qlik Sense for Administrators: Persistence for more details on requirements for a file share. 
In the case of DFS managed shares, the replication feature on file level can lead to inconsistency with the Qlik Sense apps stored on disk. 

Note: Qlik cannot verify support for all storage vendors and Qlik recommends that customers test their preferred infrastructure. In the event of an issue arising that is attributed to storage, Qlik Support may request that customers attempt to replicate the issue on a Windows hosted file share.

Deployment Examples:


Conventional Windows File Share (on-premise)

A windows host is used to serve a file share with storage from local disks or SAN.

 
File Share example01.png

Resilience: 
  • Use virtualization (e.g. VMware) for the file share OS and benefit from features in the platform to keep the node up or return to use quickly (RTO of 4 hours is simple here)
  • If available, using Windows clustering to provide HA for a file share. (requires AD and suitable SAN)
  • Otherwise, backup and restore

Tested by Qlik.

Conventional Windows file share but hosted in AWS

As above but using Amazon EBS volumes mounted to Windows
 
File Share example02.png
 
Resilience: 
  • Use virtualization (VMware) for the file share OS ie benefit from features in the platform to keep the node up or return to use quickly (RTO of 4 hours is simple here)
  • If available, using windows clustering to provide HA for a file share. (requires AD and suitable SAN)
  • Otherwise, backup and restore
  • Amazon EBS volumes feature snapshot capabilities to aid restore process and the failover process can be automated to have a rapid recovery. EBS volumes can be mounted to new instances quickly
Tested by Qlik.

SMB file share served by a Physical NAS

A physical NAS device server an SMB share, such as:
  • NetApp ONTAP 8.2
  • Dell Fluid FS
Resilience: 
  • High availability handled by the individual hardware vendor 
Labels (1)
Version history
Revision #:
3 of 3
Last update:
‎2020-10-28 11:33 AM
Updated by:
 
Contributors