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 two types of data:

Performance data: This is the data gathered by OpManager by periodically polling or querying the resources on a monitored device to determine its performance. This includes resources like CPU, Memory, Response time, Traffic etc.

Configuration data: There are quite a few configurations an administrator effects in OpManager for easy management and monitoring. The configurations include user settings, details of discovered devices, custom monitors, threshold settings, notification profiles, etc.

Please note that the given steps below is applicable for OpManager builds from 126119.

Steps to backup data:

  • Open command prompt with administrative privileges and go to < OpManager Home>/bin/backup directory.
  • Execute BackupDB.bat (use BackupDB.sh for Linux) from the command prompt as shown below
  • < OpManager Home>/bin/backup>BackupDB.bat
  • Enter the password as per the given instructions. (Backup passwords will not be stored anywhere, so users must ensure they remember the passwords.)
  • Provide the password hint. (Optional)
  • The backup process will begin.
  • The backup file created will be stored in < OpManager Home>\backup directory.
  • To store in a different destination use the command given here: BackupDB.bat -destination "<DestinationFolderPath>" (Eg : BackupDB.bat -destination "C:\Backup").
  • Please ensure to store the backup file in a different directory and not in OpManager's home or sub directories. However, you can use <OpManager Home>/backup directory to store the backup file.

Note: This utility does a backup of the complete database, i.e., performance and configuration data. Only the configuration data will be backed up for Netflow Analyzer and Firewall Analyzer modules.

To backup only the configuration data:

  • Open command prompt with administrative privileges and go to < OpManager Home>/bin/backup directory and execute the below command:

< OpManager Home>/bin/backup>BackupDB.bat -mode configdata

  • This is used to backup only the configuration data (Backup Conf., Images folder, the details of Devices, Device Templates, Interfaces, Interface Template, Dashboards & Widgets, Infrastructure Views, Business Views, Credentials, Notification Profiles and Users) and not the performance data.

Live database backup feature has been introduced for bundled PGSQL setups, from version 127189. Users can now backup a copy of a database while it is still operational.

Steps to restore data:

  • Open command prompt with administrative privileges and go to < OpManager Home>/bin/backup directory.
  • Execute RestoreDB.bat (use RestoreDB.sh for Linux) with the backup file name as argument from the command prompt as shown below:

< OpManager Home>/bin/backup>RestoreDB.bat "<Backup file name with path>"
(Eg: RestoreDB.bat "C:\backup\Backup_Pgsql_Mar8_125128_123313.zip" )

  • Enter the password for the backup zip file
  • The restoration process will begin.

Note:

1. For MSSQL database,
  • In Windows: Find the files bcp.exe and bcp.rll in MSSQL server and ensure to copy it to OpManagerHome\bin folder. If the MSSQL server is installed on a 64-bit OS, and OpManager is installed on 32-bit server, the bcp.exe and bcp.rll copied from the MSSQL server will not work on the OpManager machine. You'll need a 32-bit bcp.exe and bcp.rll
  • In Linux: Copy the 'bcp' and 'bcp.rll' files from the subfolders of /opt/mssql-tools/ directory. If the files are missing in the mssql-tools folder, or the folder itself is missing, please refer this link for more details.

2. The backup files taken during the upgrade process cannot be restored.

Thank you for your feedback!

Was this content helpful?

We are sorry. Help us improve this page.

How can we improve this page?
Do you need assistance with this topic?
By clicking "Submit", you agree to processing of personal data according to the Privacy Policy.