Page History

...

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 the Other Files and Directories to BackupBack up section at the bottom of this article.

...

Stop the Uptime Infrastructure Monitor services. - Review Starting (or restarting) and stopping UIM

Archive the datastore directory.

...

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 Uptime Infrastructure Monitor MySQL database. This tool will export DataStore contents into a human readable .sql file that can later be used 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 Uptime Infrastructure Monitor installation directory and that the default database access options have not been changed. If any parameters have 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 will be directed to the _mybackup.sql_ file. The _mybackup.sql_ file name should be changed 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

...

Importing your backup data

Before importing data, you must stop the Uptime Infrastructure Monitor services (see steps outlined in the Creating a tar or zip Archive section).

To import your backup data, run the following command:

...

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: Oracle  Oracle Database Utilities

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: SQL Server Backup

Other files and directories to back up

The >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 have configured SSL browsing in Apache, don't forget to back up the cert files in the <uptime_dir>/apache/conf directory. If you have added MIB files to the <uptime_dir>/mibs directory, you will want to back those custom files up as well.