Skip Headers
Oracle® Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1.8.0)

Part Number E10105-15
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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:

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:

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

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

17.2 Limitations and Restrictions for Backing Up Data

Note the following points:

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:

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:

    (UNIX) tar -cf mw_home_backup_042012.tar MW_HOME/*
    (Windows) jar cf mw_home_backup_042012.jar 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 Portal.

    For example:

    (UNIX) tar -cf domain_home_backup_042012.tar DOMAIN_HOME/*
    (Windows) jar cf domain_home_backup_042012.jar 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 the Managed Server, back up the Managed Server directories. See Section 16.5 for information about what you need to back up.

  4. If the Oracle instance home is not located within the Middleware home, back up the Oracle instance home. The Oracle instance home contains configuration information about system components, such as Oracle HTTP Server or Oracle Internet Directory. (See Section 3.5.2 for a list of system components.)

    For example:

    (UNIX) tar -cf sc_home_backup_042012.tar ORACLE_INSTANCE/*
    (Windows) jar cf sc_home_backup_042012.jar ORACLE_INSTANCE\*
    
  5. If a Managed Server is not located within the domain, back up the Managed Server directory. For example:

    (UNIX) tar -cf mg1_home_backup_042012.tar server_name/*
    (Windows) jar cf mgl_home_backup_042012.jar server_name\*
    
  6. Back up the OraInventory directory. For example:

    tar -cf Inven_home_backup_042012.tar /scratch/oracle/OraInventory
    
  7. On Linux and UNIX, back up the oraInst.loc file, which is located in the following directory:

    (Linux and IBM AIX) /etc
    (Other UNIX systems) /var/opt/oracle
    
  8. On Linux and UNIX, backup the oratab file, which is located in the following directory:

    /etc
    
  9. Back up the database repositories using the Oracle Recovery Manager (RMAN). For detailed steps, see the Oracle Database Backup and Recovery User's Guide.

  10. On Windows, you should also export the Windows Registry entries, as described in Section 17.3.3.

  11. Unlock the WebLogic Server configuration by clicking Release Configuration on the WebLogic Server Administration Console,

  12. Create a record of your Oracle Fusion Middleware environment. See Section 17.4.

17.3.2 Performing an Online Backup of Run-Time Artifacts

You should perform a backup of run-time artifacts (which are listed in Section 16.3.2) on a regular basis and at the times described in Section 16.3.3.

To back up run-time artifacts:

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

  2. Back up the Administration Server domain directories. This backs up Java components such as Oracle SOA Suite and Oracle WebCenter Portal. For example:

    (UNIX) tar -cf domain_home_backup_042012.tar DOMAIN_HOME/*
    (Windows) jar cf domain_home_backup_042012.jar DOMAIN_HOME\* 
    

    For Oracle Portal, Oracle Reports, Oracle Forms Services, and Oracle Business Intelligence Discoverer, you must back up the Managed Server directories, in addition to the Administration Server domain directories.

  3. Back up the Oracle instance home. This backs up the system components, such as Oracle HTTP Server. For example:

    (UNIX) tar -cf sc_home_backup_042012.tar ORACLE_INSTANCE/*
    (Windows) jar cf sc_home_backup_042012.jar ORACLE_INSTANCE\*
    
  4. Back up the database repositories using the Oracle Recovery Manager (RMAN). For detailed steps, see the Oracle Database Backup and Recovery User's Guide.

  5. Unlock the Oracle WebLogic Server configuration by clicking Release Configuration on the WebLogic Server Administration Console,

  6. Create a record of your Oracle Fusion Middleware environment. See Section 17.4.

17.3.3 Backing Up Windows Registry Entries

On Windows, you must back up Windows Registry keys related to Oracle Fusion Middleware. Which keys you back up depends on what components you have installed.

To export a key, use the following command:

regedit /E  FileName Key

Export the following entries:

  • For any component, export the following registry key:

    HKEY_LOCAL_MACHINE\Software\Oracle
    
  • For system components, such as Oracle Web Cache, and for Oracle BI Enterprise Edition, export each node that begins Oracle within the following registry keys:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services
    

    For example:

    regedit /E C:\oracleSMP.reg HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Oracleagent10gAgentSNMPPeerEncapsulator 
    

    Use a unique file name for the each key.

  • For Oracle BI EE, export the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
    

    For example:

    regedit /E C:\oracleregistry.reg HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
    

You can also use the Registry Editor to export the key. See the Registry Editor Help for more information.

17.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: