Database Reference
In-Depth Information
The types of data that are typically backed up are:
•
Static files (for example, domain configuration files, software binaries, and
patches)
•
Runtime artifacts (for example, application deployments, instance data and
metadata, and transaction logs)
So when should you backup your environments? As long as the static files don't
change, technically a single valid backup is all that is required. Configuration
changes or the application of patches tend to change the contents of these static
files, hence prompting the need to create another backup. Runtime artifacts or
dynamic data, such as continually updated instance data in the database, may
need to be backed up regularly. There are cases where both online and offline
backups may be valid for these types of data, and we will discuss them in more
detail later on in this chapter.
In the unfortunate event that a recovery is needed, performing a complete re-
store can guarantee full restoration of your environment. However, this is time
consuming and the appropriate downtime may not be sufficient to do so. Thus,
once you understand the different types of files that need to be backed up, you
will know what needs to be restored.
Understanding
what
needs
to
be
backed up
Before describing how to back up your environment, it is important to understand
what needs to be backed up first. We differentiate between static files, files
which do not change frequently such as the software installation binaries, and
dynamic data, otherwise referred to as runtime artifacts, which could include fre-
quently updated data such as instance information and deployment metadata.
