16 Introducing Backup and Recovery

This chapter provides an introduction to backing up and recovering Oracle Fusion Middleware.

This chapter includes the following topics:

16.1 Understanding Oracle Fusion Middleware Backup and Recovery

An Oracle Fusion Middleware environment can consist of different components and configurations. A typical Oracle Fusion Middleware environment contains an Oracle WebLogic Server domain with Java components, such as Oracle SOA Suite, and a WebLogic Server domain with Identity Management components. It can also include Oracle instances containing system components such as Oracle HTTP Server, Oracle Web Cache, Oracle Internet Directory, and Oracle Virtual Directory.

The installations of an Oracle Fusion Middleware environment are interdependent in that they contain configuration information, applications, and data that are kept in synchronization. For example, when you perform a configuration change, information in configuration files is updated. When you deploy an application, you might deploy it to all Managed Servers in a domain or cluster.

It is, therefore, important to consider your entire Oracle Fusion Middleware environment when performing backup and recovery. You should back up your entire Oracle Fusion Middleware environment at once, then periodically. If a loss occurs, you can restore your environment to a consistent state.

The following topics describe concepts that are important to understanding backup and recovery:

See Also:

  • Section 2.2 for conceptual information about an Oracle WebLogic Server domain

  • Section 2.2.1 for conceptual information about the Administration Server

  • Section 2.2.2 for conceptual information about Managed Servers and clusters

  • Section 2.2.3 for conceptual information about Node Manager

16.1.1 Impact of Administration Server Failure

The failure of an Administration Server does not affect the operation of Managed Servers in the domain but it does prevent you from changing the domain's configuration. If an Administration Server fails because of a hardware or software failure on its host computer, other server instances on the same computer may be similarly affected.

If an Administration Server for a domain becomes unavailable while the server instances it manages—clustered or otherwise—are running, those Managed Servers continue to run. Periodically, these Managed Servers attempt to reconnect to the Administration Server. For clustered Managed Server instances, the load balancing and failover capabilities supported by the domain configuration continue to remain available.

When you first start a Managed Server, it must be able to connect to the Administration Server to retrieve a copy of the configuration. Subsequently, you can start a Managed Server even if the Administration Server is not running. In this case, the Managed Server uses a local copy of the domain's configuration files for its starting configuration and then periodically attempts to connect with the Administration Server. When it does connect, it synchronizes its configuration state with that of the Administration Server.

16.1.2 Managed Server Independence (MSI) Mode

A Managed Server maintains a local copy of the domain configuration. When a Managed Server starts, it contacts its Administration Server to retrieve any changes to the domain configuration that were made since the Managed Server was last shut down. If a Managed Server cannot connect to the Administration Server during startup, it can use its locally cached configuration information—this is the configuration that was current at the time of the Managed Server's most recent shutdown. A Managed Server that starts without contacting its Administration Server to check for configuration updates is running in Managed Server Independence (MSI) mode. By default, MSI mode is enabled. However a Managed Server cannot be started even in MSI mode for the first time if the Administration Server is down due to non-availability of the cached configuration.

16.1.3 Configuration Changes in Managed Servers

Configuration changes are updated in a Managed Server during the following events:

  • On each Managed Server restart, the latest configuration is retrieved from the Administration Server. This happens even when the Node Manager is down on the node where the Managed Server is running. If the Administration Server is unavailable during the Managed Server restart and if the MSI (Managed Server Independence) mode is enabled in the Managed Server, it starts by reading its local copy of the configuration and synchronizes with the Administration Server when it is available. By default MSI mode is enabled.

  • Upon activating every administrative change such as configuration changes, deployment or redeployment of applications, and topology changes, the Administration Server pushes the latest configuration to the Managed Server. If the Managed Server is not running, the Administration Server pushes the latest version of the configuration to the Managed Server when it does start.

16.2 Oracle Fusion Middleware Directory Structure

The following shows a simplified view of the Oracle Fusion Middleware directory structure:

Description of dir.gif follows
Description of the illustration dir.gif

16.3 Overview of the Backup Strategies

To back up your Oracle Fusion Middleware environment, you can use:

  • File copy utilities such as copy, xcopy, tar, or jar. Make sure that the utilities:

    • Preserve symbolic links

    • Support long file names

    • Preserve the permissions and ownership of the files

    For example:

    • On Windows, for online backups, use copy; for offline backups, use copy, xcopy, or jar. Do not use Winzip because it does not work with long filenames or extensions.

      Note that for some versions of Windows, any file name with more than 256 characters will fail. You can use the xcopy command with the following switches to work around this issue:

      xcopy /s/e  "C:\Temp\*.*"  "C:\copy"

      See the xcopy help for more information about syntax and restrictions.

    • On Linux and UNIX, for online and offline backups, use tar.

  • Oracle Recovery Manager (RMAN) to back up database-based metadata repositories.

If you want to retain your backups for a longer duration, you may want to back up to tape, for example using Oracle Secure Backup.

You can also configure Oracle WebLogic Server to make backup copies of the configuration files. This facilitates recovery in cases where configuration changes need to be reversed or in the unlikely case that configuration files become corrupted. When the Administration Server starts, it saves a .jar file named config-booted.jar that contains the configuration files. When you make changes to the configuration files, the old files are saved in the configArchive directory under the domain directory, in a .jar file with a sequentially numbered name such as config-1.jar. However, the configuration archive is always local to the Administration Server host. It is a best practice to back up the archives to an external location.

16.3.1 Types of Backups

You can back up your Oracle Fusion Middleware environment offline or online:

  • An offline backup means that you must shut down the environment before backing up the files. When you perform an offline backup, the Administration Server, all Managed Servers in the domain, and all system components in the Oracle instances should be shut down.

    Back up the environment offline immediately after installation and after applying any patches or upgrades.

  • An online backup means that you do not shut down the environment before backing up the files. To avoid an inconsistent backup, do not make any configuration changes until the backup is completed. To ensure that no changes are made in the WebLogic Server domain, lock the WebLogic Server configuration, as described in Section 3.4.2.

You can perform backups on your full Oracle Fusion Middleware environment, or on the run-time artifacts, which are those files that change frequently.

To perform a full backup, you should back up the static files and directories, as well as run-time artifacts.

Static files and directories are those that do not change frequently. These include:

  • The Middleware home (MW_HOME). A Middleware home consists of a WebLogic Server home (containing the Oracle WebLogic Server product directories), an Oracle Common home, and optionally an Oracle home. It can also contain the user_projects directories, which contains Oracle WebLogic Server domains and Oracle instance homes, which are not static files.

  • OraInventory

  • OraInst.loc and oratab files, which are located in the following directory:

    (Linux and IBM AIX) /etc
(Other UNIX systems) /var/opt/oracle

  • The beahomelist file, which is located at:

    (UNIX) user_home/bea/beahomelist
(Windows) C:\bea\beahomelist

  • On Windows, the following registry key:

    HKEY_LOCAL_MACHINE\Software\oracle

    In addition, for system components, such as Oracle Web Cache, you must back up the following Windows Registry key:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

Run-time artifacts are those files that change frequently. Back up these files when you perform a full backup and on a regular basis. Run-time artifacts include:

  • Domain directories of the Administration Server and the Managed Servers (by default, a domain directory resides in MW_HOME, but it can be configured by the user to point to a different location.)

    In most cases, you do not need to back up Managed Server directories separately because the Administration Server contains information about all of the Managed Servers in its domain.

  • All Oracle instance homes, which reside, by default, in the MW_HOME but can be configured to be in a different location.

  • Application artifacts, such as .ear or .war files that reside outside of the domain.

    You do not need to back up application artifacts in a Managed Server directory structure because they can be retrieved from the Administration Server during Managed Server startup.

  • Database artifacts, such as the MDS Repository.

  • Any database-based metadata repositories used by Oracle Fusion Middleware. You use Oracle Recovery Manager (RMAN) to back up an Oracle database.

  • Persistent stores, such as JMS Providers and transaction logs, which reside by default in the user_projects directory, but can be configured in a different location. However, note the limitation described in Section 17.2.

16.3.2 Recommended Backup Strategy

This section outlines the recommended strategy for performing backups. Using this strategy ensures that you can perform the recovery procedures in this book.

  • Perform a full offline backup: This involves backing up the entities described in Section 16.3.1. Perform a full offline backup at the following times:

    • Immediately after you install Oracle Fusion Middleware

    • Immediately before upgrading your Oracle Fusion Middleware environment

    • Immediately after an operating system software upgrade

    • Immediately after upgrading or patching Oracle Fusion Middleware

  • Perform an online backup of run-time artifacts: This involves backing up the run-time artifacts described in Section 16.3.1. Backing up the run-time artifacts enables you to restore your environment to a consistent state as of the time of your most recent configuration and metadata backup. To avoid an inconsistent backup, do not make any configuration changes until backup completes. Perform an online backup of run-time artifacts at the following times:

    • On a regular basis. Oracle recommends that you back up run-time artifacts nightly.

    • Prior to making configuration changes to a component or cluster.

    • After making configuration changes to a component or cluster.

    • Prior to deploying a custom Java EE application to a Managed Server or cluster.

    • After a major change to the deployment architecture, such as creating servers or clusters.

  • Perform an offline backup of static files and directories: This involves backing up the static files and directories described in Section 16.3.1. Perform an offline backup of static files and directories at the following times:

    • After patching your Oracle Fusion Middleware environment. This backup serves as the basis for subsequent online backups.

    • After upgrading your Oracle Fusion Middleware environment. This backup serves as the basis for subsequent online backups.

16.4 Overview of Recovery Strategies

Recovery strategies enable you to recover from critical failures that involve actual data loss. Depending on the type of loss, they can involve recovering any combination of the following types of files:

  • Oracle software files

  • Configuration files

  • Metadata repository files

  • Oracle system files

  • Windows Registry keys

  • Application artifacts

You can recover your Oracle Fusion Middleware environment while Oracle Fusion Middleware is offline.

To recover your Oracle Fusion Middleware environment, you can use:

  • File copy utilities such as copy, xcopy, or tar

    When you restore the files, use your preferred tool to extract the compressed files:

    • On Windows, for online recovery, use copy; for offline recovery, use copy, xcopy, or jar.

      Note that for some versions of Windows, any file name with more than 256 characters will fail. You can use the xcopy command with the following switches to work around this issue:

      xcopy /s/e  "C:\Temp\*.*"  "C:\copy"

      See the xcopy help for more information about syntax and restrictions.

      Do not use Winzip because it does not work with long filenames or extensions.

    • On Linux and UNIX, use tar.

    Ensure that the tool you are using preserves the permissions and timestamps of the files.

  • Oracle Recovery Manager (RMAN) to recover database-based metadata repositories

16.4.1 Types of Recovery

You can recover your Oracle Fusion Middleware environment in part or in full. You can recover the following:

  • The Middleware home

  • A domain

  • The WebLogic Server Administration Server

  • A Managed Server

  • An Oracle home

  • An Oracle instance home

  • A component, such as Oracle SOA Suite or Oracle Web Cache

  • A cluster

  • Deployed applications

16.4.2 Recommended Recovery Strategies

Note the following key points about recovery:

  • Your Oracle Fusion Middleware environment must be offline while you are performing recovery.

  • Rename important existing files and directories before you begin restoring the files from backup so that you do not unintentionally override necessary files.

  • Although, in some cases, it may appear that only one or two files are lost or corrupted, you should restore the directory structure for the entire element, such as an Oracle instance home or a domain, rather than just restoring one or two files. In this way, you are more likely to guarantee a successful recovery.

  • Recover the database to the most current state, using point-in-time recovery (if the database is configured in Archive Log Mode). This is typically a time right before the database failure occurred.

16.5 Backup and Recovery Recommendations for Oracle Fusion Middleware Components

The following sections describe backup and recovery recommendations for specific Oracle Fusion Middleware components:

These topics include information about configuration files for particular components. Note that the list of files in not an exhaustive list. You do not back up or recover the individual files. Generally, you back up or recover a Middleware home, the domain, Managed Server, Oracle home, or Oracle instance.

For the steps you take to back up your environment, see Section 17.3. For the steps you take to recover a component, see Chapter 18.

16.5.1 Backup and Recovery Recommendations for Oracle WebLogic Server

The following sections describe backup and recovery recommendations for Oracle WebLogic Server:

16.5.1.1 Backup and Recovery Recommendations for Oracle WebLogic Server

This section describes the Oracle WebLogic Server data that must be backed up and restored.

Configuration Files

Configuration files and applications are stored in the domain home.

Database Repository Dependencies

Oracle WebLogic Server does not, by default, depend on any database repository. However, applications deployed on Oracle WebLogic Server may use databases as data sources. To back up a database, see the Oracle Database Backup and Recovery User's Guide, which is available at:

http://www.oracle.com/technology/documentation/database.html

Backup Recommendations

Back up the Middleware home and the domain.

Recovery Recommendations

Depending on what has failed, you may need to recover the following:

If you use Whole Server Migration, the leasing information is stored in a table in a database. If you recover Oracle WebLogic Server, you should discard the information in the leasing table. (For more information about Whole Server Migration, see "Whole Server Migration" in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server.)

After a loss of host, you may need to recover the following:

16.5.1.2 Backup and Recovery Recommendations for Oracle WebLogic Server JMS

This section describes the Oracle WebLogic Server JMS data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/jms

If a JMS uses file-system accessible stores, the default file-system store is either in a user-configured location that is specified in config.xml, or in the following location:

DOMAIN_HOME/servers/server_name/data/store/default

Database Repository Dependencies

If a JMS uses a JDBC accessible store, back up the database.

Backup Recommendations

Back up the domain and the JMS file persistent store if it is not located within the domain.

Back up the schema in the database if JDBC-based persistent store is configured. Note the following:

  • All JMS data should be backed up using an offline backup.

  • Always try to keep JMS data as current as possible. This can be achieved by using the point-in-time recovery capabilities of Oracle Database (in the case of database-based persistence) or using a highly available RAID-backed storage device (for example, SAN/NAS).

  • It is currently not possible to take consistent backup of persistent stores for a system that uses JMS and transaction logs. This is because the transaction logs can only be file-based and the JMS can be either file-based or it can reside in the database. For highest reliability, use a highly available fault-tolerant storage (for example, SAN) for JMS and transaction log file stores.

  • If, for whatever reason, you need to restore JMS data to a previous point in time, there are potential implications. Restoring the system state to a previous point in time not only can cause duplicate messages, but can also cause lost messages. The lost messages are messages that were enqueued before or after the system restore point time, but never processed. If the persistent store is a custom store that is dedicated to JMS use, then you can delete the entire store.

    See additional information and limitations in Section 17.2.

    Use the following procedure before recovery to drain messages in the JMS queue after persistent-store recovery to avoid processing duplicate messages:

    Note:

    Do not drain and discard messages without first being certain that the messages contain no data that must be preserved. The recovered messages may include unprocessed messages with important application data, in addition to duplicate messages that have already been processed.

    1. Log into the Oracle WebLogic Server Administration Console.

    2. Before recovery, configure JMS server to pause Production, Insertion, and consumption operations at boot time to ensure that no new messages are produced or inserted into the destination or consumed from the destination before you drain stale messages. To do this:

      1. Expand Services, then Messaging, and then click JMS Servers.

      2. On the Summary of JMS Servers page, click the JMS server you want to configure for message pausing.

      3. On the Configuration: General page, click Advanced to define the message pausing options. Select Insertion Paused At Startup, Production Paused At Startup, and Consumption Paused At Startup.

      4. Click Save.

    Use the following procedure after recovery:

    1. After recovering the persistent store, start the Managed Servers.

    2. Drain the stale messages from JMS destinations, by taking the following steps:

      1. Expand Services, then Messaging, and then JMS Modules.

      2. Select a JMS module, then select a target.

      3. Select Monitoring, then Show Messages.

    3. Click Delete All.

    4. Resume operations, by taking the following steps:

      1. Expand Services, then Messaging, and then JMS Servers.

      2. On the Summary of JMS Servers page, click the JMS server you want to configure for message pausing.

      3. On the Configuration: General page, click Advanced. Deselect Insertion Paused At Startup, Production Paused At Startup, and Consumption Paused At Startup.

      4. Click Save.

    If the store is not dedicated to JMS use, use the Oracle WebLogic Server JMS message management administrative tool. This tool can perform import, export, move, and delete operations from the Administration Console, MBeans, and WLST.

    For applications that use publish and subscribe in addition to queuing, you should manipulate topic subscriptions in addition to queues.

Recovery Recommendations

Recover the domain.

If the JMS persistent store is file-based, recover it from backup. If the JMS persistent store is database-based, recover the database to the most recent point in time, if needed.

For the steps to recover the domain, see Section 18.2.2 and Section 18.3.1.

16.5.2 Backup and Recovery Recommendations for Oracle Identity Management

The following sections describe backup and recovery recommendations for Oracle Identity Management:

16.5.2.1 Backup and Recovery Recommendations for Oracle Internet Directory

This section describes the Oracle Internet Directory data that must be backed up and restored.

Configuration Files

ORACLE_INSTANCE/config/tnsnames.ora
ORACLE_INSTANCE/OID/admin
ORACLE_INSTANCE/OID/ldap/server/plugin
ORACLE_INSTANCE/OID/component_name
ORACLE_INSTANCE/config/OID/component_name

Database Repository Dependencies

ODS and ODSSM schemas

Backup Recommendations

Back up the Oracle Internet Directory component directory and the Oracle instance home that contains Oracle Internet Directory. Back up the database containing the ODS and ODSSM schemas.

Recovery Recommendations

Recover the Oracle instance home that contains Oracle Internet Directory.

Recover the database to the most recent point in time, if needed.

For the steps to recover the Oracle instance home that contains Oracle Internet Directory, see Section 18.2.4. For the steps specific to recovering from loss of host, see Section 18.3.4.5.1.

16.5.2.2 Backup and Recovery Recommendations for Oracle Virtual Directory

This section describes the Oracle Virtual Directory data that must be backed up and restored.

Configuration Files

ORACLE_INSTANCE/OVD/component_name
ORACLE_INSTANCE/config/OVD/component_name
ORACLE_INSTANCE/diagnostics/logs/OVD/component_name

Database Repository Dependencies

None

Backup Recommendations

Back up the Oracle instance home that contains Oracle Virtual Directory. Back up the database containing the ODSSM schema.

Recovery Recommendations

Restore the Oracle instance home that contains Oracle Virtual Directory.

For the steps to recover the Oracle instance home that contains Oracle Virtual Directory, see Section 18.2.4. For the steps specific to recovering from loss of host, see Section 18.3.4.5.2.

16.5.2.3 Backup and Recovery Recommendations for Oracle Directory Integration Platform

This section describes the Oracle Directory Integration Platform data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/dip_version_number/configuration/dip-config.xml

The file dip-config.xml is part of the Oracle Directory Integration Platform application. It is backed up when you back up the Administration Server domain.

Database Repository Dependencies

ODSSM schema, used by Oracle Internet Directory

Backup Recommendations

Back up the Administration Server domain directories, the Managed Server directories, and Oracle Internet Directory and its dependencies.

Recovery Recommendations

Recover the Managed Server where the Oracle Directory Integration Platform application is deployed.

Recover Oracle Internet Directory.

For the steps to recover the Managed Server, see Section 18.2.6. For the steps specific to recovering from loss of host, see Section 18.3.4.5.3.

16.5.2.4 Backup and Recovery Recommendations for Oracle Directory Services Manager

This section describes the Oracle Directory Services Manager data that must be backed up and restored.

Configuration Files

Oracle Directory Services Manager, which is the graphical user interface for Oracle Internet Directory and Oracle Virtual Directory, does not have configuration files, but keeps track of host and port information of Oracle Internet Directory and Oracle Virtual Directory in serverlist.txt, which is part of the application .ear file:

DOMAIN_HOME/servers/server_name/tmp/_WL_user/odsm_version/nx1i7i/war/WEB-INF/serverlist.txt

Database Repository Dependencies

None

Backup Recommendations

Back up the domain.

Recovery Recommendations

To restore Oracle Directory Services Manager, enter the user name and password to connect to Oracle Internet Directory or Oracle Virtual Directory.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.

16.5.2.5 Backup and Recovery Recommendations for Oracle Identity Federation

This section describes the Oracle Identity Federation data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/servers/server_name/stage/OIF/version/OIF/configuration

Database Repository Dependencies

OIF schema

Backup Recommendations

Back up the Administration Server domain, the Managed Server, and the database containing the OIF schema.

Recovery Recommendations

Recover the Managed Server where the Oracle Identity Federation application is deployed.

Recover the database to the most recent point in time, if needed.

For the steps to recover the Managed Server, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.5.4.

16.5.2.6 Backup and Recovery Recommendations for Oracle Access Manager

This section describes the Oracle Access Manager data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/fmwconfig/oam-config.xml

Database Repository Dependencies

The schema used by OES for the Oracle Access Manager policy store.

Backup Recommendations

Back up the Middleware home and the domain home for the Oracle Access Manager server. Back up the Oracle home and the Oracle instance for the Oracle HTTP Server that contains the Webgate, and the database containing the schema used by OES for the Oracle Access Manager policy store.

Recovery Recommendations

Recover the Middleware home and the domain home for the Oracle Access Manager server. Recover the Oracle home and the Oracle instance for the Oracle HTTP Server that contains the Webgate, as needed.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle Access Manager, see Section 18.2.7.5. For the steps specific to recovering from loss of host, see Section 18.3.4.5.7.

16.5.2.7 Backup and Recovery Recommendations for Oracle Adaptive Access Manager

This section describes the Oracle Adaptive Access Manager data that must be backed up and restored.

Configuration Files

Configuration files are located within the domain home.

Database Repository Dependencies

OAAM, OAAM_PARTN, and OAAM_OFFLINE schemas

Backup Recommendations

Back up the domain, the Oracle home, and the database containing the schemas.

Recovery Recommendations

Recover the domain or Oracle home depending on the extent of the failure.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle Adaptive Access Manager, see Section 18.2.7.6. For the steps specific to recovering from loss of host, see Section 18.3.4.5.8.

16.5.2.8 Backup and Recovery Recommendations for Oracle Identity Manager

This section describes the Oracle Identity Manager data that must be backed up and restored.

Configuration Files

Configuration files specific to Oracle WebLogic Server are located in the domain home. The Oracle Identity Manager configuration file, oim-config.xml, and other configurations are stored in MDS.

Because Oracle Identity Manager uses Oracle SOA Suite for workflow, see the configuration files for Oracle SOA Suite, described in Section 16.5.3.

Database Repository Dependencies

OIM, MDS, and Oracle SOA Suite schemas and, optionally, the OID schema

Backup Recommendations

Back up the domain, the Oracle home, and the database containing the schemas.

Recovery Recommendations

Recover the domain or Oracle home depending on the extent of the failure.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle Identity Manager, see Section 18.2.7.3. For the steps specific to recovering from loss of host, see Section 18.3.4.5.5.

16.5.2.9 Backup and Recovery Recommendations for Oracle Identity Navigator

This section describes the Oracle Identity Navigator data that must be backed up and restored.

Configuration Files

Configuration files are stored in a file-based MDS repository.

Database Repository Dependencies

MDS schema

Backup Recommendations

Back up the domain and the Oracle home. Back up the file-based MDS repository using the WLST exportMetadata command. For example:

exportMetadata(application='oinav',server='server_name',toLocation='export_directory')

Recovery Recommendations

Recover the domain, the Oracle home, and the file-based MDS repository.

For the steps to recover Oracle Identity Navigator, see Section 18.2.7.4. For the steps specific to recovering from loss of host, see Section 18.3.4.5.6.

16.5.3 Backup and Recovery Recommendations for Oracle SOA Suite

The following sections describe backup and recovery recommendations for Oracle SOA Suite:

For the steps you need to take to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.6.

16.5.3.1 Backup and Recovery Recommendations for Oracle BPEL Process Manager

This section describes the Oracle BPEL Process Manager data that must be backed up and restored.

Configuration Files

Configuration files are stored in the database.

Database Repository Dependencies

Process definition and configuration files are stored in the MDS schema. The dehydration store is stored in the BPEL schema.

Backup Recommendations

Back up the Administration Server domain directories. Back up the database after any configuration changes, including changes to global fault policies, callback classes for workflows and resource bundles that can potentially be outside the suitcase. Also back up the database after deploying a new composite or redeploying a composite.

Recovery Recommendations

Recover the database to the most recent point in time, if needed. Point-in-time recovery ensures that the latest process definitions and in-flight instances are restored. However, this may result in reexecution of the process steps. Oracle recommends that you strive for idempotent Oracle BPEL Process Manager processes. If the system contains processes that are not idempotent, you must clean them up from the dehydration store before starting Oracle Fusion Middleware. See the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite for more information.

Because instances obtain the process definition and artifacts entirely from the database, there is no configuration recovery needed after the database is recovered to the most current state; instances should continue to function correctly.

For redeployed composites, a database recovery ensures consistency between the dehydrated in-flight processes and their corresponding definition since the process definition is stored in database repository where dehydrated instances are also stored.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.6.

16.5.3.2 Backup and Recovery Recommendations for Oracle Business Activity Monitoring

This section describes the Oracle Business Activity Monitoring data that must be backed up and restored.

Configuration Files

SOA_ORACLE_HOME/bam
DOMAIN_HOME/config/fmwconfig/servers/AdminServer/adml/server-oracle_bamweb-11.0.xml
DOMAIN_HOME/config/fmwconfig/servers/AdminServer/adml/server-oracle_bamserver-11.0.xml
DOMAIN_HOME/config/fmwconfig/servers/bam-server-name/adml/server-oracle_bamweb-11.0.xml
DOMAIN_HOME/config/fmwconfig/servers/bam-server-name/adml/server-oracle_bamserver-11.0.xml

Database Repository Dependencies

ORABAM schema

Backup Recommendations

Back up the Middleware home, the Administration Server domain, the Managed Server directory, and the database containing the ORABAM schema.

Recovery Recommendations

Recover the Managed Server or the Middleware home, or both, depending on the extent of failure.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.6.

16.5.3.3 Backup and Recovery Recommendations for Oracle B2B

This section describes the Oracle B2B data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/soa-infra/configuration/b2b-config.xml

Database Repository Dependencies

MDS schema

Backup Recommendations

Back up the Administration Server domain, the Oracle home if changes are made to the Oracle B2B configuration file, and the database containing the MDS schema.

Recovery Recommendations

Recover the Managed Server where the soa-infra application is deployed.

Recover the database to the most recent point in time, if needed.

After recovery, if the file Xengine.tar.gz is not unzipped, unzip the files. For example:

cd B2B_ORACLE_HOME/soa/thirdparty/edifecs
tar xzvf XEngine.tar.gz

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.6.

16.5.3.4 Backup and Recovery Recommendations for Oracle Service Bus

This section describes the Oracle Service Bus data that must be backed up and recovered.

Configuration Files

DOMAIN_HOME/osb/config/core

Database Repository Dependencies

Oracle Service Bus requires a database if its reporting feature is enabled. It creates two tables, WLI_QS_REPORT_DATA and WLI_QS_REPORT_ATTRIBUTE, in a user-specified schema.

Backup Recommendations

Back up the Administration Server domain and the database containing the Oracle Service Bus tables.

Recovery Recommendations

Recover the Managed Server.

Recover the database to the most recent point in time, if needed.

For the steps you need to take to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.6.

16.5.3.5 Backup and Recovery Recommendations for Oracle Mediator

This section describes the Oracle Mediator data that must be backed up and restored.

For the steps you need to take to recover components, see Section 18.2.7 and Section 18.3.4.

For recommendations specific to recovering from loss of host, see Section 18.3.4.6.

Configuration Files

DOMAIN_HOME/config/soa-infra/configuration/mediator-config.xml
DOMAIN_HOME/config/soa-infra/configuration/mediator-xpath-functions-config.xml

Database Repository Dependencies

MDS and SOAINFRA schemas.

Backup Recommendations

Back up the Administration Server domain and the database containing the MDS and SOAINFRA schemas.

Recovery Recommendations

Recover the Managed Server where the soa-infra application is deployed.

Recover the database to the most recent point in time, if needed.

16.5.3.6 Backup and Recovery Recommendations for Oracle Business Rules

This section describes the Oracle Business Rules data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/soa-infra/configuration/businessrules-config.xml

Database Repository Dependencies

MDS schema

Backup Recommendations

Back up the Administration Server domain and the database containing the MDS schema.

Recovery Recommendations

Recover the Managed Server where the soa-infra application is deployed.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.6.

16.5.3.7 Backup and Recovery Recommendations for Oracle Business Process Management

For Oracle Business Process Management, you back up and restore the same data as Oracle BPEL Process Manager, as described in Section 16.5.3.1. This section describes data specific to Oracle Business Process Management.

Configuration Files

DOMAIN_HOME/config/fmwconfig/logging/oracle.bpm-logging.xml
DOMAIN_HOME/config/jms/bpmjmsmodule-jms.xml

Database Repository Dependencies

Process definition and configuration files are stored in the MDS schema.

Backup Recommendations

In addition to the recommendations for Oracle BPEL Process Manager, described in Section 16.5.3.1, you must back up the Oracle homes, including all Oracle homes in a cluster. When you extend a SOA domain to Oracle Business Process Management and configure Oracle Business Process Management, the process adds files to the Oracle Business Process Management Oracle home. However, it does not copy the files to any other Oracle homes in the cluster. After you configured Oracle Business Process Management, you should have copied the files to the other Oracle homes in the cluster. As a result, you must back up all Oracle homes in the cluster.

Recovery Recommendations

In addition to the recommendations for Oracle BPEL Process Manager, described in Section 16.5.3.1, you must recover all of the Oracle homes in the cluster.

For the steps to recover Oracle Business Process Management, see Section 18.2.7.7.

16.5.4 Backup and Recovery Recommendations for Oracle WebCenter

The following sections describe backup and recovery recommendations for Oracle WebCenter:

16.5.4.1 Backup and Recovery Recommendations for Oracle WebCenter

This section describes the Oracle WebCenter data that must be backed up and restored.

Configuration Files

All configuration files are bundled in the EAR file, which is located in the domain.

Database Repository Dependencies

WEBCENTER and MDS schemas

Backup Recommendations

Back up the Administration Server domain and the database containing the WEBCENTER and MDS schemas.

Recovery Recommendations

Recover the Oracle WebCenter domain.

Recover the database containing the WEBCENTER and MDS schemas to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.

16.5.4.2 Backup and Recovery Recommendations for Oracle WebCenter Portlet

This section describes the Oracle WebCenter Portlet data that must be backed up and restored.

Configuration Files

All configuration files are bundled in the EAR file, which is located in the domain.

Database Repository Dependencies

PORTLET schema

Backup Recommendations

Back up the Administration Server domain and the database containing the PORTLET schema.

Recovery Recommendations

Recover the Oracle WebCenter domain.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.

16.5.4.3 Backup and Recovery Recommendations for Oracle WebCenter Discussions Server

This section describes the Oracle WebCenter Discussions server data that must be backed up and restored.

Configuration Files

Some configuration files are either bundled in the EAR file, which is located in the domain, or the files are located elsewhere in the domain. Other configuration files are located in:

DOMAIN_HOME/fmwconfig/server/server_name/owc_discussions

Database Repository Dependencies

JIVE schema

Backup Recommendations

Back up the Administration Server domain and the database containing the JIVE schema.

Recovery Recommendations

Recover the Oracle WebCenter domain.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.

16.5.4.4 Backup and Recovery Recommendations for Oracle WebCenter Wiki and Blog Server

This section describes the Oracle WebCenter Wiki and Blog Server data that must be backed up and restored.

Configuration Files

Configuration files are bundled in the WAR file, which is located in the domain.

Database Repository Dependencies

WIKI schema

Backup Recommendations

Back up the Administration Server domain and the database containing the WIKI schema.

Recovery Recommendations

Recover the Oracle WebCenter domain.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.

16.5.4.5 Backup and Recovery Recommendations for Oracle WebCenter Activity Graph

This section describes the Oracle WebCenter Activity Graph data that must be backed up and restored.

Configuration Files

Configuration information is stored in the ACTIVITIES schema.

Database Repository Dependencies

ACTIVITIES schema

Backup Recommendations

Back up the Oracle home, the domain home, and the database containing the ACTIVITIES schema.

Recovery Recommendations

Recover the Oracle home and the domain home.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle WebCenter Activity Graph, see Section 18.2.7.8.

16.5.4.6 Backup and Recovery Recommendations for Oracle WebCenter Analytics

This section describes the Oracle WebCenter Analytics data that must be backed up and restored.

Configuration Files

Configuration information is stored in the Analytics schema, ACTIVITIES.

Database Repository Dependencies

ACTIVITIES and MDS schema

Backup Recommendations

Back up the Oracle home, the domain home, and the database containing the ACTIVITIES and MDS schemas.

Recovery Recommendations

Recover the Oracle home and the domain home.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle WebCenter Analytics, see Section 18.2.7.9.

16.5.4.7 Backup and Recovery Recommendations for Oracle Content Server

For information about backing up and recovering Oracle Content Server, see Getting Started with Content Server which is available at:

http://download.oracle.com/docs/cd/E10316_01/owc.htm

Database Repository Dependencies

OCSERVER schema

16.5.5 Backup and Recovery Recommendations for Oracle JRF Installations

The following topics describe backup and recovery recommendations for components that are installed with more than one type of installation:

16.5.5.1 Backup and Recovery Recommendations for Oracle Web Services Manager

This section describes the Oracle Web Services Manager data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/fmwconfig/policy-accessor-config.xml

Database Repository Dependencies

If a database-based MDS Repository is used, Oracle Web Services Manager uses a partition in the MDS schema.

Backup Recommendations

Back up the Oracle Web Services Manager domain.

If Oracle Web Services Manager uses a file-based MDS Repository, back it up using a file copy mechanism. If it uses a database-based MDS Repository, back up the database using RMAN.

Recovery Recommendations

Restore the Oracle Web Services Manager Managed Server.

If Oracle Web Services Manager uses a file-based MDS Repository, restore it from the backup. If it uses a database-based MDS Repository, recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4.

16.5.5.2 Backup and Recovery Recommendations for Oracle Platform Security Services

This section describes the Oracle Platform Security Services data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/fmwconfig/jps-config.xml

Database Repository Dependencies

None

Backup Recommendations

Back up the Administration Server domain.

Recovery Recommendations

Restore the jps-config.xml file.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.5.1.

16.5.6 Backup and Recovery Recommendations for Web Tier Installations

The following sections describe backup and recovery recommendations for Web Tier installations:

16.5.6.1 Backup and Recovery Recommendations for Oracle HTTP Server

This section describes the Oracle HTTP Server data that must be backed up and restored.

Configuration Files

ORACLE_INSTANCE/config/OHS/component_name
ORACLE_INSTANCE/diagnostics/logs/OHS/component_name

Database Repository Dependencies

None

Backup Recommendations

Back up the Oracle instance that contains Oracle HTTP Server.

Recovery Recommendations

Restore the Oracle instance that contains Oracle HTTP Server.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.7.1.

16.5.6.2 Backup and Recovery Recommendations for Oracle Web Cache

This section describes the Oracle Web Cache data that must be backed up and restored.

Configuration Files

ORACLE_INSTANCE/config/WebCache/component_name
ORACLE_INSTANCE/diagnostics/logs/WebCache/component_name

Database Repository Dependencies

None

Backup Recommendations

Back up the Oracle instance that contains Oracle Web Cache.

Recovery Recommendations

Restore the Oracle instance that contains Oracle Web Cache.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.7.2.

16.5.7 Backup and Recovery Recommendations for Oracle Portal, Oracle Forms Services, Oracle Reports, and Oracle BI Discoverer Installations

The following sections describe backup and recovery recommendations for these components:

16.5.7.1 Backup and Recovery Recommendations for Oracle Portal

This section describes the Oracle Portal data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/config/fmwconfig/servers/WLS_PORTAL/applications/portal/configuration/appConfig.xml
DOMAIN_HOME/config/fmwconfig/servers/WLS_PORTAL/applications/portal/configuration/portal_dads.conf
DOMAIN_HOME/config/fmwconfig/servers/WLS_PORTAL/applications/portal/configuration/portal_plsql.conf
DOMAIN_HOME/config/fmwconfig/servers/WLS_PORTAL/applications/portal/configuration/portal_cache.conf

Database Repository Dependencies

PORTAL, PORTAL_DEMO, PORTAL_APP, PORTAL_PUBLIC, AND PORTAL_APPROVAL schemas

Backup Recommendations

Back up the Administration Server domain, the Managed Server directory, and the Oracle instance containing Oracle Portal, as well as the database containing the schemas.

Recovery Recommendations

Recover the WebLogic Server domain and the Oracle instance containing Oracle Portal.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.8.1.

16.5.7.2 Backup and Recovery Recommendations for Oracle Forms Services

This section describes the Oracle Forms Services data that must be backed up and restored.

Configuration Files

Forms Component:

ORACLE_INSTANCE/config/Forms/forms
ORACLE_INSTANCE/Forms/forms

Forms Common Component:

ORACLE_INSTANCE/config/Forms/frcommon
ORACLE_INSTANCE/Forms/frcommon

Forms EE application and its configuration files:

DOMAIN_HOME/forms_managed_server/tmp/_WL_user/formsapp_version
DOMAIN_HOME/config/fmwconfig/servers/forms_managed_server/applications/formsapp_version/config

Database Repository Dependencies

Any user-configured database for Oracle Forms Services applications.

Backup Recommendations

Back up the Administration Server domain, the Managed Server directory, and the Oracle instance home where Oracle Forms Services is located.

Recovery Recommendations

Restore the Oracle instance home where Oracle Forms Services is located.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.8.2.

16.5.7.3 Backup and Recovery Recommendations for Oracle Reports

This section describes the Oracle Reports data that must be backed up and restored.

Configuration Files

For Reports Server:

ORACLE_INSTANCE/config/ReportsServer/server_name/rwserver.conf
ORACLE_INSTANCE/config/ReportsServer/server_name/jdbcpds.conf
ORACLE_INSTANCE/config/ReportsServer/server_name/xmlpds.conf
ORACLE_INSTANCE/config/ReportsServer/server_name/textpds.conf
ORACLE_INSTANCE/config/ReportsServer/server_name/rwnetwork.conf
ORACLE_INSTANCE/config/ReportsServer/server_name/pcscomponent.conf
ORACLE_INSTANCE/config/ReportsServer/server_name/component-logs.xml
ORACLE_INSTANCE/config/ReportsServer/server_name/logging.xml

For Oracle Reports Servlet:

In the following paths, server_name is usually WLS_REPORTS or WLS_REPORTSn and version is the version of the software, for example, 11.1.1.4.0:

DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/cgicmd.dat
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/rwservlet.properties
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/rwserver.conf
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/jdbcpds.conf
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/xmlpds.conf
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/textpds.conf
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/rwnetwork.conf
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/logging.xml
DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration/logmetadata.xml

For Oracle Reports Bridge:

ORACLE_INSTANCE/config/ReportsBridge/bridge_name/rwbridge.conf
ORACLE_INSTANCE/config/ReportsBridge/bridge_name/rwnetwork.conf
ORACLE_INSTANCE/config/ReportsBridge/bridge_name/component-logs.xml
ORACLE_INSTANCE/config/ReportsBridge/bridge_name/logging.xml
ORACLE_INSTANCE/config/ReportsBridge/bridge_name/pcscomponent.xml

For Oracle Reports Tool:

ORACLE_INSTANCE/config/ReportsTools/rwbuilder.conf
ORACLE_INSTANCE/config/ReportsTools/rwnetwork.conf
ORACLE_INSTANCE/config/ReportsTools/jdbcpds.conf
ORACLE_INSTANCE/config/ReportsTools/xmlpds.conf
ORACLE_INSTANCE/config/ReportsTools/textpds.conf
ORACLE_INSTANCE/config/ReportsTools/pcscomponent.xml
ORACLE_INSTANCE/config/ReportsTools/rwservlet.properties
ORACLE_INSTANCE/config/ReportsTools/cgicmd.dat
ORACLE_INSTANCE/config/ReportsTools/component-logs.xml
ORACLE_INSTANCE/config/ReportsTools/logging.xml

Other directories and files:

ORACLE_INSTANCE/reports/server/*.dat
ORACLE_INSTANCE/reports/cache/
ORACLE_INSTANCE/reports/fonts/
ORACLE_INSTANCE/reports/plugins/resource
ORACLE_INSTANCE/diagnostics/logs/reports/ReportsServer
ORACLE_INSTANCE/diagnostics/logs/reports/ReportsBridge
ORACLE_INSTANCE/diagnostics/logs/reports/ReportsTools
(UNIX) ORACLE_INSTANCE/config/reports/bin/rw*.sh
(Windows) ORACLE_INSTANCE\config\reports\bin\rw*.bat
(UNIX) ORACLE_INSTANCE/config/reports/bin/reports.sh
(Windows) ORACLE_INSTANCE\config\reports\bin\reports.bat
(UNIX) ORACLE_INSTANCE/config/reports/bin/namingservice.sh
(Windows) ORACLE_INSTANCE\config\reports\bin\namingservice.bat

Database Repository Dependencies

You can configure Oracle Reports to store job-related information, such as scheduled job data, past job data, or job status data in a database.

Backup Recommendations

Back up the Administration Server domain, the Managed Server directory, and the Oracle instance home where Oracle Reports is located.

If a database is configured for Oracle Reports, back up the database.

Recovery Recommendations

Restore the Oracle instance home where Oracle Reports is located.

If a database is configured for Oracle Reports, recover the database to most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.8.3.

16.5.7.4 Backup and Recovery Recommendations for Oracle Business Intelligence Discoverer

This section describes the Oracle Business Intelligence Discoverer data that must be backed up and restored.

Configuration Files

ORACLE_INSTANCE/config/PreferenceServer/disco-comp-name/pref.txt
ORACLE_INSTANCE/config/PreferenceServer/disco-comp-name/.reg_key.dc
DOMAIN_HOME/config/fmwconfig/servers/WLS_DISCO/applications/discoverer_version/configuration/configuration.xml
DOMAIN_HOME/config/config.xml
DOMAIN_HOME/config/fmwconfig/servers/server_name/logging.xml

Log Files

ORACLE_INSTANCE/diagnostics/logs/PreferenceServer/Discoverer_instance_name/console*
ORACLE_INSTANCE/diagnostics/logs/PreferenceServer/Discoverer_instance_name/log*
DOMAIN_HOME/servers/server_name/logs/discoverer/diagnostic-*.xml
DOMAIN_HOME/servers/server_name/logs/discoverer/diagnostics*.xml
DOMAIN_HOME/servers/server_name/logs/WLS_DISCO-diagnostic-*.xml

Database Repository Dependencies

DISCOVERER and DISCOVERER_PS schemas

Backup Recommendations

Back up the Administration Server domain, the Managed Server directory, and the Oracle BI Discoverer Oracle instance home.

Back up the database containing the DISCOVERER and DISCOVERER_PS schemas.

Recovery Recommendations

Restore the Oracle instance that contains Oracle BI Discoverer.

Recover the database to the most recent point in time, if needed.

For the steps to recover components, see Section 18.2.7. For the steps specific to recovering from loss of host, see Section 18.3.4 and Section 18.3.4.8.4.

16.5.8 Backup and Recovery Recommendations for Oracle Business Intelligence

The following sections describe backup and recovery recommendations for Oracle Business Intelligence:

16.5.8.1 Backup and Recovery Recommendations for Oracle BI Enterprise Edition

This section describes the Oracle BI Enterprise Edition data that must be backed up and restored.

Configuration Files

ORACLE_INSTANCE/bifoundation/OracleBIApplication
ORACLE_INSTANCE/bifoundation/OracleBIClusterControllerComponent
ORACLE_INSTANCE/bifoundation/OracleBIJavaHostComponent
ORACLE_INSTANCE/bifoundation/OracleBIPresentationServicesComponent
ORACLE_INSTANCE/bifoundation/OracleBISchedulerComponent
ORACLE_INSTANCE/bifoundation/OracleBIServerComponent
ORACLE_INSTANCE/bifoundation/OracleBIODBCComponent
ORACLE_INSTANCE/config/OracleBIApplication 
ORACLE_INSTANCE/config/OracleBIClusterControllerComponent
ORACLE_INSTANCE/config/OracleBIJavaHostComponent
ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent
ORACLE_INSTANCE/config/OracleBISchedulerComponent
ORACLE_INSTANCE/config/OracleBIServerComponent
ORACLE_INSTANCE/config/OracleBIODBCComponent
ORACLE_INSTANCE/diagnostics/logs/OracleBIApplication 
ORACLE_INSTANCE/diagnostics/logs/OracleBIClusterControllerComponent
ORACLE_INSTANCE/diagnostics/logs/OracleBIJavaHostComponent
ORACLE_INSTANCE/diagnostics/logs/OracleBIPresentationServicesComponent
ORACLE_INSTANCE/diagnostics/logs/OracleBISchedulerComponent
ORACLE_INSTANCE/diagnostics/logs/OracleBIServerComponent
ORACLE_INSTANCE/diagnostics/logs/OracleBIODBCComponent

In addition, the following files in a file-based repository:

ORACLE_INSTANCE/bifoundation/OracleBIServerComponent/comp_instance name/repository/*.rpd 
ORACLE_INSTANCE/bifoundation/OracleBIPresentationServicesComponent/comp_instance name/catalog/catalog-name

The NQSConfig.INI configuration file points to the Repository Publishing Directory (RPD) name. The NQSConfig.INI file must exist in the following location:

ORACLE_INSTANCE/bifoundation/OracleBIServerComponent/comp_instance name/repository/

Database Repository Dependencies

UserStats, BISERVER, SCHEDULER, and BIPUBLISHER schemas

Backup Recommendations

Back up the Middleware home, the domain home, and the Oracle instance containing the Oracle BI EE components. On Windows, export Oracle BI EE Registry entries, as described in Section 17.3.3.

Back up the database containing the Oracle BI EE schemas.

Note:

Before you perform a backup, you must lock the Oracle BI Presentation Catalogs so that the catalog and RPD remain synchronized. Run the following script: 
ORACLE_INSTANCE/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalogmanager/runcat.sh

Use the following command:

./runcat.sh -cmd maintenanceMode -on -online BIP_URL 
     -login username -pwd password

Recovery Recommendations

Depending on the extent of the failure, recover the Middleware home, the domain, and the Oracle instance containing the Oracle BI EE components. On Windows, import Oracle BI EE Registry entries.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle BI EE, see Section 18.2.7.10. For the steps specific to recovering from loss of host, see Section 18.3.4.9.

16.5.8.2 Backup and Recovery Recommendations for Oracle Business Intelligence Publisher

This section describes the Oracle Business Intelligence Publisher data that must be backed up and restored.

Configuration Files

Configuration files are located in the Middleware home, the domain home, and the Oracle Business Intelligence Publisher repository.

Database Repository Dependencies

BIPUBLISHER schema

Backup Recommendations

Back up the Middleware home, the domain, and the BI Publisher repository.

The BI Publisher repository can be file-based or database-based.

Recovery Recommendations

Recover the Managed Server containing the Oracle BI Publisher component.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle BI Publisher, see Section 18.2.7.11. For the steps specific to recovering from loss of host, see Section 18.3.4.10.

16.5.8.3 Backup and Recovery Recommendations for Oracle Real-Time Decisions

This section describes the Oracle Real-Time Decisions data that must be backed up and restored.

Configuration Files

Configuration files are located in the Middleware home and the domain home.

Database Repository Dependencies

Database containing analytic models and the RTD schema

Backup Recommendations

Back up the Middleware home, the domain home, and the database containing analytic models

Recovery Recommendations

Recover the Managed Server containing the Oracle Real-Time Decisions component.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle Real-Time Decisions, see Section 18.2.7.12. For the steps specific to recovering from loss of host, see Section 18.3.4.11.

16.5.9 Backup and Recovery Recommendations for Oracle Data Integrator

This section describes the Oracle Data Integrator data that must be backed up and restored.

Configuration Files

ODI_Oracle_Home/oracledi/agent/web.xml

Database Repository Dependencies

ODI_REPO schema

Backup Recommendations

Back up the domain, the Oracle home, and the ODI_Oracle_Home/oracledi/agent folder for each machine where a standalone agent is installed.

Back up the database containing ODI schema.

Recovery Recommendations

Depending on the extent of the failure, restore the domain or the Oracle home, or both.

Recover the database to the most recent point in time, if needed.

For the steps to recover Oracle Data Integrator, see Section 18.2.7.13. For the steps specific to recovering from loss of host, see Section 18.3.4.5.

16.5.10 Backup and Recovery Recommendations for Oracle Enterprise Content Management Suite

The following sections describe backup and recovery recommendations for Oracle Enterprise Content Management Suite:

16.5.10.1 Backup and Recovery Recommendations for Oracle Information Rights Management

This section describes the Oracle Information Rights Management data that must be backed up and restored.

Configuration Files

Configuration files are located within the domain home.

Database Repository Dependencies

ORAIRM schema (IRM for DB2 and SQL Server databases. You must ensure that the name is IRM.)

Backup Recommendations

Back up the domain, the Oracle home, and the database containing the ORAIRM schema. Also, back up the LDAP directory and the keystore. The keystore is usually named irm.jks or irm.jceks.

Note that the database and the keystore must be kept synchronized. Back up both from the same point in time.

Recovery Recommendations

Restore the domain, the Oracle home, and the shared file system, depending on the severity of the failure.

Recover the database containing the ORAIRM schema to the most recent point in time, if needed.

Note that the database and the keystore must be kept synchronized. If you restore one, restore the other to the same point in time.

For the steps to recover Oracle Information Rights Management, see Section 18.2.7.14. You use the same procedure to recover from loss of host.

16.5.10.2 Backup and Recovery Recommendations for Oracle Imaging and Process Management

This section describes the Oracle Imaging and Process Management data that must be backed up and restored.

Configuration Files

Configuration files are located within the domain home.

Database Repository Dependencies

IPM and OCS schemas

Backup Recommendations

Back up the domain, the Oracle home, and the database containing the schemas.

Recovery Recommendations

Restore the domain and the Oracle home, depending on the severity of the failure.

Recover the database containing the schemas to the most recent point in time, if needed.

For the steps to recover Oracle Imaging and Process Management, see Section 18.2.7.15. You use the same procedure to recover from loss of host.

16.5.10.3 Backup and Recovery Recommendations for Oracle Universal Content Management

This section describes the Oracle Universal Content Management data that must be backed up and restored.

Configuration Files

DOMAIN_HOME/ucm/CONTEXT-ROOT/bin/intradoc.cfg
DOMAIN_HOME/ucm/CONTEXT-ROOT/config/config.cfg

Database Repository Dependencies

OCS schema

Backup Recommendations

Back up the domain, the Oracle home, and database containing the OCS schema. If the Vault and WebLayout directories are not located in the domain directory, back up their directories, which are specified in:

DOMAIN_HOME/ucm/CONTEXT-ROOT/config/config.cfg

Also, back up the following directory, which is located in a shared file system:

DOMAIN_HOME/ucm/CONTEXT-ROOT/config

Recovery Recommendations

Restore the domain and the shared file system containing the Vault and WebLayout directories, depending on the severity of the failure.

Recover the database containing the OCS schema to the most recent point in time, if needed.

For the steps to recover Oracle Universal Content Management, see Section 18.2.7.16. For the steps specific to recovering from loss of host, see Section 18.3.4.13.1.

16.5.10.4 Backup and Recovery Recommendations for Oracle Universal Records Management

Because Oracle Universal Records Management depends on Oracle Universal Content Management and has no additional backup and recovery artifacts, see the backup and recovery recommendations for Oracle Universal Content Management in Section 16.5.10.3.

16.6 Assumptions and Restrictions

The following assumptions and restrictions apply to the backup and recovery procedures in this book. Also see the restrictions listed in Section 17.2.

  • File systems and files can only be restored as of the last good backup. There is no support for roll-forward recovery to the current point in time.

  • All of the files required for recovery are maintained within the Middleware home, Oracle instance home, and Oracle Inventory (for loss of host use cases) directories. Generally, if no administration changes, such as configuration changes, deployments, redeployments, or patching, have been done during the backup, it is always safe to restore the file system pertaining to a particular component to a previous point in time using the last good backup. Thus, new backups must always performed after any administration changes.

  • Only the user who installs the product or a user who has access privileges to the directories where Oracle Fusion Middleware has been installed should be able to execute backup and recovery operations.

  • If a single Managed Server and Administration Server run on different hosts and the Managed Server is not in a cluster, you must use the pack and unpack commands on the Managed Server to retrieve the correct configuration.

  • If multiple Managed Servers run on different hosts (not in a cluster), the domain should be configured to use an external LDAP for policy store instead of using file-based policy store.

  • If the Administration Server is on a different host than the Managed Servers, the domain should be configured to use an external LDAP for the policy store instead of using a file-base policy store.

See Also:

If you are using Cold Failover Cluster or Disaster Recovery, refer to the Oracle Fusion Middleware High Availability Guide for additional information.