Upgrading Qlik Sense 3.0 to June 2017

[dwighttrumbower]

I'm wondering how difficult the upgrade to June 2017 is from a 3.0 version?  Are team has experience upgrading enterprise software in the Windows and Java world. I'm assuming if you follow the steps outlined from Qlik it should be fairly straight forward.

Do the apps have to be reprogrammed or will the install take care of that?

Thanks

Dwight

[Giuseppe_Novello · Accepted solution]

1- Read Release notes: 

https://da3hntz84uekx.cloudfront.net/QlikSense/11.11/0/QlikSense_June_2017_ReleaseNotes.pdf

2-  Read System Requirements:

https://help.qlik.com/en-US/sense/June2017/Subsystems/PlanningQlikSenseDeployments/Content/Introduct...

3- The backup process: 

>> You can do the VM snapshot or you can backup Qlik, it is your choice. 

Manually ( since you are in 3.0 or 3.1) - 

Software and files: https://help.qlik.com/en-US/sense/3.0/Subsystems/PlanningQlikSenseDeployments/Content/Server/Server-...

Certificates: https://help.qlik.com/en-US/sense/3.0/Subsystems/PlanningQlikSenseDeployments/Content/Server/Server-...

4- Upgrade process:

Any Service Release of 3.2 track should be fine, I’ll use 3.2.4:

3.0.X > 3.2.4 (Upgrading and keep Sync Persistence, read “Upgrading a site with synchronized persistence“ )

https://help.qlik.com/en-US/sense/3.2/Subsystems/Installation/Content/InstallationLicensing/Upgradin...

 a - Once in 3.2.4, Run the recursive Cleanup Script , Please read attached article name “ No Hub or QMC access after upgrade to Sense November 2017 or higher - recursive script” à once you run the Script DO NOT START THE SERVICES AND MOVE TO THE NEXT STEP.

 Read more:  https://support.qlik.com/articles/000017620

3.2.4 > June 2017 (Upgrading from Qlik Sense 3.2  later to Qlik Sense June 2017 to Shared persistence, the installer will switch you, but there are some prerequisites, that needs to be taken prior upgrading)

https://help.qlik.com/en-US/sense/February2018/Subsystems/PlanningQlikSenseDeployments/Content/Deplo...

5- Time: 

The time would be variant depending how big is the environment and number of nodes, but I would place 1 - 1.30 hr for the central node for the first version hope 3.1 > 3.2 and 1 hr to upgrade 3.2 to June 2017. 

As always, we tell the customers to always backup, please do not skip that process. Also, we explain that if they do not feel comfortable to upgrade, it is best to engage consulting services for assistance. Do all the process at your own risk, and expectation that you will follow ALL steps are listed. 

[dwighttrumbower]

Giuseppe_Novello Thank you for info.

There is no licensing issue if one where to copy the existing server to a new VM.

Do the upgrade on the new VM and when done point everyone to new VM and then turn off old VM. 

Correct?

[Giuseppe_Novello]

Now migrating to a different server, now that could be tricky. License wise, it is not a issue but it will be a violation of license agreement since you are using 2 machines with the same license; however, it shouldn't cause any problems. 

BR

Gio

[dwighttrumbower]

But the original VM  would be destroyed after a successful upgrade.