9 Disaster Recovery

This chapter provides high-level information for configuring for disaster recovery on the Exalytics Machine.

You can find information about disaster recovery in the following sources:

• For Oracle Business Intelligence, see "Recommendations for Oracle Business Intelligence" in Oracle Fusion Middleware Disaster Recovery Guide.

  Note that disaster recovery of an Oracle Business Intelligence deployment on an Exalytics server to an Oracle Business Intelligence deployment on a non-Exalytics server (IBM, Dell, and so on) is supported. When using rsync, a file synchronization program to synchronize data between the two servers, ensure that you exclude the NQSConfig.INI and the biee-domain.xml files. Table 9-1 shows the configuration files you must exclude.

  Table 9-1 Files to Exclude When Synchronizing Data

  Configuration Files
  $DOMAIN_HOME/user_projects/domains/bifoundation_domain/config/fmwconfig/biee-domain.xml
  instances/instance1/config/OracleBIServerComponent/coreapplication_obis1/NQSConfig.INI

  
  

• For Oracle TimesTen, you must carefully manage the way in which an Oracle BI repository and aggregates are replicated from the main site to the disaster recovery site. You must exactly mirror on the disaster recovery site system the sequence of operations that you apply on the production system for the repository and aggregates, in particular:

  • When a new repository is uploaded to the production system, then the same repository must be uploaded on the disaster recovery site system.

  • When aggregate scripts are run against the production repository and instances of Oracle TimesTen, then the same aggregate scripts must be run against the disaster recovery site system.

    For information, see "Using Oracle BI Summary Advisor to Identify Query Candidates for Aggregation" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.