Page History
...
mysqldump is a free utility included with the standard Uptime Infrastructure Monitor UIM MySQL database. This tool will export exports DataStore contents into a human readable .sql file that you can later be used use to recreate your DataStore. The commands below detail how to export both configuration and performance data using mysqldump.
| Info |
|---|
The following sample commands are provided with the assumption that you are executing them from the |
...
UIM installation directory and that the default database access options |
...
are unchanged since installation. If any parameters |
...
changed, refer to your uptime.conf file for the correct port, user, password, and database access information. |
The standard format for the mysqldump command is as follows:
| Code Block | ||
|---|---|---|
| ||
mysqldump --single-transaction -u |
...
[username |
...
] -p |
...
[password |
...
] -P |
...
[port # |
...
] --protocol=tcp |
...
[dbname |
...
] |
By adding > _ mybackup.sql_ to the commands below, all mysqldump data will be is directed to the _ mybackup.sql _ file. The _Change the mybackup.sql _ file name should be changed to a date-stamped file name for easy reference.
Exporting your entire datastore
| Code Block | ||
|---|---|---|
| ||
mysql/bin/mysqldump --single-transaction -uuptime -puptime -P3308 --protocol= |
...
tcp uptime > mybackup.sql |
| Info |
|---|
The |
Exporting only your configuration information
In Uptime Infrastructure Monitor 7.2 or later there is the feature to generate a Problem Report problem report with Configuration configuration via the command line. One You can schedule the execution of the command line Problem Report problem report with a cron job or scheduled task.
| Code Block | ||
|---|---|---|
| ||
prexport \[-p\] \[-cN\] Options: -p to dump last hour of data -c dump historical configuration; N is number of months defaults to 3 months |
Alternatively, here are the configuration tables:
| Code Block | ||
|---|---|---|
| ||
mysql/bin/mysqldump -uuptime -puptime -P3308 --protocol=tcp |
...
--ignore-table=uptime.erdc_decimal_data |
...
--ignore-table=uptime.erdc_int_data |
...
--ignore-table=uptime.erdc_string_data |
...
--ignore-table=uptime.ranged_object_value |
...
--ignore-table=uptime.performance_aggregate |
...
--ignore-table=uptime.performance_cpu |
...
--ignore-table=uptime.performance_disk |
...
--ignore-table=uptime.performance_esx3_workload |
...
--ignore-table=uptime.performance_fscap |
...
--ignore-table=uptime.performance_lpar_workload |
...
--ignore-table=uptime.performance_network |
...
--ignore-table=uptime.performance_nrm |
...
--ignore-table=uptime.performance_psinfo |
...
--ignore-table=uptime.performance_sample |
...
--ignore-table=uptime.performance_vxvol |
...
--ignore-table=uptime.performance_who |
...
--ignore-table=uptime.archive_delenda uptime > mybackup.sql |
Exporting
...
only your historical performance data
| Code Block | ||
|---|---|---|
| ||
mysql/bin/mysqldump -uuptime -puptime -P3308 --protocol=tcp uptime performance_aggregate |
...
performance_cpu performance_disk performance_esx3_workload performance_fscap performance_lpar_workload performance_network performance_nrm performance_psinfo performance_sample performance_vxvol performance_who erdc_decimal_data erdc_int_data |
...
erdc_string_data > mybackup.sql |
Importing your backup data
| Info |
|---|
Before importing data, you must stop the |
...
UIM services. For more information, see Creating a tar or zip Archive section |
...
. |
To import your backup data, run the following command:
...