How the Infobright Database Backup Works
Infobright database backups are enabled during installation. Because Infobright data is continuously backed up, you cannot change the backup timing or perform a manual backup.
The working directory for creation and processing of backup files is the “ibdlp” directory in persistency.xml, located on the Prime Network gateway and units. The location of this directory is specified during installation. To identify the location of the working directory, enter:
cd Main; ./runRegTool.sh localhost get persistency/nodes/infobright/ibdlp
The following sub-directories are created under the ibdlp directory:
The flow of the Infobright database backup is as follows:
1. Prime Network processes, such as auto-archive, AVM 25 and AVM 100, write data to the Infobright database and generate a text file in the DLP_Active_Files directory for each fault and event persistency (EP) table (HP_TRAP, HP_SYSLOG, NETWORKEVENT, ALARM, TICKET, NEWTRAPEVENT, NEWTRAPVALUE).
2. The text file is closed after one hour and moved to the DLP_Input_Files directory.
3. Every ten minutes, a cron job DLP process generates a compressed Infobright backup file from the closed text file and places it in the DLP_Output_Files directory. It also creates a log file under the DLP_Log_Files directory. If the cron job DLP process fails, a RJCT file is generated and placed in the DLP_Rjct_Files directory, and a system event is generated.
This cronjob is configured under prime-network crontab: $SHEERHOME/Main/unix/cron/every_10_minutes.main.gateway.cmd DLPProcessExecuter
4. A cron job SCP process transfers the backup file from the DLP_Output_Files directory to the backup directory on the database server (ibbackup). The path to this directory is specified during installation.
This cronjob is configured under root crontab:
*/10 * * * * /var/adm/cisco/infobright/move_dlp_files.sh >/dev/null 2>&1
Changing Settings for Purging Infobright
By default, backups are purged after 180 days.
To change the settings for purging Infobright backups:
Step 1 Log into the gateway and change to the Main directory.
Step 2 Check the current backup purge setting for Infobright backups:
./runRegTool.sh -gs 127.0.0.1 get 0.0.0.0 site/persistency/nodes/infobright/bkp_history
Step 3 To change the setting, specify the number of days after which backups should be purged.
# ./runRegTool.sh localhost 127.0.0.1 set 0.0.0.0 site/persistency/nodes/infobright/bkp_history value
Step 4 Log into the Infobright DB server as root user. From the following script, edit the
to reflect the new setting:
Recovering the Infobright Database
The Infobright recovery procedure can be used to load backup files into a fresh Infobright database. To do this, prepare the following:
A backup directory containing all your backup files.
A fresh installation of the Infobright database.
To recover the Infobright database:
Step 1 Rename the
directory or save it to a different location, to prevent the directory from being removed during the uninstall procedure. For example:
mv ibbackup ibbackup_old.
Step 2 Reinstall the Infobright database. This creates a fresh database, which is required for the recovery process.
Step 3 Log into the Infobright database server as the Infobright UNIX root user, and move to the following directory:
# cd /var/adm/cisco/infobright
Step 4 Start the recovery script:
You will be prompted for the following information:
The Infobright schema name. Use the default (
The path to the directory containing your backup files (see Step 1).
The script will list the available date ranges for the recovery operation.
Step 5 Choose the recovery option you require.
Recover all the backed up data
1. FULL LOAD
Recover only backed up data from a specified time period
2. PARTIAL LOAD
Step 6 If you chose PARTIAL LOAD, enter the start and end time when prompted.
Restarting the Recovery Process After a Recovery Failure
To restart the recovery process after an interruption or recovery failure:
Step 1 Start the recovery script:
Step 2 Choose
3. RESUME A FAILED LOAD SESSION
Step 3 Enter the same information (schema and backup directory) as you did for the interrupted/failed recovery.
Step 4 When the script displays the previous recovery ID, type, and start time, confirm the choice. (The script automatically uses the information from the last recovery operation.)
Step 5 Check the recovered tables for duplicates.
a. Start the recovery script:
4. CHECK DUPLICATES
– If duplicates are found in a production system, repeat the recovery process.
– If duplicates are found in a test setup, you can rerun the recovery script with option
5. TRUNCATE FAULT AND EVENT ARCHIVE (EP) TABLES - Truncate tables in preparation for load.
" and then repeat the recovery process.
c. Enter the same information (schema and backup directory) as you did for the interrupted restoration.
Recovery Log Files
For each operation (full load, partial load, resume failed operation, truncate tables), a log is created and placed in /usr/local/infobright/IBRestore/Log/IBRestore_
If the recovery process fails, you can investigate further by querying the following Infobright tables under pnibdb schema:
PNIB_RECOVERY_INFO - Holds one row for each recovery run
PNIB_RECOVERY_LOG - Holds many rows for each recovery run, with detailed information about the activities and files involved.
Backup and Restore Customized Reports
To backup and restore Customized reports:
Step 1 Copy the primenetwork-reports folder to your local server.
Step 2 Rename the ibbackup directory or save ibbackup directory to a different location. This is to prevent the directory from being removed during uninstallation.
Example: mv ibbackup ibbackup_old.
Step 3 Re-install the Prime Network, Oracle and Operations Reports.
Step 4 After re-installation, remove the primenetwork-reports directory.
For example, remove the primenetwork-reports from $ANA_HOME/pentaho/server/biserver-ee/pentaho-solutions/primenetwork-reports.
Step 5 Paste the primenetwork-reports directory.
Note You must paste the primenetwork-reports directory which you already have on your local machine to the location “$ANA_HOME/pentaho/server/biserver-ee/pentaho-solutions/”
Step 6 Change the primenetwork-reports folder permission to pnusername:ana
For example, if pn user name is pn50, then the permission should be pn50:ana.
Step 7 To recover the database follow the steps mentioned in the Recovering the Infobright Database procedure.
Step 8 Launch the Prime Network Operations reports by manually entering the following URL in your browser address field:
https:// < gateway-IP >:< port-number >/ prime-network-reports/Login and view the Customized report.
If the Customized report is not available, do the following
to view your customized report under the Files pane.
Note Files pane is located at the left bottom of the home page.