Going for shared persistence?

[jaisoni_trp]

For various reasons/bugs Qlik is recommending to upgrade Sense environment to Shared Persistence. There are significant architecture changes which comes with 3.1 and wanted to have customers opinion if you are ok upgrading the environment to 3.1 from 3.0. What are the challenges you have come across, any insight you could share.

[jaisoni_trp]

In case you are  talking about decommissioning of synchronized persistence.

Qlik Sense 3.2 Service Release 1 now available

Please pay particular attention to pages 18 and 19 in the release notes which deal with the current technical requirements and deprecation of Synchronized Persistence planned for the next Sense feature release.

[alexbjorlig]

Accodring to the article Jai Soni linked - is it not synchronized persistance that will be depreceated and not shared persistence? Or did I miss something?

[simondachstr]

Sorry - that was a mixup! I have corrected my comment. Thanks for pointing out

[alexbjorlig]

No problem. I was just reading this post and was super confused Btw - do you know if it is possible to upgrade from replication to shared persistence?

[Anonymous]

For large deployment best to wait until 3.2.3. We upgraded to 3.2.0 because of 3.1.x issues however ran into serious problem with scheduler. Master scheduler will timeout while starting if you have more than couple of thousand reload task. It will come up after several hours of retry if lucky. We have identified several other issues as well in this version. As per support most of them will be fixed in 3.2.3 release.

[crusader_]

Hi Alex.

Yes, it's possible. I'm not sure whether it could be done by clicking on the button, but if you copy DB and restore on new environment, fix repository service config and move Apps, AppContent, Extensions etc files to share - that will work.

[Anonymous]

The best plan of action is to upgrade to Qlik Sense, Shared Persistence, February 2018 release. All aforementioned issues and concerns have been addressed.