Exporting and Importing Your DataStore or Configuration

Article Contents

• Overview
• Exporting the Contents of your DataStore
• Importing the Contents of your DataStore
• Exporting & Importing only your up.time Configuration

Overview

up.time includes two command line utilities for archiving and restoring your DataStore:

• fulldatabasedump

  Creates a compressed XML file of the complete contents of your DataStore.

• fulldatabaseimport

  Imports the archived data back into your DataStore.

Both utilities work with all supported database backends.

Exporting the Contents of your DataStore

To export the contents of your DataStore:

1. Shut down the up.time Data Collector service.
2. Navigate to the scripts folder under the directory where up.time is installed.
3. Run the following command to save the dump file to the folder of the root installation:

   fulldatabasedump

   Or, to specify the location of the dump file:

   fulldatabasedump <path>

   Depending on the size of your DataStore, this process can take anywhere from several minutes to several hours.

4. The utility will create a uptimedump_YYYY-MM-DD.xml.gz file. For example, uptimedump_2007-01-02.xml.gz. This file is saved in up.time's root installation directory.

Importing the Contents of your DataStore

To import the contents of your DataStore:

1. Ensure that the DataStore service is running.
2. Use the resetdb utility to delete and then recreate the up.time database structure by running one of the following commands:

   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
   

3. Run the following command:

   fulldatabaseimport path/<filetoimport>.xml.gz

   Where 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 up.time's root installation directory, enter:

   fulldatabaseimport uptimedump_2007-01-02.xml.gz

4. Restart the up.time Data Collector service by running the following command:

   On Windows:
   
   >net start "up.time Data Collector"

   On Linux or Solaris:
   
   /etc/init.d/uptime_core start

Exporting & Importing only your up.time Configuration

If you do not require all of your historical performance data or service monitor outage information, you can migrate only your up.time configuration from one up.time installation to another using the steps below.

1. On the current up.time installation, generate a problem report using the Problem Reporting link under the Config tab.
2. 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.
3. Copy this problem report to your new up.time server and place it in the up.time installation directory.
4. 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:pr20120618-123456.zip or /root/pr20120618-123456.zip):

   On Windows:
   
   >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:
   
   /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