Skip Headers
Oracle® Communications Network Integrity System Administrator's Guide
Release 7.2.2

Part Number E36030-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

6 Backing Up and Restoring Network Integrity Data

This chapter describes how to back up and restore Oracle Communications Network Integrity data. It covers the following topics:

About Backup in Network Integrity

You can backup discovered data and application configurations using Network Integrity. Network Integrity has an effective backup mechanism which can be set up to run at regular time intervals for a systematic backup of all the required Network Integrity data and configuration, and also restore it as and when required. One option is to perform a routine backup on a daily basis setting it up as an overnight process.


You must perform regular database integrity checks. It is recommended that this check be performed on the backed-up database, and not the live system.

Data can be backed up even if the server is not running, or if the database is not in use.

For more information about backup, and to perform a backup, see the Oracle Fusion Middleware documentation at the following location:

About Backing up Data

All data is critical and has to be backed up. There is no data which can be considered non-critical and hence not be backed up. Network Integrity backs up the following information:

  • Database information

    This type of data is database driven or database specific. Following are the database information types:

    • Network Integrity tablespaces: Contains information on configuration, scans, and discrepancies along with Network Integrity configuration. This information can be viewed using the Mbean console.

    • ESS tablespaces: Contains information on scheduled jobs for scheduler or blackout.

    • ESS metadata store: Contains the Applcore database repository for storing scheduled job definitions. For example, startscanjob, blackoutjob, and stopscanjob.

    • WebLogic persistent store: Contains information responsible for persisting the scan, discrepancy, and assimilation of jobs (if a job failure such as a server failure, it ensures that the job is resumed and completed.)

  • Domain configuration

    This type of data contains information about the following:

    • Connection pool sizes (database, SNMP JCA)

    • Workmanager (thread pools) for cartridges

    • Security configuration (SSL), security providers (embedded LDAP or Oracle Internet Directory)

    • Other J2EE resources (JMS queues, topics, cluster configuration, and loadbalancing etc)

      • Work managers

      • GC parameters

      • Domain configuration files (set and so on)

      • Data sources

      • Java Message Service (JMS) resource configurations

      • Installed applications

  • Security provider

    This type of data contains users/roles in LDAP provider (embedded LDAP or Oracle Internet Directory). If you use embedded LDAP, data is backed up as part of WebLogic domain backup. If you use external LDAP or any other system, you must follow the backup mechanism specifically mentioned in that software.

Backup Data in Offline and Online Modes

You can backup data in both offline and online modes. A complete high availability and disaster recovery strategy requires dependable data backup, restore, and recovery procedures. You can use Oracle Recovery Manager (RMAN), a command-line and Oracle Enterprise Manager-based tool for backing up and recovering your database. RMAN provides block-level corruption detection during backup and restore and optimizes performance and space consumption with file multiplexing and backup set compression. You can integrate RMAN with Oracle Secure Backup and third party media management products for tape backup.

About Restore in Network Integrity

Restore is a method whereby lost data can be recovered completely. Network Integrity has a restore feature that works as a recovery strategy for outages that involve actual data loss or corruption, host failure, or media failure where the host or disk cannot be restarted and are permanently lost. This type of failure requires some type of data restoration before the Oracle Fusion Middleware environment can be restarted and continue with normal processing.

For more information on recovering data and for steps on recovering data, see the Oracle Fusion Middleware documentation at the following location:

Restoring In a Cluster Environment

In a cluster environment, if a Network Integrity adaptor is installed on the Administration server and the server fails, restore the entire server using a backup.

If a Network Integrity adaptor is installed on a managed server and the server fails, follow these steps to restore the server:

  1. Add a new managed server to the cluster on the same system.

  2. Deploy all Network Integrity components on this managed server.