Recovering a SOA WebLogic Environment

This document describes suggested recovery strategies and procedures for recovering Oracle Fusion Middleware Domain and Managed Servers from types of failures and outages, such as VM failures (loss of host) or loss of data etc.

1. Current Scenario Currently the SOA Domain in production environment is running with reduced capacity. Two of the four WebLogic managed servers are not up & running. The WebLogic Admin and EM console do not work as expected.

2. Recovery Approaches

In absence of a reliable restore point, following recovery approaches are proposed.

• Recovery of the entire Oracle SOA WebLogic Server Domain Note: Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost. OR

• Recovering individual SOA Managed Servers A variety of events can lead to the failure of a server instance. Often one failure condition leads to another. The current managed server failure appears to be an after effect of a virtual machine crash.

• Recovering a Managed Server When It Cannot Be Started In this scenario, the Managed Server does not operate properly or

cannot be started because the configuration has been deleted or corrupted or the configuration was mistakenly changed and we cannot ascertain what was changed.

• Recovering a Managed Server When It Does Not Function Correctly

In this scenario, the Managed Server is running, but the file system for the Managed Server has been lost or corrupted.

• Recovering an Oracle SOA Suite Managed Server That Has a Separate Directory

• When Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server, you must restore the Managed Server directory.

• Recovering the Administration Server Configuration If the Administration Server configuration has been lost because of file deletion or file system corruption, after a restart the Administration Server console fails to function. The Administration Server directory is regenerated automatically, except for security information. As a result, whenever the admin console is accessed, it fails to render. To prevent this, we can recover/restore the configuration.

• Recovering a Component That Is Not Functioning Properly Currently the EM Console shows SOA processes as broken. This severely limits the support and maintenance administrators from monitoring and deploying components. It is recommended that this issue be fixed as well.

2. Disaster Recovery (Highly Recommended) Disaster Recovery (DR) is the ability to safeguard mission critical data and applications against natural or unplanned outages at a production site by having a properly implemented and successful recovery strategy to a geographically separate secondary site.

Please refer to FMW DR Strategy Document for further details.FMW DR

Strategys.docx

3. Estimated Hours per Approach.

Please refer to the excel file.Reovery High Level

Plan.xlsx