Cumulative incremental?

Similar Questions

• 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.

• 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

• 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?

• 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 LEVEL BACKUP INCREMENTAL 0 AND 1 OF CUMULATIVE LEVEL

  Dear friends

  This is Eliza, I need some clarification, your suggestion will help me more...

  Currently I am working in RMAN backup and restore, recovery and I need to take the extra SIZE 0 AND LEVEL 1 CUMULATIVE

  I know something about what level rman incremental 0 and level 1 cumulative can do is, first I have to take the level 0 and then level 1 respectively.

  As follows

  SUNDAY: LEVEL 0 CUMULATIVE

  MONDAY - SATURDAY: LEVEL 1 CUMULATIVE

  SUNDAY: LEVEL 0 CUMULATIVE (repetition of this cycle)
  

  MY QUESTION IS

  Can I use after an order to take INCREMENTIELLE LEVEL 1 CUMULATIVE backup of,

  CUMULATIVE DATABASE INCREMENTAL LEVEL 1; # has changed since the level 0 blocks

  But, if I want to take CUMULATIVE INCREMENTAL level 0 BACKUP, that is me I want to use the following,

  INCREMENTAL LEVEL 0 BACKUP CUMULATIVE BASIS;

  (GOLD)

  DATABASE INCREMENTAL LEVEL 0 BACKUP;

  (GOLD)

  Suggest me your valuable idea. Thanks in advance.

  
  

  Hello

  I think that this CUMULATIVE or incremental level 0 backup specification makes no sense so INCREMENTAL level 0 BACKUP database; = INCREMENTAL CUMULATIVE 0 DATA LEVEL;

• 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_

• Incremental backup policy

  Hi experts,

  In my organization, we have 4 TB size of database. If we take a complete backup of it, will it take huge time. While we do intend to follow an incremental backup of this jet of RMAN database, my question is, what kind of policy of incremental backup, we follow. I am new to an incremental backup. Yet, I was followed political only full backup.

  (1) we must / should follow political not backup incremental cumulative GOLD diffrential.

  (2) who is stupid or why (cumulative backup incremental GOLD diffrential)

  (3) how to track level in both cases...

  as = > Sunday M T W T F S Sunday

  0 2 2 1 2 2 2 0

  Reg,

  Thomas

  I would prefer cumulative incremental but if the daily a cumulative incremental size is large, you could make an additional bonus.  The disadvantages of additional premium are

  (a) If you lose an additional intermediate differential, you cannot restore the database past the point (unless you have backups, archivelog separated through all database backups)

  (b) it may take more time to restore and recover using additional bonus you would need to restore and apply backups more

  See http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV109

  Note: Level 2 is is more documented.  Level 2 backups are actually incremental differential.

  Hemant K Collette

• 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

• for the cumulative backup catalog view

  Hi all
  
  I take, I'm 11.2.0.1 two trgt db and recovery of the catalog... my question is, is there any notice that I can query for the type of backup that I've taken?
  
  for example, I can easily query rc_backup_piece go I did a level 0, level 1 incremental backup... but what to the query, if I want to know info when I made a cumulative backup of level 1? or the oracle dose dose does not provide that, as I watched almost all the views in the recovery catalog and dose not this info... my backup syntax is cumulative database backup incremental level 1; (obviosuly I got level 0 backup before I did)...

  Hello

  is there advice I can query for the type of backup that I took?

  The view v$ backup_set_details or (rc_backup_set_details to the catalog) are close.
  The difference between a differential or cumulative incremental backups cannot be questioned since this fine point of view.
  Kind regards
  Tycho

• 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

• RMAN delete policy has not worked and not delete outdated backup

  Hi all

  I am facing a problem this obsolete backup is not delete unwanted backup.

  I used to take level 0 once weekly and cumulative incremental in 3 times a day.

  I have 2 TB hard drive, every week, I used the backup from command remove obsolete based file can delete based on my redundancy strategy 1.

  The previous week it works fine and deleted obsolete backup based on the deletion policy. but this week when I try to use the delete obsolete command, it is not removed and the hard drive is always full and I couldn't take later backup.

  It's live server, I need to take the free space on the hard drive. Please help me.

  You will find details of error that I met in the log file.

  output channel: C1

  output channel: C2

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of backup so archivelog command at 05/05/2015 10:57:14

  ORA-19502: write error on file 'G:\RMAN\AWSPROCESS\BACKUP\AWSPROCESS\BACKUPSET\2015_05_05\O1_MF_NNND1_TAG20150505T090032_BNJGC9RR_. BKP", the number of block 7227648 (block size = 8192)

  ORA-27070: async read/write failed

  OSD-04016: error queuing an asynchronous i/o request.

  S/O-error: (OS 112) there is not enough space on the disk.

  Your backup on May 02 is not a valid backup, then you can try something like:

  RMAN > delete database backup completed after 'sysdate-6 ";

• New added file how to recover using backup controlfile

  Hi all

  From a complete backup direct (extra number 0) I cloned a new dev server database. The next day a new data file added in Live and I took a cumulative incremental backup in Live. Live and Dev server have not even mount point. While the restoration itself I gave the name of the new set for the control of data file to remap all the data files in the new location on the dev server. Now, I want to know how to get back with cumm incr backup when a new data added live file.

  Concerning

  Jennifer

  DBA CTS team

  I restored a backup of incr 0 in dev server with the set new name command. and after that I got the database with the archives transferred to live. and then I opened the database with reset logs... now the database is open... the next day I took differential bkp live to contain the new datafile... How can you apply that backup incr 1 cumm in my dev server.

  You must restart level 0, i.e.

  1. After the level 1 backup archivelogs
  2. backup controlfile
  3. have all the backups on the dev server (level 0, 1, archivelogs and controlfile)
  4. Restore controlfile (from #2)
  5. restore the backup of level 0 (with set newname, including the new data file)
  6. recover the database
  7. Open the database with the resetlogs option.

• Hot RMAN backup fails every time in R12.

  Hi experts,

  Please suggest me that I have to plan rman backup hot. I have "write" command to perform hot backup. When I take backup hot of 1st time the backup completed successfully. but when I run the same command resume backup for the second day. it is impossible to give space issue I havhot e calendar for daily use rman backup.

  I had to take the backup hot daily and I want backup overwrite the backup file according to the daily backup.

  Please suggest me what I need to make changes in the configuration of rman and the rman command.

  OS - réhèl 5.6

  Database - 11.1

  EBS - r12.3

  configuration of RMAN:

  RMAN > show all.
  
  Database with db_unique_name UAT RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  CONFIGURE BACKUP OPTIMIZATION
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / d06/UAT/rman_hot_backup/Backup_daily%d_DB_%u_%s_%p';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d06/UAT/db/tech_st/11.1.0/dbs/snapcf_UAT.f'; # by default
  
  RMAN >

  
  

  ##############################################################################################################

  
  

  RMAN command that I used to make hot extra strength 0 cumulative backup.

  
  RMAN > run
  {
  allocate channels c1 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  allocate channel c2 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  allocate channels c3 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  allocate channel c4 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  cumulative incremental database backup level 1 more archivelog;
  output channel c1;
  output channel c2.
  output channel c3.
  output channel c4.
  }
  

  If something bad in the configuration of rman and my order please suggest me to take the backup hot every day with success.

  
  

  concerning

  pritesh Rodriguez
  

  Hi Pritesh, thanks for the update. You can mark this thread as answered if your questions have been answered. cordially Karan