Uptime Infrastructure Monitor includes two command line utilities for archiving and restoring your DataStore:
Creates a compressed XML file of the complete contents of your DataStore.
Imports the archived data back into your DataStore.
Both utilities work with all supported database backends.
To export the contents of your DataStore:
Navigate to the scripts folder under the directory where Uptime Infrastructure Monitor is installed.
Run the following command to save the dump file to the folder of the root installation:
Or, to specify the location of the dump file:
Depending on the size of your DataStore, this process can take anywhere from several minutes to several hours.
uptimedump_YYYY-MM-DD.xml.gzfile. For example,
uptimedump_2016-01-02.xml.gz. This file is saved in Uptime Infrastructure Monitor's root installation directory.
To import the contents of your DataStore:
Use the resetdb utility to delete and then recreate the Uptime Infrastructure Monitor database structure by running one of the following commands:
On Windows: > net stop "up.time Controller" > net stop "up.time Data Collector" > <uptime_dir>\resetdb --nodata really On Linux or Solaris: # /etc/init.d/uptime_controller stop # /etc/init.d/uptime_core stop # <uptime_dir>/resetdb --nodata really
Run the following command:
path/<filetoimport>.xml.gz is the path to and file name of the archived contents of your DataStore. For example, to import the archive that is located in Uptime Infrastructure Monitor's root installation directory, enter:
Restart the up.time Data Collector service by running the following command:
On Windows: > net start "up.time Data Collector" > net start "up.time Controller" On Linux or Solaris: # /etc/init.d/uptime_core start # /etc/init.d/uptime_controller start
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.
If you do not require all of your historical performance data or Service Monitor outage information, you can migrate only your Uptime Infrastructure Monitor configuration from one Uptime Infrastructure Monitor installation to another using the steps below.
> 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:
# /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