In this Webinar, we covered how to approach a Qlik Sense Enterprise on Windows migration.
The session covers:
How to Back-Up and Restore
If assistance is needed, Qlik Consulting would need to be engaged. Qlik Support cannot provide walk-through assistance with server migrations outside of a post-installation and migration completion break/fix scenario.
Q: Is it possible to migrate from a standalone installation to a clustered one? A: Yes. Once the Central Node has been moved to a new host, additional Rim nodes can be added as usual through the QMC.
Q: What about the personnal objects created by users (sheets, bookmarks, ...) ? Are they included in the QSR backup ? A: All user objects as well as base sheets are included both in the Apps themselves as well as in the QSR.
Q: Is this possible to migrate one repository to another server and merge the repository with another one? A: Not through the procedure outlined in this webinar. If your goal is to merge content from multiple sites, or seamlessly migrate content, I recommend reaching out to your Account Manager and discuss Qlik Mission Control platform.
Q: Would the steps given here change if postgres is installed on a stand-alone server? A: The only steps that would change would be the backup/restore for the DB itself, as this would have to be performed locally on the DB host. Additionally, if the DB location has changed, the QRS connection strings will have to be updated via QlikSenseUtil.
Q: Is it necessary to have the same release on both servers before migrating ? Or is there compatibility between versions of QlikSense ? A: You can restore a database from a previous version on a newer Qlik Sense release and the system will update the internal objects automatically, however the reverse is not possible. It is recommended to perform the upgrade in place, before migrating the server.
Q: Is it possible to restore without certificate ? A: Yes, Trust Root and Qlik Client certificates can be recreated from scratch, however as mentioned during the call, all internal metadata values that were previously encrypted, such as data source connection strings, would have be updated via the QMC by re-entering the connection password and saving.