Versions Compared

Old Version 1

changes.mady.by.user Unknown User (adimopoulos)

Saved on

compared with

New Version Current

changes.mady.by.user IDERA

Saved on

Key

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

Contents

Table of Contents

Overview

\n \n \n \n \n \n \n \n \n \n \n \n \n
Related \nDocumentationVersion \nof up.time AffectedAffected \nPlatforms
Exporting and Importing Your DataStore \n 4.2 or laterAll

...

Contents

...

...

Overview

...

Note
titleNote

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.timeUptime Infrastructure Monitor, based on your configured archive policy.

...

Note
titleNote

...

Archived data can only be restored by the same version of

...

Uptime Infrastructure Monitor that was used to create it.

...

You can configure up.time Uptime Infrastructure Monitor to selectively archive data in the DataStore. Each month, up.time Uptime Infrastructure Monitor 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 \ninstallation installation directory.

...

If up.time If Uptime Infrastructure Monitor discovers data that is older than the archive \nperiodperiod, 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 \n1212, 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 \ncontain contain the information that you want to import. up.time Uptime Infrastructure Monitor creates the following archives:

...

\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Type \nof Type of DataArchive \nFilenameFilenameDatabase \nTableTable(s) Archived
CPU Statisticsperformance_cpu_<date>.xml.gzperformance_cpu 
Overall CPU \nStatisticsStatisticsperformance_aggregate_<date>.xml.gzperformance_aggregate
NRM Statisticsperformance_nrm_<date>.xml.gzperformance_nrm \n (if you are running Novell NRM in your environment)
Multi-CPU \nStatisticsStatisticsperformance_cpu_<date>.xml.gzperformance_cpu
Detailed \nProcess Detailed Process Statisticsperformance_psinfo_<date>.xml.gzperformance_psinfo 
Disk \nPerformance StatisticsDisk Performance Statisticsperformance_disk_<date>.xml.gzperformance_disk
File System \nCapacity Capacity Statisticsperformance_fscap_<date>.xml.gzperformance_fscap
Network StatisticsNetwork \nStatisticsperformance_network_<date>.xml.gzperformance_network
User \nInformation User Information Statisticsperformance_who_<date>.xml.gzperformance_who
Volume Manager \nStatisticsStatisticsperformance_vxvol_<date>.xml.gzperformance_vxvol
Retained Dataerdc_int_data_<date>.xml.gz
\n erdc_decimal_data_<date>.xml.gz
\n erdc_string_data_<date>.xml.gz		erdc_int_data
\n erdc_decimal_data
\n 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:

...

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

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

    \n

    On Windows: C:\Program Filesuptime \nsoftwareuptimescripts.

    \n
    2. \n

  2. Files\uptime software\uptime\scripts.

  3. Run the restorearchive command with \none one or more of the following options: \n
      \n
    • -f <filename> \n

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

      \n
      • \n
    • -d <date> \n

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

      \n
      • \n
    • -D <directory> \n

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

      \n
      • \n
    • -c <configFile> \n

      The full path to the uptime.conf file.

      \n
      • \n
    \n

    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:

    \n
    Code Block
    restorearchive -d
    \n2010
     2010-09-23 -d /usr/local/uptime/archives/ -c /usr/local/uptime/uptime.conf
    \n
    4. \n