Performing regular backups of your Uptime Infrastructure Monitor DataStore is a highly recommended practice. The DataStore is the Uptime Infrastructure Monitor backbone and holds all configuration information and historical performance data. This article outlines five common methods for backing up your DataStore. It is recommended to choose at least one of these methods to back up your Uptime DataStore. For added safety, you can implement more than one of the options below in case one of the methods should falter. Only one of the options below can be used to restore a backup; the methods cannot be merged when restoring the backup.
These backup methods are intended for a single Monitoring Station. Never attempt to merge two or more Monitoring Station configurations in a single database.
In addition to backing up the Uptime DataStore, it is also important to back up the Uptime configuration files and any customized files. Be sure to follow the recommendations in the Other Files and Directories to Back up section at the bottom of this article.
Option 1: Creating a tar or zip archive
One backup option is to regularly create tar or zip archives of your /datastore directory. This is the most straightforward method but requires Uptime Infrastructure Monitor to be stopped during the backup period.
To use this method, simply include the /datastore directory in the tar/zip archive. If you need to recover your DataStore from a tar/zip archive, ensure that all Uptime Infrastructure Monitor services are stopped and that you delete the existing /datastore files before extracting your archive.
- Stop the Uptime Infrastructure Monitor services.
- Archive the datastore directory.
- On a Windows system:
- Locate the Uptime Infrastructure Monitor install directory (default C:\Program Files\uptime software\uptime).
- Archive the \datastore directory (using an archiving tool such as Winzip).
- Move the zip archive to another system or drive.
- On a Unix system, enter the following commands:
# cd /usr/local/uptime OR cd /opt/uptime (depending on the OS) # tar -cvf uptime_backup.tar datastore # gzip uptime_backup.tar
- On a Windows system:
- Start the Uptime Infrastructure Monitor services. -Review Starting (or restarting) and stopping UIM
Option 2: Using the mysqldump tool
mysqldump is a free utility included with the standard UIM MySQL database. This tool exports DataStore contents into a human readable .sql file that you can use to recreate your DataStore. The commands below detail how to export both configuration and performance data using mysqldump.
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:
mysqldump --single-transaction -u[username] -p[password] -P[port #] --protocol=tcp [dbname]
By adding > mybackup.sql to the commands below, all mysqldump data is directed to the mybackup.sql file. Change the mybackup.sql file name to a date-stamped file name for easy reference.
Exporting your entire datastore
mysql/bin/mysqldump --single-transaction -uuptime -puptime -P3308 --protocol=tcp uptime > mybackup.sql
The [dbname] variable may be uptime_v4 if your database was created in Uptime Infrastructure Monitor 4.
Exporting only your configuration information
In Uptime Infrastructure Monitor 7.2 or later there is the feature to generate a problem report with configuration via the command line. You can schedule the execution of the command line problem report with a cron job or scheduled task.
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:
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
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
Before importing data, you must stop the UIM services. For more information, see the topic above regarding Creating a tar or zip Archive.
To import your backup data, run the following command:
mysql/bin/mysql -q -f -u uptime -puptime -P3308 --protocol=tcp uptime < mybackup.sql
This process attempts to insert any non-duplicate data that is found in your mybackup.sql file. If you need to rebuild your database from scratch, run the resetdb utility before importing your backup file. This utility erases all of the data in your existing DataStore. Be absolutely sure that a full backup recovery is your best option before running this command.
resetdb really --nodata
Option 3: MySQL replication
MySQL replication is the most complex backup method but is the most powerful for quick recovery. MySQL's built-in replication feature will maintain a completely up-to-date copy of your DataStore on another database instance (on the local system or a secondary server). This copy can be quickly set up to act as the primary DataStore in the event of a failure, or can be easily copied from the replication server to the primary server in the event of an outage.
Information on starting replication can be found at:
- MySQL Online Documentation: How to set up replication.
- Uptime Infrastructure Monitor KB article: Setting up a reporting instance.
Option 4: Oracle data pump
If your DataStore is running on Oracle, you can use the Data Pump utility to export data from an Oracle database. Refer to the Oracle database utilities page for more information:
Option 5: SQL Server backup
If your DataStore is running on Microsoft SQL Server, you can use the SQL Backup tool to export data. Refer to the Microsoft Developer Network for more information:
Other files and directories to back up
The following files and directories listed in this section are not part of the DataStore but should also be backed up on a regular basis as well.
<uptime_dir>/license.dat <uptime_dir>/UptimeDataCollector.ini (Windows OS) <uptime_dir>/uptime.conf <uptime_dir>/uptime.jcnf (Linux OS) <uptime_dir>/apache/conf/httpd.conf <uptime_dir>/apache/conf/php.ini (Linux OS) <uptime_dir>/apache/php/php.ini (Windows OS) <uptime_dir>/dashboards <uptime_dir>/gadgets <uptime_dir>/plugins <uptime_dir>/scripts <uptime_dir>/xml
If you configured SSL browsing in Apache, remember to back up the cert files in the <uptime_dir>/apache/conf directory.
If you added MIB files to the <uptime_dir>/mibs directory, you should also back up those custom files.