HP A.06.11 - Manual (Page 77)

• On other UNIX systems: /usr/omni/bin/omnib -oracle8_list \
backup_specification_name -test_bar
• On OpenVMS: $omnib -oracle8_l qist backup_specification_name
-test_bar
The ob2rman.pl command is started, which then starts the BACKUP VALIDATE
DATABASE RMAN
command.
Starting backup sessions
There are two strategies for backing up a database. These are an offline or consistent
database backup, and an online or inconsistent database backup. The latter is also
known as a hot backup. Special attention is required to reach a consistent state with
an online backup.
A decision about your database backup strategy depends on a number of factors.
If the database must be open and available all the time, then online backup is your
only choice. If you can afford to have the database offline at a certain time, then
you are more likely to make periodic offline backups of the entire database,
supplementing them with online backups of the dynamically changing tablespaces.
Oracle offline
An offline backup of a database is a backup of the datafiles and control files which
are consistent at a certain point in time. The only way to achieve this consistency is
to cleanly shut down the database and then back up the files while the database is
either closed or mounted.
If the database is closed, the offline backup of an Oracle target database can be
performed using a Data Protector filesystem backup specification. In this case, the
Data Protector Disk Agent is used.
If the database is mounted, a Data Protector Oracle backup specification, based on
which Data Protector automatically generates and executes the RMAN script, can
be used. In this case, the Data Protector Oracle integration software component is
used.
Typically, you would perform an offline backup of the entire database, which must
include all datafiles and control files, while the parameter files may be included
optionally.
The whole offline database backup is performed as follows:
Integration guide for Oracle and SAP 77