Qlikview server Migration

[TusharDev_Qlik]

@Chip_Matejowsky 

We have multi-node QlikView environment where we have divided the services between Qlikview servers and Publishers. We need to demise only the Qlikview servers and replace them with new QVS servers. We are not making any changes in the publisher servers and they will remain same. Please suggest best approach to implement this.

[marcus_sommer]

It's not quite clear what do you want to do - migrating QlikView to new machines or upgrading the QlikView release (from  which to which) or maybe both?

- Marcus

[TusharDev_Qlik]

Hi Marcus ,

So we have 4 servers(2 publisher and 2 Access point Servers) architecture out of which we are moving 2 QVS  to brand new servers keeping the other 2 publisher servers as it is. Hope this explains my issue.

Note: This is not a version upgrade. 

`

[marcus_sommer]

AFAIK the entire communication between the QlikView services depends on the server names. Therefore remaining by them should simplify the task. I don't have a multi-server environment but my previous migrations worked each time very well by copy & paste from data & application + all configurations from all the program-data parts (QlikView, OS tasks, various driver and connectors - depends on your environment).

Important is that you stop all processes before copying the configurations and applying them - with needed adjustments, for example in the case you have different server-names - before you start the services. Maybe it's also an alternatively to create an image from the environment and using it within the new server.

- Marcus

[Chip_Matejowsky · Accepted solution]

Hi @TusharDev_Qlik,

To confirm, you're swapping out the Windows servers on which the QlikView Server (QVS) nodes are installed, and you're not upgrading the QlikView Server/Publisher version at this time, correct?  What other QlikView services are installed on these QVS nodes?

Is the QlikView Management Service installed on one of these QVS nodes?  If not, then the process shouldn't be too difficult.  

1. Back up the existing QVS nodes - Backup and upgrade preparation (note the folders/files regarding QVS)
2. Install QlikView Server on the new Windows servers
3. Restore the QVS related content to the new Windows servers
4. In QlikView Management Console (QMC) > System > Setup > QlikView Servers > @QVS > General tab > Url update to the new servername qvp://<servername>/
5. Edit all .xml files in the following folders, replacing all references to the previous machine names with the new machine names.
   1. %ProgramData%\QlikTech\ManagementService
   2. %ProgramData%\QlikTech\ManagementService\QVPR

It's very important that you test this once or twice in a test environment first prior to performing in your production environment to ensure a smooth transition.  If you need direct assistance with this, reach out to your Qlik Account Manager and they can help in scheduling an engagement with Qlik Consulting Services.

Best Regards

[TusharDev_Qlik]

Thank you so much for the quick response.

You're not upgrading the QlikView Server/Publisher version at this time, correct? --Yes

What other QlikView services are installed on these QVS nodes?--QVS, QVWS and DSC

Is the QlikView Management Service installed on one of these QVS nodes? --No

We use alias for the server names instead of Computer name so it will not be an issue I guess.

[Chip_Matejowsky]

Okay.  You'll want to ensure you back up all of the folders/files for the other QV services residing on these Windows servers - QVWS and DSC - as well as QVS then.  As I said, it's important to perform this server move in your test environment first before doing so in production.

[TusharDev_Qlik]

Hello @Chip_Matejowsky 

what measures must be taken in this scenario to ensure all DOC and Named Cal's are preserved in new QVS servers?

Our SAN drives where all source and user documents are hosted are also changing to the new SAN drives.

Will this impact the allocated licenses?