Page History

Article Contents

...

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

...

Overview

...

Overview

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

...

\n
• fulldatabasedump \n

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

  \n
\n
• fulldatabaseimport \n

  Imports the archived data back into your DataStore.

  \n
\n

...

Both utilities work with all supported database backends.

...

Exporting the Contents of your DataStore

...

To export the contents of your DataStore:

...

\n
1. Shut down the Stop the "up.time Data Collector service" and "up.time Controller" services.
\n

2. Navigate to the scripts folder under the directory where

   up.time

   Uptime Infrastructure Monitor is installed.

\n

3. Run the following command to save the dump file to the folder of the root installation:

   Code Block
   fulldatabasedump

   \n

   Or, to specify the location of the dump file: \n

   Code Block
   fulldatabasedump <path>

   \n

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

\n
4. The utility will create a uptimedump_YYYY-MM-DD.xml.gz file. For example, uptimedump_20072016-01-02.xml.gz. This file is saved in up.timeUptime Infrastructure Monitor's root installation directory.
\n

...

Importing the Contents of your DataStore

...

To import the contents of your DataStore:

...

1. Ensure that the DataStore service is running.
\n

3. Use the resetdb utility to delete and then recreate the

   up.time

   Uptime Infrastructure Monitor database structure by running one of the following commands:

   \n

   Code Block
   language text
   On Windows:

   \n
   >net

   > net stop "up.time Controller"  > net stop "up.time Data Collector"

   \n
   >C:>Program Files>uptime software>uptime>resetdb

   > <uptime_dir>\resetdb --nodata

   really \n \n

   really  On Linux or Solaris:

   \n
   

   # /etc/init.d/uptime_

   core

   controller stop

   \n
   

   # /

   usr

   etc/

   local

   init.d/uptime_core stop  # <uptime_dir>/resetdb --nodata really

   \n \n
\n

5. Run the following command:

   \nfulldatabaseimport

   Code Block
   language text
   <uptime_dir>\scripts\fulldatabaseimport path/<filetoimport>.xml.gz

   \n

   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.timeUptime Infrastructure Monitor's root installation directory, enter: \n \nfulldatabaseimport uptimedump_2007

   Code Block
   language text
   <uptime_dir>/scripts/fulldatabaseimport uptimedump_2016-01-02.xml.gz

   \n
\n \n

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

   \n

   Code Block
   language text
   On Windows:

   \n
   >net

   > net start "up.time Data Collector"

   \n

   > net start "up.time Controller"   On Linux or Solaris:

   \n
   

   # /etc/init.d/uptime_core start  # /etc/init.d/uptime_controller start

   \n
\n

...

Exporting & Importing only your

...

Uptime Infrastructure Monitor Configuration

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 Service Monitor outage information, you can migrate only your up.time Uptime Infrastructure Monitor configuration from one up.time Uptime Infrastructure Monitor installation to another using the steps below.

...

\n
1. On the current up.time Uptime Infrastructure Monitor installation, generate a problem report using the Problem Reporting link under the Config tab. \n
2. Install the same version of up.time Uptime Infrastructure Monitor on your new up.time Uptime Infrastructure Monitor server. It is very important that the export system and the import system are using the same up.time Uptime Infrastructure Monitor version. \n
3. Copy this problem report zip file to your new up.time Uptime Infrastructure Monitor server and place it in the up.time Uptime Infrastructure Monitor installation directory. \n
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:pr20120618pr20160618-123456.zip or /root/pr20120618pr20160618-123456.zip): \n
   

   On

   Windows:

   \n
   >net

   Code Block
   > net stop "up.time Controller" > net stop "up.time Data Collector"

   \n
   >C:>Program Files>uptime software>uptime>resetdb

   > <uptime_dir>\resetdb --nodata really

   \n
   >C:>Program Files>uptime software>uptime>scripts>primport PR-NAME \n
   >net

   > <uptime_dir>\scripts\primport <pr_zipfile> > net start "up.time Data Collector"

   \n \n

   > net start "up.time Controller"

   On

   Linux

   or

   Solaris:

   \n
   

    

   Code Block
   # /etc/init.d/uptime_

   core

   controller stop

   \n
   /usr/local/uptime

   # /etc/init.d/uptime_core stop # <uptime_dir>/resetdb --nodata really

   \n
   /usr/local/uptime/

   # <uptime_dir>/scripts/primport

   PR-NAME \n
   

   <pr_zipfile> # /etc/init.d/uptime_core start

   \n \n

   # /etc/init.d/uptime_controller start

Save

Save