Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Stop the "up.time Data Collector" and "up.time Controller" services.
  2. Navigate to the scripts folder under the directory where Uptime Infrastructure Monitor is installed.

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

    Code Block
    fulldatabasedump

    Or, to specify the location of the dump file:

    Code Block
    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_20072016-01-02.xml.gz. This file is saved in Uptime Infrastructure Monitor's root installation directory.

...

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

    Code Block
    languagetext
    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
  3. Run the following command:

    Code Block
    languagetext
    <uptime_dir>\scripts\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 Uptime Infrastructure Monitor's root installation directory, enter:

    Code Block
    languagetext
    <uptime_dir>/scripts/fulldatabaseimport uptimedump_20072016-01-02.xml.gz
  4. Restart the up.time Data Collector service by running the following command:

    Code Block
    languagetext
    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

Exporting & Importing only your Uptime Infrastructure Monitor Configuration

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.

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.

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

...