Backup and Recovery Recommendations for Oracle Business Intelligence Publisher

16-36 Oracle Fusion Middleware Administrators Guide Also, back up the following directory, which is located in a shared file system: DOMAIN_HOMEucmCONTEXT-ROOTconfig 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.20 . For the steps specific to recovering from loss of host, see Section 18.3.4.16.1 .

16.5.11.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.11.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 . ■ 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. See Also: If you are using Cold Failover Cluster or Disaster Recovery, refer to the Oracle Fusion Middleware High Availability Guide for additional information. 17 Backing Up Your Environment 17-1 17 Backing Up Your Environment This chapter describes recommended backup strategies for Oracle Fusion Middleware and the procedures for backing up Oracle Fusion Middleware. This chapter includes the following topics: ■ Overview of Backing Up Your Environment ■ Limitations and Restrictions for Backing Up Data ■ Performing a Backup ■ Creating a Record of Your Oracle Fusion Middleware Configuration

17.1 Overview of Backing Up Your Environment

As described in Section 16.3.3 , you should use the following recommended strategy for backing up your Oracle Fusion Middleware environment: ■ If you are performing an online 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 . ■ Perform a full offline backup immediately after you install Oracle Fusion Middleware. See Section 17.3.1 for information on performing a full backup. ■ Perform backups of run-time artifacts after every administrative change and on a regular basis. Oracle recommends that you back up run-time artifacts nightly. See Section 17.3.2 for information on performing a backup of run-time artifacts. ■ Perform a new full backup after a major change, such as any upgrade or patch, or if any of the following files are modified: MW_HOMEwlserver_ncommonbinnodemanager.properties MW_HOMEwlserver_ncommonbinwlsifconfig.sh MW_HOMEwlserver_ncommonbinsetPatchEnv.sh MW_HOMEwlserver_ncommonbincommEnvg.sh See Section 17.3.1 for information on performing a full backup. ■ Create a record of your Oracle Fusion Middleware environment. See Section 17.4 . ■ When you create the backup, name the archive file with a unique name. Consider appending the date and time to the name. For example, if you create a backup of the Middleware home on March 20, 2010, name the backup: mw_home_backup_092010.tar