Article Contents
- Overview
- Option 1: Creating a tar or zip Archive
- Option 2: Using the mysqldump Tool
- Option 3: MySQL Replication
- Option 4: Oracle Data Pump
- Option 5: SQL Server Backup
- Other Files to Backup
...
Overview
Performing regular backups of your up.time DataStore is a highly recommended practice. The DataStore is the up.time backbone and holds all configuration information and historical performance data. This article outlines five common methods for backing up your DataStore.
| Info | ||
|---|---|---|
| ||
| These backup methods are intended for a single Monitoring Station. Never attempt to merge two or more Monitoring Station configurations in a single database. |
...
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 up.time to be stopped during the backup period.
...
- Archive the datastore directory.
On a Windows system:
- Locate the up.time install directory (default
C:\Program Files\uptime software\uptime). - Archive the
\datastoredirectory (using an archiving tool such as Winzip). - Move the zip archive to another system or drive.
On a Unix system, enter the following commands:
Code Block # cd /usr/local/uptime OR cd /opt/uptime (depending on the OS) # tar -cvf uptime_backup.tar datastore # gzip uptime_backup.tar
- Locate the up.time install directory (default
- Start the up.time services. - Review Starting and Stopping up.time
Option 2: Using the mysqldump Tool
mysqldump is a free utility included with the standard up.time 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.
...
| Code Block |
|---|
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.
...
- MySQL Online Documentation: How to Set Up Replication.
- up.time 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 to Backup
The following files are not part of the DataStore but should also be backed up on a regular basis, especially if they have been modified or tuned.
...