Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

  1. Stop the Uptime Infrastructure Monitor services.
  2. Archive the datastore directory.
    • On a Windows system:
      1. Locate the Uptime Infrastructure Monitor install directory (default C:\Program Files\uptime software\uptime).
      2. Archive the \datastore directory (using an archiving tool such as Winzip).
      3. Move the zip archive to another system or drive.
    • On a Unix system, enter the following commands:
      Code Block
      languagesql
      # cd /usr/local/uptime OR cd /opt/uptime 
      (depending on the OS)
      # tar -cvf uptime_backup.tar datastore 
      # gzip uptime_backup.tar


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

...

Info

Before importing data, you must stop the UIM services. For more information, see the topic above regarding Creating a tar or zip Archive section.

To import your backup data, run the following command:

Code Block
languagesql
mysql/bin/mysql -q -f -u uptime -puptime -P3308 --protocol=tcp uptime < mybackup.sql

This process will attempt 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 will erase ALL erases all of the data in your existing DataStore; be . Be absolutely sure that a full backup recovery is your best option before running this command.

Code Block
languagesql
resetdb really --nodata

Option 3: MySQL replication

...

Information on starting replication can be found at:

  • MySQL Online Documentation: How to

...

...

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  

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 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.

Code Block
languagesql
<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 remember 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 should also back up those custom files up as well.