Back again with a tip for our current users. We’ve heard this question several times and had a few people mess it up so we thought we’d post it for everyone’s benefit.
The steps are easy, but the order is critical.
Another thing to point out: The prerequisites are fundamental and you would not believe how many people ignore the preparation for such a move, imagining that it is just like copying a notepad file from one file server to another. It is not.
Even though Visual KPI is a modern and quick-to-deploy mobile monitoring and BI tool, it is still an enterprise application and should be treated as such during a migration such as this.
For this post, we will assume the worst case, which is SQL Server and Visual KPI are on different physical machines. We will also assume that the database and Visual KPI Instance name are identical and are the default value of “VisualKPI” as delivered from the factory (us). The optional steps will be shown for the trivial case where SQL Server and Visual KPI are on the same machine.
- OS is not important, you can move from Windows Server 2003 to 2008 or back.
- Both servers have all Visual KPI prerequisites installed and tested (.NET 4.0 Client and Extended profiles).
- Both servers are patched up to date for the OS version
- IIS is configured to allow .NET 4.0 to run on the target server
- The SQL software is of the same vintage (i.e. moving from 2005 to 2005, or from 2008 to 2008 or from 2008R2 to 2008R2, etc.)
- Note: This is a SQL requirement, not a Visual KPI requirement
- To migrate SQL versions, a more involved process is required rather than simply creating a BAK file for restoration. Contact us if you need help with this.
- SQL Server is patched the same on both machines, or the target machine is more up-to-date with patches than the original
Steps to Migrate:
Here are the steps for migrating Visual KPI to a new server. Note: make sure you have the necessary permissions before you begin. This should take no more than 10 minutes:
- Use SQL Server Backup to create a .BAK file on the Source SQL Server machine, then copy it to the Target SQL Server machine. E.g. VKPI.BAK, containing the database “VisualKPI”
- Restore the Database using SQL Restore function, now you have a database on the Target SQL box called VisualKPI.
- Run the Visual KPI Server manager on the Visual KPI Target machine and create a new website instance named “VisualKPI”
- When the database creation step arrives, simply choose a DB name of “VisualKPI-deleteme”
- Keep all other selections named “VisualKPI”
- Let the wizard run to completion
- Modify connection strings in the 3 applications, change “DB=VisualKPI-delete” me to “DB=VisualKPI” in
- Cache Server
- Alert Server
- Create all Interfaces (to data sources – OSIsoft PI System, Oracle, etc.) again with same names
- For ODBC, OLEDB and OLAP interfaces, copy the *.SQL fields which hold the Current and Trend data queries to their folders in the Target Visual KPI machine, overwriting the default files created when the interfaces were installed on the Target Visual KPI machine.
- Delete the dummy database in the Target SQL Server machine named “VisualKPI-deleteme”
- You are done
Hope this helps. We’ll be along with more tips in the coming weeks so let us know if there is something you would like us to write about.