EM12c create non-cumulative incremental backups (level 1) against target DB

It is not available? It seems that we can create only cumulative backups RMAN incremental by Cloud 12 c (it's against a 11 GR 2 DB). No cumulative incremental are no longer supported?

When planning a backup via the wizard, the last step shows the RMAN script, the wizard has generated for you. Have you tried clicking "Edit Script RMAN" and delete the word "cascade" of the generated script?

I run backups using scripts stored in the recovery catalog so I do not use the Backup Wizard clicks, but it not lead to a differential incremental backup if you edit the script?

Tags: Enterprise Manager

Similar Questions

While you take the cumulative incremental backup RMAN. Meanwhile users ke
While you take the cumulative incremental backup RMAN.
During this time users keep be updated, insert the corresponding schema.
But my Client doesn't backup up-to-date. Is it possible to get the up-to-date backup?
(If I have something wrong, sorry about that, that was my interview question)

Thanks for all,
Kind regards
DB
DB wrote:
While you take the cumulative incremental backup RMAN.
During this time users keep be updated, insert the corresponding schema.
But my Client doesn't backup up-to-date. Is it possible to get the up-to-date backup?
(If I have something wrong, sorry about that, that was my interview question)

Thanks for all,
Kind regards
DB

RMAN backup is not compatible and easy to follow on-line transactions. If it's something any purpose of migration suggest taking COLD backup.
If it's no way suggested, then after your entire + cumulative backups, however, that data will be available in archives

Problems with the retention policy that removes a Cumulative incremental backup

Hello
I have following two scripts:
1 RMAN script runs the weekend and made a full backup of level 0.
2 RMAN script works on a daily basis and a level 1 Cumulative backup.
at the end of each script I delete noprompt obsolete redundancy 1; (I don't need a single copy of local disk)
My problem is that it seems that remove obsolete handles only level 0 (full) backups.
for example, my goal is:
Saturday = > level 0 + delete obsolete (level 0 + all the incremental)
Sunday = > obsolete level 1 cumulative + delete
Monday = > level 1 cumulative + Delete obsolete (backup Sunday)
etc...
What happens in reality is rather that remove obsolete Monday, completely ignores Sunday 1 cumulative level.
and he keeps all the up to the next level 0 backup
its actually covered in the Oracle Documentation:
http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400
but it's just not make sense.
in order to have redundancy of 1 copy I only need to level 0 + unique Level 1 cumulative backup.
I don't have level 0 + all level 1 cumulative backups between full backups.

so my question is there a way to make the retention policy to keep only the last level 1 cumulative?

It's true window of 1 day recovery ignores several backups of cumulativ made the same day as being obsolete. Regular retention strategies rman probably cannot provide what you want. You can manually identify the backupset and delete them or change of cumulativ backups to incremental backups.

That would save the space of several cumulative backups and and would work even for several backups on the same day. Of course with the disadvantage that you need all of the incremental backups and your recovery time may be longer

Cumulative incremental backup solution?
Hi all,

I want to use the backup strategy incremental cumulative rman i.e.I want to take a full backup Level0 every week (Sunday) and a cumulative LEVEL1 database incremental backup every day.

RMAN configuration parameters are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
CONFIGURE BACKUP OPTIMIZATION * / / I did this to avoid making backup on the same archivelogs files, in this case RMAN backs up only files that were not saved in amont.*
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default value
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO "%F", # default value
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL. ORA'; # by default

Here's my RMAN scripts:

Weekly.RMAN
-------------------
+ race {+
ACE OF COMPRESSED BACKUPSET BACKUP
ADDITIONAL = 0 CUMULATIVE
DEVICE DISC TYPE
TAG = "LEVEL0-SUNDAY.
FORMAT 'D:\RMAN_BACKUP\DB_%d_%u_%s_%T '.
DATABASE;
overlap archivelog all;
remove expired archivelog all;
AS to COMPRESSED BACKUPSET ARCHIVELOG BACKUP ALL FORMAT 'D:\RMAN_BACKUP\arch_%d_%u_%s_%T ';
CROSS-CHECKING OF BACKUP;
DELETE NOPROMPT OBSOLETE; Delete the backup (Level0 and LEVEL1) and archivelogs files because RETENTION POLICY to REDUNDANCY 1 and to offer a free space for new backup Level0.
DELETE THE EXPIRED NOPROMPT BACKUP;
overlap archivelog all;
remove expired archivelog all;
DELETE NOPROMPT ARCHIVELOG until 'SYSDATE-3 ";
+}+

Daily.RMAN
-------------
+ race {+
ACE OF COMPRESSED BACKUPSET BACKUP
ADDITIONAL = 1 CUMULATIVE
DEVICE DISC TYPE
TAG = "LEVEL1-MONDAY.
FORMAT 'D:\RMAN_BACKUP\DB_%d_%u_%s_%T '.
DATABASE;
AS to COMPRESSED BACKUPSET ARCHIVELOG BACKUP ALL FORMAT 'D:\RMAN_BACKUP\arch_%d_%u_%s_%T ';
overlap archivelog all;
remove expired archivelog all;
DELETE NOPROMPT ARCHIVELOG until 'SYSDATE-3'; * //To remove archivelog files more elders that 3 days, I don't have enough space to store files to archive all the weekly
+}+

What do you think of the RMAN scripts?
You have a better solution?

Thanks in advance for any proposal or suggestion!
Scripts look good. But why use "cross check archivelog all; and delete all; expired archivelog' several times?

RMAN incremental backup levels
Hi experts,

It is a 10g database operates in archivelog mode.

It's the backup plan I currently use:

backup database archivelog; (runs once a day)

database backup incremental level 1; This runs every 3 hours

All of the incremental backups that I do are level 1.

* I will be able to restore, if I have no extra 0 level? **

Thank you, John
user629010 wrote:
Thanks for the replies.

So I should make a level 0 backup immediately after the full backup (backup of database ;) is that correct?

Not its correct level 0 is in fact the entire backup only. This is the point which includes everything and hereonly, you start your next batch of incremental backups. You can throw the last backups made if you have taken a level 0 backup, because it covers everything and is a full backup.

HTH
Aman...

Differential incremental backup for RAC

I inherited a CAR of two nodes (11r2 on RHEL 5.8 tikanga) with a shared network directory to be used as a backup location. He is the current backup strategy.

RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTdb are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;  # default
CONFIGURE BACKUP OPTIMIZATION OFF;  # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;  # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;  # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';  # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;  # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE MAXSETSIZE TO UNLIMITED;  # default
CONFIGURE ENCRYPTION FOR DATABASE OFF;  # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128';  # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;  # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;  # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_testdb1.f';  # default

The above is for the node 1, node 2 is identical except for line 17 (he refers to the "_testdb2.f").

The backup script is below.

run
{
recovery copy of database with tag 'ORA_OEM_LVL0_TESTdb_PRIM' until time 'SYSDATE-7';
backup check logical incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA_OEM_LVL0_TESTdb_PRIM' database;
backup check logical archivelog all tag 'ORA_OEM_ARCH_TESTdb_PRIM';
}
allocate channel for maintenance device disk type;
crosscheck backupset;
crosscheck archivelog all;
delete noprompt obsolete device type disk;

I'm a relatively new DBA, but I think that the strategy above maybe even does not work like the "db_recovery_file_dest" SQLPLUS references + FRA (not the shared network directory) and the two places (both FRA directories) and shared network directory without large amounts of data in them. I think that the previous owners of this CAR may not had adequate support DBA.

In any case, I thought to change the configuration as such:

RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTdb are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON; 
CONFIGURE DEFAULT DEVICE TYPE TO DISK;  # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';  # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/SharedNetworkDrive/ora_df%t_s%s_s%p';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;  # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE MAXSETSIZE TO UNLIMITED;  # default
CONFIGURE ENCRYPTION FOR DATABASE OFF;  # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128';  # default
CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;  # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_testdb1.f';  # default

RUN
{
RECOVER COPY OF DATABASE WITH TAG 'incr_update' UNTIL TIME 'SYSDATE - 7';
BACKUP INCREMENTAL LEVEL 1  FOR RECOVER OF COPY WITH TAG 'incr_update' DATABASE PLUS ARCHIVELOG;
DELETE ARCHIVELOG ALL;
}

I don't know that miss me a few things in my backup strategy. Any advice is greatly appreciated!

Thank you

PS - Yes, we have a license for compression

Good point about ARCHIVELOG ALL DELETE. Your suggestion would be to replace it with DELETE NOPROMPT OBSOLETE? Do I need to perform a cross-checking beforehand or Oracle already know from the backup?

CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED 1 TIME TO THE DISK.
INCREMENTAL BACKUP LEVEL 1 for BACK OF COPY WITH TAG "incr_update" DATABASE MORE ARCHIVELOG;
DELETE ARCHIVELOG ALL;

As you have Setup CONFIGURE the STRATEGY of DELETING ARCHIVELOG RMAN will not delete archivelog until archivelog backup 1 time on the disc.

But HemantKChitale have a good point, if for some reason any person clearly that the configuration you'll probably ARCHIVELOG DELETE without backup, do your backup is inconsistent.

So is advised 'INCREMENTAL BACKUP of LEVEL 1 TO RETRIEVE COPY WITH TAG "incr_update" base of DATA PLUS ARCHIVELOG DELETE INPUT' or 'BACKUP ARCHIVELOG ALL DELETE INPUT';

You can avoid delete the archivelogs without backup, because RMAN will only remove saved ARCHIVELOGS.

Is slow makes differential incremental backup restore?
DB version: 11.2
Platform: Unix/Unix

Lets say we have a 1 TB database and we have 2 GB of change every day.

For a differential incremental backup
```
Sunday -->     Level 0 backup

Monday -->     Level 1 backup  --------> Monday's Backup piece size of    2gb
Tuesday-->     Level 1 backup  --------> Tuesday's Backup piece size of   2gb
Wednesday-->     Level 1 backup  --------> Wednesday's Backup piece size of 2gb
Thursday-->     Level 1 backup  --------> Thursday's Backup piece size of  2gb
Friday-->     Level 1 backup  --------> Friday's Backup piece size of    2gb
Saturday-->      Level 1 backup  --------> Saturday's Backup piece size of  2gb
```
For a cumulative incremental backup, all changes Sunday will be saved for each LEVEL 1 run
```
Sunday -->     Level 0 backup

Monday -->     Level 1 backup  --------> Monday's Backup piece size of    2gb 
Tuesday-->     Level 1 backup  --------> Tuesday's Backup piece size of   4gb (monday + tuesday)
Wednesday-->     Level 1 backup  --------> Wednesday's Backup piece size of 6gb (monday + tuesday + Wednesday)
Thursday-->     Level 1 backup  --------> Thursday's Backup piece size of  8gb (monday + tuesday + Wednesday+Thursday)
Friday-->     Level 1 backup  --------> Friday's Backup piece size of    10gb .
Saturday-->      Level 1 backup  --------> Saturday's Backup piece size of  12gb .
```
Lets say after the backup of LEVEL 1 of Friday (incremental or cumulative), we want to restore from a backup.

For the award of
================
RMAN will take backup of level 0 Sunday and apply all differential incremental backups (2 GB) until Friday.

For Cumulative
================
RMAN will take the level 0 of the Sunday backup and apply the latest cumulative backup taken on Friday (10 GB).

The only delay (if any) for the restoration of the differential backup is that RMAN should check all elements of backup that was created after the Sunday level 0. But y at - he's going to be a noticeable delay for RMAN in the follow-up of these elements of backup? Just search the catalog to find who are the backup items created by LEVEL 1 runs after Sunday LEVEL 0. This should take only milliseconds. Right?
Identify the backuppieces may not take a lot of time (However if you have a lot of data files and the data files by backupset, you would still have much backupsets every day!)

But if from your backups on tape, restore each day may have to be reading a different tape - library will pass some time 'mix tapes'.

Hemant K Collette

Cumulative incremental?
I hope that you all can answer a question for me. I was under the impression that a CUMULATIVE backup and an INCREMENTAL backup were two different things.

EXTRA STRENGTH : copies only the data blocks that have changed since the last full incremental backup, where the integer is 0 or 1 (see example 2-16).
CUMULATIVE : copy data blocks used since the last backup of level 0 (see example 2-16).

So, I'm going to 'Example 2-16'...
```
http://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta007.htm

Example 2-16 Performing a Cumulative Incremental Backup

This example backs up all blocks changed in the database since the most recent level 0 incremental backup. If no level 0 backup exists when you run a level 1 backup, then RMAN makes a level 0 backup automatically. Any inaccessible files are skipped.

BACKUP 
  INCREMENTAL LEVEL 1 CUMULATIVE
  SKIP INACCESSIBLE 
  DATABASE;
```
I'm confused. I thought that cumulative/differentials were exclusive types of backup. How the two can be referenced in the same block of code?

Thank you
Hello

Please donot merge in the same written document

Incremental backups:

An INCREMENTAL level 0 backup backs up all blocks of data in data files to back up. A level 0 incremental backup is identical to the contents of a FULL backup
But unlike a full backup, the level 0 backup is a part of the incremental backup strategy.

A backup copy of level 1 only changed blocks. A level 1 incremental backup is differential or CUMULATIVE.
* If they are cumulative, RMAN backs up all blocks changed since the last level 0 backup.*
* If the differential, RMAN backup blocks updated since last level 0 or incremental level 1 backup.*

HTH :)

Merger of the RMAN incremental backups
Hi all

I have a confusion.

Sunday I L0 scheduled backup (backup as compressed).
Then next 6 days (MON - sat) I incremental backup Level1 (differential).

So let's assume that if I need to restore the Thursday, I need Sunday L0 and L1 of (MON, TUE, WED).

Is it possible to merge L0 and L1 (until WEDNESDAY).

Please specify.

Thanks in advance.

Kind regards
Bikram
As long as you use differential incremental backups, you need all of them between the last level 0 backup and recovery at the time point. It is exactly the concept of cumulative incremental backups to change this behavior. In the case of cumulative backups you would only need the full backup and the incremental backup from Wednesday.

Werner

Restore cumulative incremental level 0 and cumulative incremental level 1 backups on a new host (not available Archivelogs)

Hi guys, I have a disaster to manage.

Due to a shooting incident, I physically lost my Oracle database server. Fortunately, I was doing extra effective Cumulative weekly 0 my databases backups and daily incremental cumulative level 1 of my databases on an external hard drive.

Now, I need to restore these backups on a new physical server. I don't have backups of the archivelogs.
Data loss can be allowed in this scenario. I have backup of the control file and the spfile (controlfile autobackup is configured).

How can I restore and recover my databases on the new server (with a different directory structure)? I do not use a recovery catalog.

Thanks in advance

Clamarion

@Hemant K Collette

I have good news! I was able to raestore and recover my database with almost no loss of data. I have a ws, helped by a DBA called J.P. Boileau. I did not use the Oracle Support solution because it was too complicated to deploy. That's what I did:

1. I arrived the last RCS of my backup cumulative incremental level 1 thanks to a list backup command.

2. then, I used the SNA to make a series until the SNA...

3. Finally, I did a restore of database; recover the database; and alter database open resetlogs.

It's the detailed output of a simulation testing of this solution:

[oracle@cumulative ~] $. oraenv

ORACLE_SID = [oracle]? ORCL

ORACLE_HOME = [/ home/oracle]? /U01/app/Oracle/product/11.2.0/dbhome_1

The Oracle base has been set on/u01/app/oracle

[oracle@cumulative ~] target rman $ /.

Recovery Manager: release 11.2.0.3.0 - Production on Thu Oct 3 09:12:30 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to the database target (not started)

RMAN > startup mount;

Oracle instance started

mounted database

Total System Global Area 835104768 bytes

Bytes of size 2232960 fixed

574623104 variable size bytes

251658240 of database buffers bytes

Redo buffers 6590464 bytes

RMAN > catalogue start by ' / u01/backup ';

From implicit overlapping backup 3 October 13

using the control file of the target instead of recovery catalog database

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 133 type device = DISK

Cut 7 objects

Implicit overlapping backup has completed 3 October 13

Starting copy implied overlap in October 3, 13

using channel ORA_DISK_1

Copy of implicit cross ended up at October 3, 13

the search for all files in the recovery area

cataloging files...

not cataloged files

the search for all files that match the/u01/backup model

List of unknown files from the database

=====================================

File name: /u01/backup/autobackup/o1_mf_s_827753589_94qxm5o3_.bkp

File name: /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

File name: /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

Do you want to catalog the files above (enter YES or NO)? Yes

cataloging files...

cataloging done

List of cataloged files

=======================

File name: /u01/backup/autobackup/o1_mf_s_827753589_94qxm5o3_.bkp

File name: /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

File name: /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

RMAN > overlap backupset;

using channel ORA_DISK_1

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd0_TAG20130930T114816_94loqk4w_.BKP element of backup RECID = 1 STAMP = 827495297

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495353_94losbfm_.BKP element of backup RECID = TONE 2 = 827495354

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd1_TAG20130930T115510_94lp4h7v_.BKP element of backup RECID = STAMP 3 = 827495711

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495755_94lp5w1f_.BKP element of backup RECID = STAMP 4 = 827495756

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/autobackup/2013_10_02/o1_mf_s_827749047_94qs58bo_.BKP backup RECID piece = 6 = 827749048 STAMP

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.BKP element of backup RECID = STAMP 5 = 827748980

"" element of verified backup: turned out to be "AVAILABLE"

handle=/U01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.BKP element of backup RECID = STAMP 8 = 827831641

verified backup item: found to be "EXPIRED".

handle=/U01/app/Oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.BKP element of backup RECID = STAMP 7 = 827753553

"" element of verified backup: turned out to be "AVAILABLE"

handle=/U01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.BKP element of backup RECID = STAMP 9 = 827831641

Cut 9 objects

RMAN > list backup;

List of backup sets

===================

Time of accomplishment BS key Type LV size device Type elapsed time

------- ---- -- ---------- ----------- ------------ ---------------

1 DISK of 1.06 G Incr 0 00:00:51 30-SEP-13

BP key: 1 situation: EXPIRED compressed: NOT of Tag: TAG20130930T114816

Part name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd0_TAG20130930T114816_94loqk4w_.bkp

List of files to backup data value 1

Name of file LV Type cash SNA cash time

---- -- ---- ---------- --------- ----

1 0 incr 1123837 /u01/app/oracle/oradata/orcl/system01.dbf 30-SEP-13

2 0 1123837 /u01/app/oracle/oradata/orcl/sysaux01.dbf incr 30-SEP-13

3 0 incr 1123837 /u01/app/oracle/oradata/orcl/undotbs01.dbf 30-SEP-13

4 0 incr 1123837 /u01/app/oracle/oradata/orcl/users01.dbf 30-SEP-13

5 0 incr 1123837 /u01/app/oracle/oradata/orcl/example01.dbf 30-SEP-13

Time of accomplishment BS key Type LV size device Type elapsed time

------- ---- -- ---------- ----------- ------------ ---------------

2 full 9.36 M DISC 01:00:00 30-SEP-13

BP key: 2 location: EXPIRED compressed: NOT of Tag: TAG20130930T114913

Part name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495353_94losbfm_.bkp

SPFILE included: Modification Date: 30-SEP-13

SPFILE db_unique_name: ORCL

Control file included: cash SNA: 1123870 cash time: 30-SEP-13

Time of accomplishment BS key Type LV size device Type elapsed time

------- ---- -- ---------- ----------- ------------ ---------------

3 incr 1 DISK of 4.54 M 00:00:39 30-SEP-13

BP key: 3 location: EXPIRED compressed: NOT of Tag: TAG20130930T115510

Part name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_09_30/o1_mf_nnnd1_TAG20130930T115510_94lp4h7v_.bkp

List of files of data in backup set 3

Name of file LV Type cash SNA cash time

---- -- ---- ---------- --------- ----

1 1 incr 1124362 /u01/app/oracle/oradata/orcl/system01.dbf 30-SEP-13

2 1 incr 1124362 /u01/app/oracle/oradata/orcl/sysaux01.dbf 30-SEP-13

3 1 incr 1124362 /u01/app/oracle/oradata/orcl/undotbs01.dbf 30-SEP-13

4 1 incr 1124362 /u01/app/oracle/oradata/orcl/users01.dbf 30-SEP-13

5 1 incr 1124362 /u01/app/oracle/oradata/orcl/example01.dbf 30-SEP-13

Time of accomplishment BS key Type LV size device Type elapsed time

------- ---- -- ---------- ----------- ------------ ---------------

4 whole 9.36 M DISC 01:00:00 30-SEP-13

BP key: 4 location: EXPIRED compressed: NOT of Tag: TAG20130930T115555

Part name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_09_30/o1_mf_s_827495755_94lp5w1f_.bkp

SPFILE included: Modification Date: 30-SEP-13

SPFILE db_unique_name: ORCL

Control file included: cash SNA: 1124391 cash time: 30-SEP-13

Time of accomplishment BS key Type LV size device Type elapsed time

------- ---- -- ---------- ----------- ------------ ---------------

6 whole 9.36 M DISK 00:00:01 2 October 13

BP key: 6 location: EXPIRED compressed: NOT of Tag: TAG20131002T101727

Part name: /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2013_10_02/o1_mf_s_827749047_94qs58bo_.bkp

SPFILE included: Date modified: October 2, 13

SPFILE db_unique_name: ORCL

Control file included: cash SNA: 1177698 cash time: 2 October 13

BS key Type LV size

------- ---- -- ----------

8 0 incr 1.06 G

List of files to backup set of 8 data

Name of file LV Type cash SNA cash time

---- -- ---- ---------- --------- ----

1 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/system01.dbf

2 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

3 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

4 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/users01.dbf

5 0 incr 1177574 2 October 13 /u01/app/oracle/oradata/orcl/example01.dbf

Backup the exemplary value of the backup set of 8 #1

Time of accomplishment of the time Type compressed device Tag

----------- ------------ --------------- ---------- ---

00:00:00 DISC 2 OCTOBER 13 NO. TAG20131002T101620

The list of items to backup the save game 8 copy #1

Name of the Key BP Pc # status element

------- --- ----------- ----------

5 1 EXPIRED /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp

Backup the exemplary value no. 2 backup set of 8

Time of accomplishment of the time Type compressed device Tag

----------- ------------ --------------- ---------- ---

DISC 00:00:00 3 OCTOBER 13 NO. TAG20131002T101620

The list of items to backup the save game 8 copy #2

Name of the Key BP Pc # status element

------- --- ----------- ----------

8 1 /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp AVAILABLE

BS key Type LV size

------- ---- -- ----------

9 incr 1 9,20 M

List of files to backup data value 9

Name of file LV Type cash SNA cash time

---- -- ---- ---------- --------- ----

1 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/system01.dbf

2 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/sysaux01.dbf

3 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/undotbs01.dbf

4 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/users01.dbf

5 1 incr 1182056 2 October 13 /u01/app/oracle/oradata/orcl/example01.dbf

The exemplary value value 9 Backup #1 backup

Time of accomplishment of the time Type compressed device Tag

----------- ------------ --------------- ---------- ---

00:00:00 DISC 2 OCTOBER 13 NO. TAG20131002T113233

List backup to backup the value 9 #1 copy items

Name of the Key BP Pc # status element

------- --- ----------- ----------

7 1 EXPIRED /u01/app/oracle/fast_recovery_area/ORCL/backupset/2013_10_02/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp

Backup the exemplary value no. 2 backup the value 9

Time of accomplishment of the time Type compressed device Tag

----------- ------------ --------------- ---------- ---

DISC 00:00:00 3 OCTOBER 13 NO. TAG20131002T113233

List backup to backup the value 9 #2 copy items

Name of the Key BP Pc # status element

------- --- ----------- ----------

9 1 /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp AVAILABLE

RMAN > run {}

2 > until the SNA 1182056.

3 > restore database;

4 > restore database;

{5 >}

executing command: SET until clause

From restoration to 3 October 13

using channel ORA_DISK_1

channel ORA_DISK_1: from the restore backup set data file

channel ORA_DISK_1: specifying datafile (s) to restore from backup set

channel ORA_DISK_1: restore datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf

channel ORA_DISK_1: restore datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf

channel ORA_DISK_1: restore datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf

channel ORA_DISK_1: restore datafile 00004 in /u01/app/oracle/oradata/orcl/users01.dbf

channel ORA_DISK_1: restore datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf

channel ORA_DISK_1: backup /u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp piece reading

channel ORA_DISK_1: room handle=/u01/backup/o1_mf_nnnd0_TAG20131002T101620_94qs34qw_.bkp tag = TAG20131002T101620

channel ORA_DISK_1: restored the backup part 1

channel ORA_DISK_1: restore complete, duration: 00:00:47

Restoration finished in October 3, 13

From pick up to 3 October 13

using channel ORA_DISK_1

channel ORA_DISK_1: from additional data file from the restore backup set

channel ORA_DISK_1: specifying datafile (s) to restore from backup set

destination for the restoration of the data file 00001: /u01/app/oracle/oradata/orcl/system01.dbf

destination for the restoration of the data file 00002: /u01/app/oracle/oradata/orcl/sysaux01.dbf

destination for the restoration of the data file 00003: /u01/app/oracle/oradata/orcl/undotbs01.dbf

destination for the restoration of the data file 00004: /u01/app/oracle/oradata/orcl/users01.dbf

destination for the restoration of the data file 00005: /u01/app/oracle/oradata/orcl/example01.dbf

channel ORA_DISK_1: backup /u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp piece reading

channel ORA_DISK_1: room handle=/u01/backup/o1_mf_nnnd1_TAG20131002T113233_94qxl1yt_.bkp tag = TAG20131002T113233

channel ORA_DISK_1: restored the backup part 1

channel ORA_DISK_1: restore complete, duration: 00:00:07

starting media recovery

media recovery complete, duration: 00:00:01

Finished recover to 3 October 13

RMAN > alter database open resetlogs;

open database

RMAN >

Thanks again for all your help and patience.

Concerning

Clamarion.

How to set the incremental backup of level 1 to restore on a different database

Hello
I have a question what is annoys me all week.
I have 2 databases. ORCL and ORCL2. ORCL2 is an auxiliary ORCL database. ORCL my database is backup incrementaly Sunday level 0, other days level 1. Now, I would like to update my ORCL2 db every night to be synchronized with the ORCL database. Is this possible? I have Oracle Standard Edition, so I can't use Data guard. If you can help me I would be very thanful. Or if you could send me a link to some textbooks.
I have db Oracle 10.2.0.3 Standard Edition
Windows Server 2003 Standard edition
With respect,
Ivan

Hello Ivan,.

You can recover the database duplicate, once created each day with an incremental backup of the target database.

What you need here is a simple restore to another host without opening the database with resetlogs. RMAN: Restoring a backup RMAN to another node [ID 73974.1]

Thank you

Unlike cumulative and incremental backups in RMAN premium

Could someone please explain with example on Cumulative and differential incremental backups in RMAN... ?

It is true that in Oracle 10 g, we have only level 0 and level 1 incremental backups?

-Yasser

incremental backup diffrentail backup of the blocks that have changed since the last level or same level backup IE

SAT             L0     (include blocks which ever been used block 1,2,3)
after that             block changed only 3
SUN             L1     (block 3)
after that             block changed occur 2
MON             L1     (include block only 2)
Mon (night)     L2     (include those block which modified after Monday L1 backup)

Cumulative will take backup with its level (n-1)

SAT             L0     (include blocks which ever been used block 1,2,3)
after that             block changed only 3
SUN             L1     (here n is 1 then n-1=0 include block 1,2,3)
MON             L1     (here n is 1 then n-1=0 include block  1,2,3)
Mon (night)     L2     (here n is 2 then n-1=1 include those block which modified after Monday L1 backup)

Khurram

What is the right tag for level 1 incremental backup?

We have a level 0 backup Sunday like this:
Run {}
Compressed backupset backup
filesperset 1
database incremental level 0
tag = "LEVEL_0_BACKUP."
include current controlfile
more entered archivelog delete;
SQL 'alter database backup controlfile to trace. "
}
And level 1 incremental backup Monday Saturday like this:
Run {}
Compressed backupset backup
database incremental level 1
tag = "LEVEL_1_BACKUP."
include current controlfile
more entered archivelog delete;
SQL 'alter database backup controlfile to trace. "
}
These scripts exist some time ago. I wonder if the level 1 tag must be same as level 0 to all combined together?
Please advice kindly.

849425 wrote:

Thanks for all your response.

What, in my opinion, is with block change tracking turned on, is that the differential must roll in the full backup of level 0?

What makes you think that? Block change tracking allows simply to rman avoid having to analyze each block to see if it needs to be saved.

I've never heard of a differential (level 1) 'random' in level 0.

Recovery begins by restoring the files of level 0. Followed by the restoration of the blocks from level 1. Follow up by applying archived redo changes. Follow-up (if necessary) changes it again online.

As stated previously, the tags are just user-defined labels. Use however seems them appropriate - after fully understand what they are and what they are not. Tags specified by the user are not even necessary. I'd be cautious about change in a system already set up and running.

Case of level 1 RMAN incremental backup failure...

Hello
I have a question. If the incremental level 1 RMAN backup fails, the next level 1 backup attempt will have backup all changes since the last backup of level 0 OR level 1 successful?
Best regards

Hello

I have a question. If the incremental level 1 RMAN backup fails, the next level 1 backup attempt will have backup all changes since the last backup of level 0 OR level 1 successful?

Check the dictionary BACKUP_SET V$ to confirm if the last backup has been affected by the data dictionary. If incremental backup failed is picked up then the last incremental backup will be required in the case of the next LEVEL 1 DIFFERENTIAL INCREMENTIELLE backup.

But to be on the safe side, it is recommended that you take a LEVEL 01 CUMILATIVE INCREMENTAL backup of level 0 up to this day. For the recovery process can go through even if the previous backup is not valid.

Thank you &

Best regards

difference between cumulative backup and incremental backup
Hi all

What is the difference between cumulative incremental and differential backup incremental backup.
Go and take a look at the link below

http://download.Oracle.com/docs/CD/B1930601/backup.102/b14192/bkup004.htm_

EM12c create non-cumulative incremental backups (level 1) against target DB

Similar Questions

Maybe you are looking for