5 Replies Latest reply: Oct 30, 2013 7:51 AM by Hampus von Platen RSS

    Server Migration

    Leni Balakrishnan

      Hi All,


      I would like to get the list of things that need to take care while migrating the Qlikview environment from one server to an another server.



      1. Need to know the downtime of the server.

      2. The information I need to get from the client


      Apart from this if anything we need to take care knidly let me know those points well.


      Can anyone help me to get an estimate on the downtine of the server and the things to be taken care during migration?


      We are moving our current server to an another server.


      Please help me and it is urgent.



      Leni Balakrishan

        • Re: Server Migration
          Michele Barini


          you can install qlikview services on the new server, copy the qvw documents and test everything is fine.

          Then you could migrate the user to the new server and stop the services in the old one.

            • Re: Server Migration
              Leni Balakrishnan

              Is there any downtime faced by the enduser during this migration?


              Like the user will not be able to access the accesspoint portal during migration. If so, then for how many hours the user may face the downtime?


              Thank you for the reply

                • Re: Server Migration



                  At a customer I migrated the environment from one server to another and at the same time I upgraded it from QV10 to QV11. At the cutover point the downtime for the end users was below 1 hour.


                  For this migration the following approach was used:

                  1. Setup new server with OS and other for technical maintenance needed tooling (like OS, backups, etc.)
                  2. On the new server install QlikView and configure it as needed. Time is required based upon the environment configuration.
                  3. copy QVW + QVD from the old server to the new server. Time required is depending on the volume of data. In my case it took a day to copy everything due to network slowness.
                  4. on the new server setup all needed tasks and perform the reloads so that both environments are in sync with regard to the data presented in the dashboards
                  5. let the new server run in parallel with the old server, in this period also let key users validate that all dashboards are still working as expected. For this period I took a month to ensure I covered all reload scenario's and give enough time for analysis.
                  6. to ensure all shared objects of users are available on the new environment I stopped the old server (so that users cannot access the applications) and copied all shared files from the old server to the new server.
                  7. after a final environment check give the users access to the new server


                  Hope this helps to give you an idea of the timelines and how you can minimze the downtime for your end users.


                  Kind regards,