article Importing Archived Data into up.time

Related Documentation Version of up.time Affected Affected Platforms
Exporting and Importing Your DataStore 4.2 or later All

Contents

Overview

Note: The archiving procedure that is described in this article only works with MySQL databases. See Exporting and Importing Your DataStore for information on exporting and importing data into Oracle and SQL databases.


This article describes how to retrieve DataStore data that was automatically archived by up.time, based on your configured archive policy.

Note: Archived data can only be restored by the same version of up.time that was used to create it.


You can configure up.time to selectively archive data in the DataStore. Each month, up.time checks the DataStore to determine if the data is older than the specified archive period. The archived data is moved into a directory named archives under the base installation directory.

If up.time discovers data that is older than the archive period, the data is copied out of the database and saved as a compressed XML file. The name of this file consists of the type of data that was archived and the date on which the data was archived. For example, a file containing file system capacity data that was archived on June 12, 2010 has the following file name:

performance_fscap_2010-06-12.xml.gz

Identifying the Data to Restore

Before importing your data, identify the files that contain the information that you want to import. up.time creates the following archives:

Type of Data Archive Filename Database Table(s) Archived
CPU Statistics performance_cpu_<date>.xml.gz performance_cpu 
Overall CPU Statistics performance_aggregate_<date>.xml.gz performance_aggregate
NRM Statistics performance_nrm_<date>.xml.gz performance_nrm (if you are running Novell NRM in your environment)
Multi-CPU Statistics performance_cpu_<date>.xml.gz performance_cpu
Detailed Process Statistics performance_psinfo_<date>.xml.gz performance_psinfo 
Disk Performance Statistics performance_disk_<date>.xml.gz performance_disk
File System Capacity Statistics performance_fscap_<date>.xml.gz performance_fscap
Network Statistics performance_network_<date>.xml.gz performance_network
User Information Statistics performance_who_<date>.xml.gz performance_who
Volume Manager Statistics performance_vxvol_<date>.xml.gz performance_vxvol
Retained Data erdc_int_data_<date>.xml.gz
erdc_decimal_data_<date>.xml.gz
erdc_string_data_<date>.xml.gz
erdc_int_data
erdc_decimal_data
erdc_string_data

Importing the Archived Data

When you have identified the archived data that you want to import into the database, run the following commands to import the archived data:

  1. At the command line, navigate to the following directory:

    On Linux and Solaris: /usr/local/uptime/scripts/.

    On Windows: C:Program Filesuptime softwareuptimescripts.

  2. Run the restorearchive command with one or more of the following options:
    • -f <filename>

      Imports a single file (specify the full path to the file name).

    • -d <date>

      Imports all files with the specified date (in YYYY-MM-DD format).

    • -D <directory>

      The directory containing the archived files. Note that you must specify this option when using the -d option.

    • -c <configFile>

      The full path to the uptime.conf file.

    For example, enter the following command to import all data archived on September 23, 2010 which is located in the default directory for archived data:

    restorearchive -d 2010-09-23 -d /usr/local/uptime/archives/ -c /usr/local/uptime/uptime.conf

Related Articles


The up.time Data Collector is unavailable

RatingViews
article

By: uptime Support | Date Created: 6-9-2006 | Last Modified: 10-17-2013 | Index: 077

  5510

Exporting and Importing Your DataStore or Configuration

RatingViews
article

This article explains the DataStore export and import utilities.

By: uptime Support | Date Created: 2-13-2007 | Last Modified: 12-19-2012 | Index: 140

  5489

'up.time Data Collector is unavailable' error in web interface

RatingViews
article

If you have recently changed the hostname of your monitoring station and receive the message "Database Not Responding" in the monitoring station web interface, you must make the following...

By: uptime Support | Date Created: 10-1-2009 | Last Modified: 10-18-2013 | Index: 379

  3013

Limited Performance Data Available

RatingViews
article

By: uptime Support | Date Created: 6-15-2006 | Last Modified: 1-16-2013 | Index: 082

  9395

Understanding and Using Retained Data

RatingViews
article

This article explains how to use data that is optionally retained by up.time service monitors.

By: uptime Support | Date Created: 7-19-2007 | Last Modified: 6-28-2011 | Index: 196

  2460

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement