0% found this document useful (0 votes)
4 views

Configuring Database Recoverability

Uploaded by

AKIRA Harashi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views

Configuring Database Recoverability

Uploaded by

AKIRA Harashi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Configuring Database Recoverability

Your backup and recovery plan should include, at a minimum, these


tasks:
 Configuration Define backup destinations, encryption, and
retention policies.
 Scheduling Automate backups to minimize human error and
manual intervention.
 Testing Perform routine backup and recovery options to ensure that
your backup
plan works before you experience a real disaster.
 Monitoring Ensure that you minimize the resources used to
perform a sufficient
backup and minimize the impact to other database users.
 Restoration Restore your database files in the file system (datafiles,
archive logs, and
so on), from a previous backup.
 Recovery Perform a recovery of the database to the point of failure
of the database by
applying archived redo log entries to restored database files and rolling
forward
changes to your restored backup. Know how to recover your database.
Backup and recovery tools such as RMAN can be used in nonemergency
situations as
well: For example, you can take a snapshot of an entire database at one
location and
restore it to another location for developers or for testing

Logical Backups
A logical backup of a database involves reading a set of database rows
and writing
them to a file. These records are read independently of their physical
location. In
Oracle, the Data Pump Export utility performs this type of database
backup. To
recover using the file generated from a Data Pump Export, you use Data
Pump Import.
Oracle’s Data Pump Export utility queries the database, including the
data dictionary,
and writes the output to an XML file called an export dump file. You can
export the
full database, specific users or tablespaces, or specific tables. During
exports, you can
choose whether or not to export the data dictionary information
associated with
tables, such as grants, indexes, and constraints. The file written by Data
Pump Export
will contain the commands necessary to completely re-create all the
chosen objects
and data.

Physical Backups
Physical backups involve copying the files that constitute the database.
These
backups are also referred to as file system backups because they involve
using
operating system file backup commands. Oracle supports two different
types of
physical file backups: offline backups and online backups (also known
as cold and hot
backups, respectively).

Offline Backups
Consistent offline backups occur when the database has been shut down
normally
(that is, not due to instance failure) using the NORMAL, IMMEDIATE,
or
TRANSACTIONAL option of the SHUTDOWN command. While the
database is offline,
the following files should be backed up:

You might also like