QlikView: Migrating to a different machine

[Andre_Sostizzo]

Basic instructions on how to migrate a QlikView server installation to a different host. 

If an upgrade is planned, see How to Upgrade or Migrate QlikView 11.20 and later versions.
The instructions in this article have been sourced from the above.

The example is written for a single node environment.

See the QlikView Online Help Upgrading to a different machine for details.
When planning your migration consider how to maintain CAL assignments. See Migrating QlikView Server without losing CAL assignments?

Summary:

1. On the new machine, install a running, licensed version of QlikView Server.
2. Stop all QlikView services on the old machine.
3. On the new machine, remove or rename the %ProgramData%\QlikTech\ManagementService\QVPR folder.
4. On the new machine, remove or rename the %ProgramData%\QlikTech\ManagementService\qvpr_<NewMachineName>.ini file.
5. To retain User Document mounts, copy the %ProgramData\QlikTech\QlikViewServer\Settings.ini file and move it to the new server.
6. Copy the QVPR folder and the .ini file “as is” from the old machine to the new one (that is, keep the folder name).
7. Change all references to <OldMachineName> to <NewMachineName> in the following files:
   
   ProgramData\QlikTech\DistributionService\Configuration.xml
   ProgramData\QlikTech\DistributionService\Registration.xml
   ProgramData\QlikTech\WebServer\Config.xml
   ProgramData\QlikTech\ManagementService\Config.xml
   
   
8. (Only applicable for previous version of QlikView such as 12.30 and earlier) Rename the .ini file (that is, change qvpr_<OldMachineName>.ini to qvpr_<NewMachineName>.ini).
9. Change all references to<OldMachineName> to <NewMachineName> in the QVPR .xml files.
10. Start the QlikView services on the new machine.
11. Do NOT use the QMC to change the Distribution Service Source Document paths, as doing so will potentially break the task links.  If you need to change paths, go directly to the SourceFolderDocumentResource.xml in the QVPR and make the changes directly there to point to the new paths, do not change anything but the path information, as the GUID links must stay the same in order to keep the tasks aligned. An alternative to editing the XML file directly is to use the XML DB Viewer power tool which allows you to search as well as find/replace.  
12. Shut down the old machine.

NOTE: If there have been any changes made to the QMS exe.config file, be certain those changes are documented somewhere, as they will need to be re-applied to the new QMS exe.config file post-upgrade.  The upgrade uninstalls the 11.20 files and installs new 12.xx files, which means the exe.config will be removed and recreated without customizations.  The QMS is unique in that it does not write changes to the programdata path like the other services, so be certain the customizations are documented and reapplied post-upgrade prior to bringing the services back online again.  

[Purushothaman]

@Andre_Sostizzo  

Thanks for the detailed information. I have the same task in my company next week, QlikView: Migrating to a different machine .

Out of curious, have you done Demo video for this activity? If yes, May I request you to share the same.

Many Thanks,

[TusharDev_Qlik]

@Andre_Sostizzo 

We recently followed the steps given above but step no 7 created issue for us.

1. Rename the .ini file (that is, change qvpr_<OldMachineName>.ini to qvpr_<NewMachineName>.ini)

The QMS service was not able to start on the new machine and log suggested it is failing to initialize the database. Is this step no longer required now? Our Qlikview version is April 2020 SR4.

[Sonja_Bauernfeind]

Hello @TusharDev_Qlik 

Thank you for raising this! I will update the article. 

This step is no longer required with newer versions (though it shouldn't break the migration either). Have you confirmed that renaming the .ini rename is what causes the issue? 

See Upgrading to a different machine for general instructions for our current (and supported) versions. 2020 is out of support at this point.

All the best,
Sonja 

[TusharDev_Qlik]

@Andre_Sostizzo 

Yes the QMC service was not starting when you use the qvpr_ini file from old server. When this step is skipped we are able to successfully complete the migration.

We are planning a upgrade to latest version soon as 2020 is out of support.

[Sonja_Bauernfeind]

Thank you for confirming, @TusharDev_Qlik 

[john_oll]

The copying should include
ProgramData\QlikTech\QlikViewServer\Settings.ini
or at least the line DocumentMounts from that file!

Otherwise old folder mounts are not available (and thus tasks not working)!

[Sonja_Bauernfeind]

@john_oll Thanks! I have updated the article.