Database Reference
In-Depth Information
Summary
Backing up and restoring an environment should be relatively simple. After all,
software is merely a bunch of files scattered on various filesystems. However, the
two challenges that Oracle SOA Suite 11g administrators face when the need to
restore arises are:
•
To identify what exactly needs to be recovered
•
To establish at what state or point in time you should recover to
In this chapter, we described all the various components that need to be backed
up in an Oracle SOA Suite 11g environment and then followed up with detailing
how to actually perform the backup. Specifically, we covered the following:
•
The various static files in an Oracle SOA Suite 11g installation such as Oracle
system files, the JDK, and the Middleware Home
•
Runtime artifacts that include the database and SOA domain
•
The implications of backing up and restoring JMS file stores and transaction
logs
•
A backup strategy, focusing on what needs to be backed up after installations,
upgrades, patches, and configuration changes, as well as a recommended
regular backup schedule
•
The backup commands for Linux-based installations
•
Key recovery strategy considerations
•
The mechanism to back up and restore a Middleware installation and domain
from one environment to another via cloning
At this point, you should be fully capable of backing up your environment with
a thorough enough understanding of when to restore individual components as
needed.
Advance administration topics such as silent installations, patching, and upgrad-
ing the SOA infrastructure, upgrading from Oracle SOA Suite 10g, and setting up
a highly available clustered installation for Oracle SOA Suite 11g, are available
as a downloadable chapter from Packt's website.