Database Reference
In-Depth Information
time of the database backup. Therefore, if you require it, you may perform a full
database backup before or after SOA code is deployed to protect yourself.
Ongoing backups
As part of your operation, maintenance, and support activities, you will want to
regularly schedule backups of your environment. Some backups may be nightly
while others may be weekly. If little to no changes take place on your midtiers,
nightly delta filesystem backups of the Middleware Home, JDK, and SOA do-
main may suffice (after a full offline backup is performed at least once). In this
case, the only ongoing changes that really do occur are growth of log files.
As for the JMS file store and transaction logs, as mentioned earlier, these are
not backed up. In the event of an irrecoverable failure to them, the best option
will be to recreate them.
As a good practice, your databases should be backed up consistently. Daily and
weekly full backups of databases are not uncommon, and the database admin-
istrator will need to be engaged in this activity.
Files within your SOA domain rarely change unless there is a
code deployment or configuration change. If neither of these
two activities are performed, delta file system backups are of-
ten sufficient.
As for ongoing backups, certain components such as the Oracle system files,
JDK, and Middleware Home do not require frequent backing up unless changes
occur to them. Regardless, implementing some type of ongoing and regular
backup is typically recommended. This table provides a guideline for your
backup schedule, but should be customized based on your needs and opera-
tional standards:
