Backup and Recovery Recommendations for Oracle Essbase Backup and Recovery Recommendations for Oracle Hyperion Calculation Manager

17-2 Oracle Fusion Middleware Administrators Guide The flowchart in Figure 17–1 provides an overview of how to decide which type of backup is appropriate for a given circumstance. Figure 17–1 Decision Flow Chart for Type of Backup

17.2 Limitations and Restrictions for Backing Up Data

Note the following points: ■ LDAP backups: If you use the built-in LDAP, do not update the configuration of a security provider while a backup of LDAP data is in progress. If a change is made for example, if an administrator adds a user, while you are backing up the ldap directory tree, the backups in the ldapfiles subdirectory could become inconsistent. Refer to WebLogic Server Managing Server Startup and Shutdown for detailed LDAP backup procedures. ■ Java Transaction API JTA: Oracle does not recommend that you back up and restore JTA transaction logs. ■ Audit Framework: If you have configured Oracle Fusion Middleware Audit Framework to write data to a database, you should not back up the local files in the bus stop. Auditable events from each component are stored in a repository Major Changes Upgrade, Patch? Yes No Administrative Changes? No Yes Oracle Fusion Middleware Installation and Configuration Completed Oracle Fusion Middleware Running Full OffLine Backup of Oracle Fusion Middleware Online Backup of Runtime Artifacts Regular Scheduled Backup? No Yes Backing Up Your Environment 17-3 known as a bus stop; each Oracle WebLogic Server has its own bus stop. Data can be persisted in this file, or uploaded to a central repository at which point the records are available for viewing and reporting. If you back up the local files, duplicate records are uploaded to the database. That is, they are uploaded to the database when the bus stop is created and then are uploaded again when you restore the files. The default locations for bus stop local files are: – For Java components: DOMAIN_HOMEserversserver_namelogsauditlogscomponent_type – For system components, such as Oracle HTTP Server or Oracle Internet Directory: ORACLE_INSTANCEauditlogscomponent_typecomponent_name For more information about Oracle Fusion Middleware Audit Framework and the bus stop, see Configuring and Managing Auditing in the Oracle Fusion Middleware Application Security Guide.

17.3 Performing a Backup

You can perform a full offline backup or an online or offline backup of run-time artifacts, as described in the following topics: ■ Performing a Full Offline Backup ■ Performing an Online Backup of Run-Time Artifacts ■ Backing Up Windows Registry Entries

17.3.1 Performing a Full Offline Backup

To perform a full offline backup, you copy the directories that contain Oracle Fusion Middleware files. Archive and compress the source Middleware home, using your preferred tool for archiving, as described in Section 16.3 . Take the following steps: 1. Shut down all processes in the Middleware home. For example, shut down the Managed Servers, the Administration Server, and any Oracle instances running in the Middleware home. 2. Back up the Middleware home MW_HOME on all hosts. For example: tar -cf mw_home_backup_092010.tar MW_HOME 3. If the domain is not located within the Middleware home, back up the Administration Server domain separately. This backs up Java components such as Oracle SOA Suite and Oracle WebCenter. For example: tar -cf domain_home_backup_092010.tar DOMAIN_HOME In most cases, you do not need to back up the Managed Server directories separately, because the Administration Server domain contains information about the Managed Servers in its domain. If you have customized your environment for