Backup and Recovery Recommendations for Oracle Real-Time Decisions

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 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