HP Data Protector A.06.11 Integration Manual page 135

For oracle and sap
Hide thumbs Also See for Data Protector A.06.11:
Table of Contents

Advertisement

run{
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORCL,OB2BARLIST=New1)';
allocate channel 'dev_1' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORCL,OB2BARLIST=New1)';
allocate channel 'dev_1' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORCL,OB2BARLIST=New1)';
backup incremental level <incr_level>
format 'New1<ORCL_%s:%t:%p>.dbf'
NOT BACKED UP SINCE TIME "TO_DATE('5/15/2009 15:30:00',
'MM/DD/YY HH24:MI:SS')"
database;
sql 'alter system archive log current';
backup
format 'New1<ORCL_%s:%t:%p>.dbf'
NOT BACKED UP SINCE TIME "TO_DATE('5/15/2009 15:30:00',
'MM/DD/YY HH24:MI:SS')"
archive log all;
backup
format 'New1<ORCL_%s:%t:%p>.dbf'
NOT BACKED UP SINCE TIME "TO_DATE('5/15/2009 15:30:00',
'MM/DD/YY HH24:MI:SS')"
recovery area;
backup
format 'New1<ORCL_%s:%t:%p>.dbf'
NOT BACKED UP SINCE TIME "TO_DATE('5/15/2009 15:30:00',
'MM/DD/YY HH24:MI:SS')"
current controlfile;
Consequently, RMAN skips the backup sets that were backed up successfully in the
original session.
Suppose that you run the following sessions:
1.
2009/05/13–1 (original backup session)
2.
2009/05/13–2 (resuming 2009/05/13–1)
3.
2009/05/13–3 (resuming 2009/05/13–2)
The Time in the RMAN clause NOT BACKED UP SINCE Time is always the original
backup session start time. Consequently, the RMAN script created in the third session
(2009/05/13–3) does not use the start time of the session 2009/05/13–2 but the
start time of the original backup session (2009/05/13–1). This ensures that each
backup set is backed up only once after the original backup session was started.
Integration guide for Oracle and SAP
135

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Data Protector A.06.11 and is the answer not in the manual?

Questions and answers

Table of Contents