...
- Ensure that the DataStore service is running.
Use the resetdb utility to delete and then recreate the up.time database structure by running one of the following commands:
Code Block language text On Windows: >net stop "up.time Data Collector" >C:>Program Files>uptime software>uptime>resetdb --nodata really On Linux or Solaris: /etc/init.d/uptime_core stop /usr/local/uptime/resetdb --nodata really
Run the following command:
Code Block language text fulldatabaseimport path/<filetoimport>.xml.gz
Where
path/<filetoimport>.xml.gzis the path to and file name of the archived contents of your DataStore. For example, to import the archive that is located in up.time's root installation directory, enter:Code Block language text fulldatabaseimport uptimedump_2007-01-02.xml.gz
Restart the up.time Data Collector service by running the following command:
Code Block language text On Windows: >net start "up.time Data Collector" On Linux or Solaris: /etc/init.d/uptime_core start
...
- On the current up.time installation, generate a problem report using the Problem Reporting link under the Config tab.
- Install the same version of up.time on your new up.time server. It is very important that the export system and the import system are using the same up.time version.
- Copy this problem report to your new up.time server and place it in the up.time 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:pr20140618-123456.zip or /root/pr20140618-123456.zip):
On Windows:
Code Block >net stop "up.time Data Collector" >C:>Program Files>uptime software>uptime>resetdb --nodata really >C:>Program Files>uptime software>uptime>scripts>primport PR-NAME >net start "up.time Data Collector"
On Linux or Solaris:
Code Block /etc/init.d/uptime_core stop /usr/local/uptime/resetdb --nodata really /usr/local/uptime/scripts/primport PR-NAME /etc/init.d/uptime_core start