...
By default, a problem report contains configuration information for elements from the last three months. If the configuration has not changed for an element in that time (ie. size memory is the same, number of CPU's is the same, etc.), then the problem report will not contain configuration for that element. When the problem report is loaded into a new Uptime install, you may see an error in the UI because the configuration information for the element is unavailable. Within the next 24 hours, the Configuration Gatherer for that element will run and update the missing configuration and the error will go away. This can be sped up by clicking the Rescan Configuration button in the Info page for that element.
...
- On the current Uptime Infrastructure Monitor installation, generate a problem report using the Problem Reporting link under the Config tab.
- Install the same version of Uptime Infrastructure Monitor on your new Uptime Infrastructure Monitor server. It is very important that the export system and the import system are using the same Uptime Infrastructure Monitor version.
- Copy this problem report zip file to your new Uptime Infrastructure Monitor server and place it in the Uptime Infrastructure Monitor installation directory.
- Import the configuration from your problem report by running the following commands (replace PR-NAME with the full path & file name for your problem report, e.g. c:pr20160618-123456.zip or /root/pr20160618-123456.zip):
On Windows:
Code Block > net stop "up.time Controller" > net stop "up.time Data Collector" > <uptime_dir>\resetdb --nodata really > <uptime_dir>\scripts\primport <pr_zipfile> > net start "up.time Data Collector" > net start "up.time Controller"
On Linux or Solaris:
Code Block # /etc/init.d/uptime_controller stop # /etc/init.d/uptime_core stop # <uptime_dir>/resetdb --nodata really # <uptime_dir>/scripts/primport <pr_zipfile> # /etc/init.d/uptime_core start # /etc/init.d/uptime_controller start