Article will explain how to change the index location.
If you wish to transfer the Syskit Insights application (the agent that does the collection) AND at the same time keep the existing data here is what you need to do:
Stop the Syskit Insights Agent service and the Syskit Insights Maintenance service.
Install the Syskit Insights on a different server.
Copy the entire index from the old to the new location.
Start the Configuration Wizard and:
Connect to the "old", already used Syskit Insights database
Connect to the new index location.
Finish the Configuration Wizard, start the application and that's it.
Stop the Syskit Insights Agent service and the Syskit Insights Maintenance service.
Copy the entire index from the old to the new location.
Start the Configuration Wizard and:
Connect to the "old", already used Syskit Insights database
Connect to the new index location.
Finish the Configuration Wizard, start the application and that's it.
A list of commonly asked questions.
Once the farms are imported from the SPDocKit database, Syskit Insights does not continue to use it. Instead, Syskit Insights uses its own database. See here for system requirements.
No, Syskit Insights uses the same database to store information about every farm you wish to monitor.
Each Syskit Insights' agent can use only one index location.
It is very difficult to hypothesize on the required index size as this largely depends on your infrastructure and how big your farm/s are. Recommended minimum of 200GB disk space should be enough to store the data (ULS, SQL logs and Windows Event logs) of three SharePoint farms (Test, Preproduction, Production). However, please note, that index size can vary from a few gigabytes up to a terabyte of data depending on which Event Levels you are collecting and again, on your infrastructure. These Event Levels can be changed in available farm settings in order to optimize the amount of collected data.