16 Backing Up Your Environment

16.1 Overview of Backing Up Your Environment

As described in Section 15.3.2, 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 16.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 16.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_HOME/wlserver_n/common/bin/nodemanager.properties
  MW_HOME/wlserver_n/common/bin/wlsifconfig.sh
  MW_HOME/wlserver_n/common/bin/setPatchEnv.sh
  MW_HOME/wlserver_n/common/bin/commEnvg.sh
  

  See Section 16.3.1 for information on performing a full backup.

• Create a record of your Oracle Fusion Middleware environment. See Section 16.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_032010.tar
  

The flowchart in Figure 16-1 provides an overview of how to decide which type of backup is appropriate for a given circumstance.

Figure 16-1 Decision Flow Chart for Type of Backup

Description of "Figure 16-1 Decision Flow Chart for Type of Backup"

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

• Persistent stores: A persistent store provides a built-in, high-performance storage solution for WebLogic Server subsystems and services that require persistence. For example, it can store persistent JMS (Java Messaging Service) messages or durable subscriber information, as well as temporarily store messages sent to an unavailable destination using the Store-and-Forward feature. The persistent store supports persistence to a file-based store (File Store) or to a JDBC-enabled database (JDBC Store). The default store maintains its data in the data\store\default directory inside the servername subdirectory of a domain's root directory.

  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.

  For clustered servers, Oracle WebLogic Server enables you to migrate a failing server, including the Transaction Recovery Service, to a new system. When the server migrates to another system, it must be able to locate the transaction log records to complete or recover transactions. Transaction log records are stored in the default persistent store for the server.

  If you plan to migrate clustered servers in the event of a failure, you must set up the default persistent store so that it stores records in a shared storage system that is accessible to any potential system to which a failed migratable server might be migrated. For highest reliability, use a shared storage solution (for example, SAN) or an Oracle database that is highly available and supports a point-in-time recovery. This solution is also recommended for all the JMS modules.

• 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 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_HOME/servers/server_name/logs/auditlogs/component_type
    

  • For system components, such as Oracle HTTP Server or Oracle Internet Directory:

    ORACLE_INSTANCE/auditlogs/component_type/component_name
    

  For more information about Oracle Fusion Middleware Audit Framework and the bus stop, see "Configuring and Managing Auditing" in the Oracle Fusion Middleware Security Guide.

16.3 Performing a Backup

You can perform the following types of backups:

• Full offline backup. See Section 16.3.1.

• Online or offline backup of run-time artifacts. See Section 16.3.2.

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

cd Source_Middleware_Home 
tar cf - * | gzip > mw_home_backup_032010.tar.gz

16.4 Creating a Record of Your Oracle Fusion Middleware Configuration

In the event that you need to restore and recover your Oracle Fusion Middleware environment, it is important to have all the necessary information at your disposal. This is especially true in the event of a hardware loss that requires you to reconstruct all or part of your Oracle Fusion Middleware environment on a new disk or host.

You should maintain an up-to-date record of your Oracle Fusion Middleware environment that includes the information listed in this section. You should keep this information both in hardcopy and electronic form. The electronic form should be stored on a host or e-mail system that is completely separate from your Oracle Fusion Middleware environment.

Your Oracle Fusion Middleware hardware and software configuration record should include:

• The following information for each host in your environment:

  • Host name

  • Virtual host name (if any)

  • Domain name

  • IP address

  • Hardware platform

  • Operating system release level and patch information

• The following information for each Oracle Fusion Middleware installation in your environment:

  • Installation type (for example, Oracle SOA Suite)

  • Host on which the installation resides

  • User name, userid number, group name, groupid number, environment profile, and type of shell for the operating system user that owns the Oracle home (/etc/passwd and /etc/group entries)

  • Directory structure, mount points, and full path for the Middleware home, Oracle Common home, Oracle homes, Oracle WebLogic Server domain home (if it does not reside in the user_projects directory in the Middleware home), and the Oracle instance home

  • Amount of disk space used by the installation

  • Port numbers used by the installation

• The following information for the database containing the metadata for components:

  • Host name

  • Database version and patch level

  • Base language

  • Character set

  • Global database name

  • SID