Managing Fusion Applications - Oracle Fusion Applications Administration Essentials - page 92

Backing up the Oracle Fusion

Applications

All ERP applications require a comprehensive backup and recovery mechanism. The
ability to back up an application provides insurance against application failure. This
can happen for several reasons:

• Hardware failure

• Database corruption

• Application failure due to patching

A comprehensive backup allows the application to be recovered to a point in time at
which the entire application was in an integral state. Since Oracle Fusion Applications
have multiple components, the backup of Oracle Fusion Applications spans multiple
layers. There are primarily two areas of backup with multiple subcomponents. The
high-level layers are shown in the following figure:

Filesystem backup

The filesystem has a copious amount of files. Some of these files are static and hence
a single backup for these files would suffice. Other files change based on the applica-
tion setup and usage. These files need to be backed up on a regular basis. In general,
the following categories of files are backed up:

• Binary files : These files are static in nature. They include the application serv-

er binaries as well as the application logic components. These files do not
change often, and are usually impacted during a major version upgrade.

• Configuration files : These files contain configuration information regarding

the application. These files change often and should be backed up on a regu-
lar basis.

The files themselves include technology stack binaries, application logic files, and
application configuration files. These files are stored across servers and nodes and