HP A.06.11 - Manual (Page 134)

4. Click the General, Messages, or Media tab to display general information on
the session, session messages, or information on the media used for this session,
respectively.
Details about Oracle backup and restore sessions are also written in the following
logs on the Oracle Server system:
• Data Protector writes the logs in:
Windows: Data_Protector_home\log\oracle8.log
HP-UX, Solaris, and Linux: /var/opt/omni/log/oracle8.log
Other UNIX: usr/omni/log/oracle8.log
HP OpenVMS: OMNI$ROOT:[LOG]ORACLE8.LOG
• Oracle writes the logs in the Oracle_user_dump_directory\sbtio.log
file.
Resuming sessions
Backup and restore sessions that did not complete successfully can be restarted using
the Data Protector resume session functionality. The functionality enables you to back
up or restore only the files that failed to be backed up or restored in the original
session. Consequently, a session started using the resume session functionality
(resumed session) generally takes less time to complete.
You can resume a session using the Data Protector GUI or CLI.
Considerations
• Sessions that completed successfully cannot be resumed.
• Each session can only be resumed once.
• A resumed session that did not complete successfully can also be resumed.
Resuming backup sessions
When you resume a backup session, Data Protector starts a new backup session
using the same backup specification as used in the original session (note that changes
made to the backup specification affect the resume session). The main difference
compared to a standard backup session is that, during a resumed session, Data
Protector modifies the RMAN script before the actual backup is started, adding the
clause NOT BACKED UP SINCE Time for each backup command, where Time is
the original backup session start time. See the following example:
Integrating Oracle and Data Protector 134