Deployment Scenario

[ali_hijazi]

Hello

We have QlikView server with server cluster of 2 enabled

What is the best way to install QlikView services on the two server machines so that if one of the machines failed over then everything continues normally on one machine (Reload tasks, dashboard etc...)

Currently we have 2 server BI1, and BI2

on BI1 we have all services, and on BI2 we have QV server service and is used for load balancing

Please advise

[Gysbert_Wassenaar]

If one server needs to be able to fully take over the functionality of the other in case of failure then all services must be installed on both machines.

[ali_hijazi]

So we install all services and shut down the ones that are not needed in normal case?

What about qvpr folder? Do we need to have a copy on the two servers? Can they be synchronised

Please advise

[Gysbert_Wassenaar]

Perhaps this discussion helps: Re: Cluster and Distribution architecture for Qlikview enterprise edition

[#5]

If you want implement cluster fail over method, you need to install the the all services on two machines. But you need virtual IP that sits either any server based on availability. You can talk to your network team so they will setup one virtual IP or server like QLIKBV on BI1 and BI2

Next install all the services on the both server BI1 & BI2

Add the server info on the QEMC and and fail over cluster service on windows and switch from BI1 to BI2

[ali_hijazi]

What is the fail over service?

Is it part of QlikView installation?

What about the tasks and qvpr ?

The issue is that we are not starting from scratch we already have a functional QlikView solution with 2 clusters for load balancing but now management decided to have fail over structure

[Peter_Cammaert]

Picture 2 on page 3 of the document that Gysbert is pointing to. Note that this is just a picture detailing the setup of a resilient QlikView Server set-up, not a Publisher.

The QlikView Server Reference manual contains the same and more pictures and explanations in Chapter 17 (Clustering Servers) on page 101 and in Chapter 18 (Publisher) on page 110. As you can deduce from these two pictures, clustered Server & Publisher are living-apart-together - and communicate through the network, the NAS (for documents and task folders = QVPR) and through configuration. If you want to duplicate all live services (do not shut them down, or you will get a cold-standby set-up that needs to be powered up every time one service goes down.), make sure that you park your QVPR in a shared spot i.e. on a Windows file server or a SAN.

If you go that far in making your set-up resilient, don't forget that there is a third party that needs to know about its brethren: the DSC. Otherwise you'll get weird double identical identity lists in QMC.

Peter