| Related \nDocumentation | \nVersion \nof up.time Affected | \nAffected \nPlatforms | \n
| Exporting and Importing Your DataStore \n | \n4.2 or later | \nAll | \n
Contents
\n \n \nOverview
\nNote: 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.
\n \nThis article describes how to retrieve DataStore data that was automatically archived by up.time, based on your configured archive policy.
\n \nNote: Archived data can only be restored by the same version of up.time that was used to create it.
\n \nYou 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 \ninstallation directory.
\n \nIf up.time discovers data that is older than the archive \nperiod, 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 \n12, 2010 has the following file name:
\n \nperformance_fscap_2010-06-12.xml.gz
\n \n \n \nIdentifying \nthe Data to Restore
\nBefore importing your data, identify the files that \ncontain the information that you want to import. up.time creates the following archives:
\n \n| Type \nof Data | \nArchive \nFilename | \nDatabase \nTable(s) Archived | \n
| CPU Statistics | \nperformance_cpu_<date>.xml.gz | \nperformance_cpu | \n
| Overall CPU \nStatistics | \nperformance_aggregate_<date>.xml.gz | \nperformance_aggregate | \n
| NRM Statistics | \nperformance_nrm_<date>.xml.gz | \nperformance_nrm \n(if you are running Novell NRM in your environment) | \n
| Multi-CPU \nStatistics | \nperformance_cpu_<date>.xml.gz | \nperformance_cpu | \n
| Detailed \nProcess Statistics | \nperformance_psinfo_<date>.xml.gz | \nperformance_psinfo | \n
| Disk \nPerformance Statistics | \nperformance_disk_<date>.xml.gz | \nperformance_disk | \n
| File System \nCapacity Statistics | \nperformance_fscap_<date>.xml.gz | \nperformance_fscap | \n
| Network \nStatistics | \nperformance_network_<date>.xml.gz | \nperformance_network | \n
| User \nInformation Statistics | \nperformance_who_<date>.xml.gz | \nperformance_who | \n
| Volume Manager \nStatistics | \nperformance_vxvol_<date>.xml.gz | \nperformance_vxvol | \n
| Retained Data | \nerdc_int_data_<date>.xml.gz \n erdc_decimal_data_<date>.xml.gz \n erdc_string_data_<date>.xml.gz |
\n erdc_int_data \n erdc_decimal_data \n erdc_string_data |
\n
Importing \nthe Archived Data
\nWhen you have identified the archived data that you want to import into the database, run the following commands to import the archived data:
\n \n-
\n
- At the command line, navigate to the following directory:
\n
On Linux and Solaris: /usr/local/uptime/scripts/.
\nOn Windows: C:Program Filesuptime \nsoftwareuptimescripts.
\n
\n - Run the restorearchive command with
\none or more of the following options:
\n
-
\n
- -f <filename>
\n
Imports a single file (specify the full path \nto the file name).
\n
\n - -d <date>
\n
Imports all files with the specified date (in YYYY-MM-DD \nformat).
\n
\n - -D <directory>
\n
The directory containing the archived files. Note that \nyou must specify this option when using the -d option.
\n
\n - -c <configFile>
\n
The full path to the uptime.conf file.
\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:
\nrestorearchive -d \n2010-09-23 -d /usr/local/uptime/archives/ -c /usr/local/uptime/uptime.conf
\n
\n - -f <filename>
\n