Date: Thu, 28 Mar 2024 22:12:26 +0000 (UTC) Message-ID: <245220835.5529.1711663946413@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5528_588056383.1711663946411" ------=_Part_5528_588056383.1711663946411 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Contents
Performing regular backups of your Uptime Infrastructure Monitor DataSto= re is a highly recommended practice. The DataStore is the Uptime Infrastruc= ture Monitor backbone and holds all configuration information and historica= l performance data. This article outlines five common methods for backing u= p your DataStore. It is recommended to choose at least one of these m= ethods to back up your Uptime DataStore. For added safety, you can im= plement more than one of the options below in case one of the methods shoul= d falter. Only one of the options below can be used to restore a back= up; the methods cannot be merged when restoring the backup.
Note
In addition to backing up the Uptime DataStore, it is also important to = back up the Uptime configuration files and any customized files. Be s= ure to follow the recommendations in the Other Files and Dire= ctories to Backup section at the bottom of this article.
One backup option is to regularly create tar or zip archives of your
To use this method, simply include the /datastore
directory in the tar/zip archive. If you need to r=
ecover your DataStore from a tar/zip archive, ensure that all Uptime Infras=
tructure Monitor services are stopped and that you delete the existing
On a Windows system= :
\datastore
directory (using an archiving tool =
such as Winzip).On a Unix system, enter the following commands:
# cd /u= sr/local/uptime OR cd /opt/uptime (depending on the OS) # tar -cvf uptime_backup.tar datastore # gzip uptime_backup.tar
mysqldump is a free utility included with the standard Uptime Infrastruc= ture Monitor MySQL database. This tool will export DataStore contents into = a human readable .sql file that can later be used to recreate your DataStor= e. The commands below detail how to export both configuration and performan= ce data using mysqldump.
Note
The standard format for the mysqldump command is as follows:
mysqldu= mp --single-transaction -u[username] -p[password] -P[port #] --protocol=3Dt= cp [dbname]
By adding >
myback=
up.sql to the commands below, all mysqldump data will be directed to t=
he mybackup.sql file. The mybackup.sql fil=
e name should be changed to a date-stamped file name for easy reference.
Exporting Your Entire DataStore<= /span>
mysql/b= in/mysqldump --single-transaction -uuptime -puptime -P3308 --protocol=3DTCP= uptime > mybackup.sql
Note
[dbname]
variable may be uptime_v4
if your da=
tabase was created in Uptime Infrastructure Monitor 4.
Exporting Only Your =
Configuration Information
In version Uptime Infrastructure= Monitor 7.2 or later there is the feature to generate a Problem Report wit= h Configuration via the command line. One can schedule the execution = of the command line Problem Report with a cron job or scheduled task.
prexpor= t [-p] [-cN] Options: -p to dump last hour of data -c dump historical configuration; N is number of months defaults to 3 month= s
Alternatively, here are the configuration tables:
mysql/b= in/mysqldump -uuptime -puptime -P3308 --protocol=3Dtcp --ignore-table=3Duptime.erdc_decimal_data=20 --ignore-table=3Duptime.erdc_int_data=20 --ignore-table=3Duptime.erdc_string_data=20 --ignore-table=3Duptime.ranged_object_value=20 --ignore-table=3Duptime.performance_aggregate=20 --ignore-table=3Duptime.performance_cpu=20 --ignore-table=3Duptime.performance_disk=20 --ignore-table=3Duptime.performance_esx3_workload=20 --ignore-table=3Duptime.performance_fscap=20 --ignore-table=3Duptime.performance_lpar_workload=20 --ignore-table=3Duptime.performance_network=20 --ignore-table=3Duptime.performance_nrm=20 --ignore-table=3Duptime.performance_psinfo=20 --ignore-table=3Duptime.performance_sample=20 --ignore-table=3Duptime.performance_vxvol=20 --ignore-table=3Duptime.performance_who --ignore-table=3Duptime.archive_delenda=20 uptime > mybackup.sql
Exporting Only Your Historical P= erformance Data
mysql/b= in/mysqldump -uuptime -puptime -P3308 --protocol=3Dtcp 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 Da= ta
To import your backup data, run the following command:
mysql/b= in/mysql -q -f -u uptime -puptime -P3308 --protocol=3Dtcp uptime < mybac= kup.sql
This process will attempt to insert any non-duplicate data that is found= in your mybackup.sql file. If you need to rebuild your data= base from scratch, run the resetdb utility before importing = your backup file. This utility will erase ALL data in your existing DataSto= re; be absolutely sure that a full backup recovery is your best option befo= re running this command.
resetdb= really --nodata
MySQL replication is the most complex backup method but is the most powe= rful for quick recovery. MySQL's built-in replication feature will maintain= a completely up-to-date copy of your DataStore on another database instanc= e (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 ea= sily 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 utilit= y to export data from an Oracle database. Refer to the Oracle database util= ities page for more information:
If your DataStore is running on Microsoft SQL Server, you can use the SQ= L Backup tool to export data. Refer to the Microsoft Developer Network for = more information:
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.&n= bsp;
If you have configured SSL browsing in Apache, don't forget to back up t= he cert files in the <uptime_dir>/apache/conf directory.
If you have added MIB files to the <uptime_dir>/mibs director= y, you will want to back those custom files up as well.