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.
Note that these backup methods are intended for a single Monitoring Station. Never attempt to merge two or more Monitoring Station configurations in a single database.
One backup option is to regularly create tar or zip archives of your
To use this method, simply include the
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.
NOTE: The following sample commands are provided with the assumption that you are executing them from the up.time installation directory and that the default database access options have not been changed. If any parameters have changed, refer to your
The standard format for the mysqldump command is as follows:
mysqldump --single-transaction -u[username] -p[password] -P[port #] --protocol=tcp [dbname]
mysql/bin/mysqldump --single-transaction -uuptime -puptime -P3308 --protocol=TCP uptime > mybackup.sql
Exporting Only Your Configuration Information
mysql/bin/mysqldump -uuptime -puptime -P3308 --protocol=tcp
Exporting Only Your Historical Performance Data
mysql/bin/mysqldump -uuptime -puptime -P3308 --protocol=tcp uptime
Importing Your Backup Data
NOTE: Before importing data, you must stop the up.time services (see steps outlined in the Creating a tar or zip Archive section).
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 will attempt to insert any non-duplicate data that is found in your
resetdb really --nodata
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:
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:
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:
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.
As part of the initial install of up.time, the Monitoring Station itself is setup as an element within up.time. This sample element is initially setup to use localhost as it's hostname, along...
By: uptime Support | Date Created: 3-8-2013 | Last Modified: 3-8-2013 | Index: 592
Learn how to configure up.time to point to your Scrutinizer instance to enable click-through graphing, as well as an integrated Scrutinizer view from Global Scan.
By: uptime Support | Date Created: 7-8-2010 | Last Modified: 2-8-2013 | Index: 459
Use up.time to monitor the performance and health of Java applications running on WebSphere servers.
By: uptime Support | Date Created: 12-20-2006 | Last Modified: 7-26-2011 | Index: 108
By: uptime Support | Date Created: 6-9-2006 | Last Modified: 10-17-2013 | Index: 077
By: uptime Support | Date Created: 6-7-2006 | Last Modified: 8-9-2011 | Index: 075