Page History
...
| Table of Contents |
|---|
Identifying the Data to Restore Importing the Archived Data
...
|
...
| Info |
|---|
The archiving procedure that is described in this article only works with MySQL databases. |
...
See Exporting and |
...
importing your DataStore or configuration 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 Uptime Infrastructure Monitor, based on your configured archive policy. Note
| Info |
|---|
Archived data can only be restored by the same version of |
...
UIM that was used to create it. |
You can configure Uptime Infrastructure Monitor UIM to selectively archive data in the DataStore. Each month, Uptime Infrastructure Monitor UIM 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 Uptime Infrastructure Monitor UIM 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 2023 has the following file name:
performance_fscap_
...
2023-06-12.xml.gz
...
Identifying
...
data you want to restore
Before importing your data, identify the files that contain the information that you want to import. Uptime Infrastructure Monitor 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:
- At the command line, navigate to the following directory:
- On Linux and Solaris: /usr/local/uptime/scripts/.
- On Windows: C:\Program Files\uptime software\uptime\scripts.
- Run the
restorearchivecommand 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.
- -f <filename>
For example, enter the following command to import all data archived on September 23, 2010 2023 which is located in the default directory for archived data:
| Code Block | ||
|---|---|---|
| ||
restorearchive -d |
...
2023-09-23 -d /usr/local/uptime/archives/ -c /usr/local/uptime/uptime.conf |