Database Reference
In-Depth Information
Recovery strategies
The purpose of recovering your environment is to restore it due to a software fail-
ure (such as a faulty patch or misconfiguration), hardware failure (such as an in-
ternal hard disk failure), or due to a need to perform a point-in-time recovery (to
undo configuration or architectural changes that have proven defective or prob-
lematic).
Multiple factors should be considered before recovering an environment. It de-
pends on which component failed and what point in time you want to recover to.
Additional factors such as ensuring consistency among components is equally
important. Full restores of the entire mid-tier and database to the same point in
time are perhaps the simplest and least risky of all approaches, but are time con-
suming in nature. Furthermore, when a simple faulty configuration change needs
to be rolled back, do you really need to restore the entire environment or just re-
store that particular component?
The installation of an Oracle SOA Suite
11g
environment relies on interdependent
components that contain configuration information, applications (both Java and
composite), and data that must be kept in synchronization. As a consequence,
both backing up and restoring an Oracle SOA Suite
11g
installation requires more
thought than merely unzipping the backup files.
By now, you have a good understanding of how Oracle SOA Suite
11g
functions,
what files and components it requires and relies on, and what area to perhaps
recover in the event of a failure. You also understand the implications of restoring
different components separately.
All components, with the exception of the database, are backed up by using
standard file system commands or tools. To recover your Oracle SOA Suite
11g
environment, simply restore the file or files of the component that needs to be re-
stored. For example, any combination of the following may need to be restored
depending on the type of failure:
