Data Backup and Restoration
Periodically
backing up the
database is very essential, as it helps you restore OpManager service
back
during planned maintenance as well as unplanned mishaps. OpManager
database contains performance data and the configuration data.
Performance data are the polled data of the devices that are managed
by
OpManager, while the configuration data contain details about the
configurations that are made in OpManager, which include user settings,
details
of discovered devices, custom monitors, threshold settings,
notification profiles, etc.
Backup
OpManager provides various backup options out-of-the-box that provide
real time backup according to your needs.
MySQL:
If you are using MySQL
that is bundled with OpManager as the backend database and sure about
the non-possibility of migrating to MSSQL in the near future, then you
can make use of the
batch files BackupDB_Mysql.bat/sh
or BackupDB_Mysql_Config.bat/sh
[<OpManager
Home>/bin/backup]
to backup the database. The advantage of using these batch files is
that you can backup the database very quickly. BackupDB_Mysql.bat/sh takes a
backup of the entire database, while BackupDB_Mysql_Config.bat/sh
takes a backup of the configuration data alone, which will be very
helpful if you want to re-establish the existing OpManager setup in
another machine leaving the performance data.
MSSQL:
If you are using MSSQL, then use the
batch files
BackupDB.bat/sh or BackupDB_Config.bat/sh [<OpManager
Home>/bin/backup]. BackupDB.bat/sh
takes a backup of the entire database, while
BackupDB_Config.bat/sh takes a
backup of the configuration data alone.
You can also use Microsoft SQL
Enterprise Manager to backup the database. If so, then once you
complete taking the backup, also execute the batch file
BackupConfFiles.bat [<OpManager
Home>/bin/backup], because the SQL Enterprise Manager backups only the
database leaving
the configuration files which are required to run OpManager properly.
Across DB:
If you are using MySQL
as the backend database, but have an idea of migrating to MSSQL later
or wishing
to migrate to MSSQL now, then use the batch files
BackupDB.bat/sh or BackupDB_Config.bat/sh [<OpManager
Home>/bin/backup] to backup the database. The advantage with these
batch files is that you can restore the backed up data into MSSQL also.
Using third party tool:
If you are using any third party tool to back the database (MySQL or
MSSQL), then execute the batch file
BackupConfFiles.bat [<OpManager
Home>/bin/backup].
This is because, the third party tool backups only the database leaving
the configuration files which are required to run OpManager properly.
Name & Location of the backup
files
The name of the backup file that is created will be in this format
<filename>_<date>_<time>_<build
number>.zip eg: BackUp_APR3_2009_17_43_38_8100.zip. The backup files
are stored under OpManager
Home/backup directory.
If you want the backup file to be stored in some other directory
other
than the default directory (<OpManager
Home/backup>) in case of shortage of free space, then from the
command prompt execute the required
batch file with the path of the destination directory as argument. The
command for
doing so is
<backup execution command>
-destination <path of the
destination directory>
Example:
BackupDB_Mysql.bat -destination D:\OpManager_backup
Restoration
To restore the backed up data,
- Go
to <OpManager Home>/bin/backup
directory
- Execute
RestoreDB.bat/sh with
the backup file name as argument. See example below:
C:\<OpManager Home>\bin\backup>RestoreDB.bat
BackUp_APR3_2009_17_43_38_8100.zip
While restoring the backup, the tables that are dropped or retained
varies according to the backup file restored:
- BackupDB.bat/sh:
During restoration, all the existing tables are dropped, new tables are
created,
and the data are restored.
- BackupDB_Config.bat/sh: During
restoration, all the existing tables are dropped, new tables are
created, and only the configuration data are restored.
- BackupDB_Mysql.bat/sh:
During
restoration, all the existing tables are dropped, new tables are
created,
and the data are restored.
- BackupDB_Mysql_Config.bat/sh:
During
restoration, all the existing tables are dropped, new tables are
created, and only the configuration data are restored.
- BackupConfFiles.bat/sh:
During restoration, no tables get dropped. Only the configurations
files are restored.
Copyright © 2005-2009,
ZOHO Corp. All Rights Reserved.