- Of course this will have an impact on performance. When one of the two publishers is shut down, your QlikView setup will only have 50% of the full reload capacity
- AFAIK if you cluster QlikView Publishers or QlikView Servers or both, the QMC must be shared. Otherwise you will be unable to share the cluster license which consists of one single serial with a number of nodes embedded in the license allowances. Also, without a shared QMS, you won't be able to distribute essential configuration information across multiple Publishers and/or Servers.
Note that clusters are commonly used to distribute loads and make a QlikView architecture scalable (scale out). Clustered environments should be seen as a single QlikView environment, managed by a single QMS/QMC. The added advantage is that nodes (except the last one) can go down while the QlikView environment keeps running. But this fail-safe setup only works if you put all other services on a third machine, so that a single node going down doesn't take vital services like the QVWS or QVS with it. For an overview of a clustered/resilient QlikView Server set-up, see: Clustering QlikView Servers ‒ QlikView and Clustering QlikView Publisher ‒ QlikView
Thanks for your response
Have to set up DR server which should work when the Active (A) is down and adding both the servers in the cluster should work, I think.
But adding both the servers in a cluster and keeping B down will show 2 out of 1 service running at a time in QMC, but when i want to switch over while performing DR just have to bring the services down on server A and up the services on server B, QMC will be shared though.
Should i go ahead of this kind of setup, as this is PROD and don't want to hamper other components
Any suggestion/ solution will be helpful.
P.S this setup is just for reload server