Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi @dipti1
Following this guide will make it very easy
https://community.qlik.com/t5/Support-Updates/Qlik-Sense-Migration-Migrating-your-Entire-Qlik-Sense/...
You'll need to consider a few important things:
1. be sure to install the same version and patch on new server, after that you can start doing the migration. if you do the migration in the proper way, you will not need to apply the license manually.
2. Whether the new server will have a different name, you shoudl carefully follow this part on the shared link
If you don't do this, among other problems, all your connections and data sources will fail because the keys are linked to the certificates of the server you have running.
3. If the new server will have the same name, it's a bit simpler because you can skip the bootstrap and cluster service file paths steps. (you could megrate old certificates)
4. You might also have problems running both servers simultaneously. My suggestion would be that after you have the necessary backups, shut down the old server and start working on the new one. This is not mandatory but can avoid some mess regarding license llocations
5. check if the environment is single node or mulitnode. for each case, the same link has the complete information.
6. check if the new servers IP has access to the existing data sources
hope this helps,
Best,
Help users find answers! Don't forget to mark a solution that worked for you & to smash the like button! 🙂
Hi @dipti1
Following this guide will make it very easy
https://community.qlik.com/t5/Support-Updates/Qlik-Sense-Migration-Migrating-your-Entire-Qlik-Sense/...
You'll need to consider a few important things:
1. be sure to install the same version and patch on new server, after that you can start doing the migration. if you do the migration in the proper way, you will not need to apply the license manually.
2. Whether the new server will have a different name, you shoudl carefully follow this part on the shared link
If you don't do this, among other problems, all your connections and data sources will fail because the keys are linked to the certificates of the server you have running.
3. If the new server will have the same name, it's a bit simpler because you can skip the bootstrap and cluster service file paths steps. (you could megrate old certificates)
4. You might also have problems running both servers simultaneously. My suggestion would be that after you have the necessary backups, shut down the old server and start working on the new one. This is not mandatory but can avoid some mess regarding license llocations
5. check if the environment is single node or mulitnode. for each case, the same link has the complete information.
6. check if the new servers IP has access to the existing data sources
hope this helps,
Best,
Help users find answers! Don't forget to mark a solution that worked for you & to smash the like button! 🙂
@RafaelBarrios Thank You
I have one doubt what happens if I install the fresh instance on new server where it have its own postgress db and Certificates,I just restore the Apps and directories and No bakcup of .tar files and certifictates and apply the license and allocate analyzer access to the Windows administrator than what impact i have in
furure?
Please guide
Hi @dipti1
if i understood correctly you want to:
- export app manually from old environment and import manually in new one
- no restore DB
- no restore certificates
- apply license manually
as result you will end up with a very clean environment but you will lose:
- streams
- personal and community sheets
- personal and community bookmarks
- stories
- data connections
- logs
- license allocation
- QMC configuration such as custom properties, security rules, proxy, users directory and so on
Remember that regarding apps binary files in \\sharedFolder\apps\, it's not just a matter of moving the files to the new server; the new environment won't automatically detect and include them.
You could copy the files from the old directory and import them but have to be done by the QMC of the new installation. In this case, you would need to add the .qvf extension to the files and import, but everything that was personal or community will become part of the app's public sheets.
Another important thing about "allocate analyzer access to the Windows administrator" is that if this is the user running the Qlik services, this user should never have a license. If you do, some services may fail because it assumes the user has many open sessions.
hope this helps.
best,