Incremental cumulative backup ?

Oracle 11.2.0.2 / Windows 2008
Up till now, I've been running nightly 'full' backups but I've now decided to run Incremental Cumulative backups. What I plan to do is create a level '0' backup on a Monday night, and then run daily level '1' (cumulative) backups from Tuesday - Sunday and then for the whole process to start again for the following week. I've setup this up within enterprise manager (and I'm going to run them via enterprise manager) and it has produced the below scripts
Level 0
$rman_script="backup incremental level 0 cumulative device type disk tag '%TAG' database;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);
Level 1
$rman_script="backup incremental level 1 cumulative device type disk tag '%TAG' database;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);
At the moment, my retention policy is set to 31 days and the 'Retain at least the specified number of full backups for each datafile is set to '1'. Do I have to change this to cater for the above ?
Thanks in advance for any assistance

>'Retain at least the specified number of full backups for each datafile is set to '1'.
Are you referring to configuration in your MML -- NetBackup or Networker or the like ?
RMAN's retention policy is in terms of either redundancy (number of copies) or days (number of days).  You've defined it to be 31 days so the oldest backup that would not be obsoleted would be the L0 backup closest to sysdate-31 at any time.
Hemant K Chitale

Similar Messages

  • Incremental cumulative backup solution?

    Hi to all,
    I want to use rman cumulative incremental backup strategy i.e.I want to take one full database backup LEVEL0 every week (Sunday), and one incremental cumulative LEVEL1 database backup every day.
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON;* *// I did this to avoid doing backup on the same archivelogs files, in this case RMAN will backup only files that were not backed up.*
    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 ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default
    Here are my RMAN scripts:
    weekly.rman
    +run {+
    BACKUP AS COMPRESSED BACKUPSET
    INCREMENTAL LEVEL = 0 CUMULATIVE
    DEVICE TYPE DISK
    TAG = 'LEVEL0-SUNDAY'
    FORMAT 'D:\RMAN_BACKUP\DB_%d_%u_%s_%T'
    DATABASE;
    crosscheck archivelog all;
    delete expired archivelog all;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT 'D:\RMAN_BACKUP\arch_%d_%u_%s_%T';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE; // To delete backup (LEVEL0 and LEVEL1) and archivelogs files because RETENTION POLICY TO REDUNDANCY 1 and to make free space for new LEVEL0 backup.
    DELETE NOPROMPT EXPIRED BACKUP;
    crosscheck archivelog all;
    delete expired archivelog all;
    DELETE NOPROMPT ARCHIVELOG UNTIL TIME "SYSDATE-3";
    +}+
    daily.rman
    +run {+
    BACKUP AS COMPRESSED BACKUPSET
    INCREMENTAL LEVEL = 1 CUMULATIVE
    DEVICE TYPE DISK
    TAG = 'LEVEL1-MONDAY'
    FORMAT 'D:\RMAN_BACKUP\DB_%d_%u_%s_%T'
    DATABASE;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT 'D:\RMAN_BACKUP\arch_%d_%u_%s_%T';
    crosscheck archivelog all;
    delete expired archivelog all;
    DELETE NOPROMPT ARCHIVELOG UNTIL TIME "SYSDATE-3"; *//To delete archivelog files older than 3 days, I do not have enough space to store archive files from all week.*
    +}+
    What do you think about this RMAN scripts?
    Do you have a better solution?
    Thanks in advance for any proposal or suggestion!

    Your script looks good. As an alternative, you can also use the following command:
    Backup archivelog until time 'sysdate-3' backedup 1 times to 'sbt_tabe';
    Any suggestions are highly appreciated.
    Thanks,
    Sai.

  • Retention policy for incremental cumulative backup question

    Hi,
    I have a production database configured with retention policy for 30 days window. No catalog is used.
    The backup plan is:
    Sunday - Level 0 backup.
    Weekdays - Incremental 1 cumulative backup.
    I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
    Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
    Thanks for your help!
    RMAN> list backup summary;
    using target database control file instead of recovery catalog
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    *14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
    21 B F A SBT_TAPE 08-MAR-10 1 1 NO
    24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    27 B F A SBT_TAPE 08-MAR-10 1 1 NO
    35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    38 B F A SBT_TAPE 09-MAR-10 1 1 NO
    46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    49 B F A SBT_TAPE 10-MAR-10 1 1 NO
    57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
    60 B F A SBT_TAPE 11-MAR-10 1 1 NO
    66 B A A SBT_TAPE 12-MAR-10 1 1 NO
    67 B A A SBT_TAPE 12-MAR-10 1 1 NO
    68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
    70 B A A SBT_TAPE 12-MAR-10 1 1 NO
    71 B F A SBT_TAPE 12-MAR-10 1 1 NO
    77 B A A SBT_TAPE 14-MAR-10 1 1 NO
    78 B A A SBT_TAPE 14-MAR-10 1 1 NO
    79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    81 B A A SBT_TAPE 14-MAR-10 1 1 NO
    82 B F A SBT_TAPE 14-MAR-10 1 1 NO
    88 B A A SBT_TAPE 15-MAR-10 1 1 NO
    89 B A A SBT_TAPE 15-MAR-10 1 1 NO
    90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    92 B A A SBT_TAPE 15-MAR-10 1 1 NO
    93 B F A SBT_TAPE 15-MAR-10 1 1 NO
    99 B A A SBT_TAPE 16-MAR-10 1 1 NO
    100 B A A SBT_TAPE 16-MAR-10 1 1 NO
    101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    103 B A A SBT_TAPE 16-MAR-10 1 1 NO
    104 B F A SBT_TAPE 16-MAR-10 1 1 NO
    109 B A A SBT_TAPE 17-MAR-10 4 1 NO
    110 B F A SBT_TAPE 17-MAR-10 1 1 NO
    111 B A A SBT_TAPE 17-MAR-10 1 1 NO
    112 B F A SBT_TAPE 17-MAR-10 1 1 NO
    113 B A A SBT_TAPE 17-MAR-10 1 1 NO
    114 B A A SBT_TAPE 17-MAR-10 1 1 NO
    115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
    117 B A A SBT_TAPE 17-MAR-10 1 1 NO
    118 B F A SBT_TAPE 17-MAR-10 1 1 NO
    123 B A A SBT_TAPE 18-MAR-10 2 1 NO
    124 B F A SBT_TAPE 18-MAR-10 1 1 NO
    125 B A A SBT_TAPE 18-MAR-10 2 1 NO
    126 B F A SBT_TAPE 18-MAR-10 1 1 NO
    127 B A A SBT_TAPE 18-MAR-10 1 1 NO
    128 B F A SBT_TAPE 18-MAR-10 1 1 NO
    129 B A A SBT_TAPE 18-MAR-10 1 1 NO
    130 B F A SBT_TAPE 18-MAR-10 1 1 NO
    131 B A A SBT_TAPE 18-MAR-10 1 1 NO
    132 B A A SBT_TAPE 18-MAR-10 1 1 NO
    133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
    135 B A A SBT_TAPE 18-MAR-10 1 1 NO
    136 B F A SBT_TAPE 18-MAR-10 1 1 NO
    142 B A A SBT_TAPE 19-MAR-10 2 1 NO
    143 B F A SBT_TAPE 19-MAR-10 1 1 NO
    144 B A A SBT_TAPE 19-MAR-10 1 1 NO
    145 B F A SBT_TAPE 19-MAR-10 1 1 NO
    146 B A A SBT_TAPE 19-MAR-10 1 1 NO
    147 B F A SBT_TAPE 19-MAR-10 1 1 NO
    148 B A A SBT_TAPE 19-MAR-10 1 1 NO
    149 B F A SBT_TAPE 19-MAR-10 1 1 NO
    150 B A A SBT_TAPE 19-MAR-10 1 1 NO
    151 B A A SBT_TAPE 19-MAR-10 1 1 NO
    152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
    154 B A A SBT_TAPE 19-MAR-10 1 1 NO
    155 B F A SBT_TAPE 19-MAR-10 1 1 NO
    161 B A A SBT_TAPE 21-MAR-10 1 1 NO
    162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    164 B A A SBT_TAPE 21-MAR-10 1 1 NO
    165 B F A SBT_TAPE 21-MAR-10 1 1 NO
    171 B A A SBT_TAPE 22-MAR-10 1 1 NO
    172 B F A SBT_TAPE 22-MAR-10 1 1 NO
    173 B A A SBT_TAPE 22-MAR-10 1 1 NO
    174 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       19     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_5_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       18     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_4_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       17     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_3_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       16     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_2_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       15     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_1_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       14     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_5_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       13     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_4_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       12     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_3_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       11     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_2_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       10     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_1_1
    Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
    Edited by: user12019850 on 22-Mar-2010 10:53 AM

    Another database with the same configuration and same plan seems fine:
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
    RMAN> list backup summary;
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
    775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
    795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    797 B A A SBT_TAPE 20-FEB-10 1 1 NO
    803 B A A SBT_TAPE 20-FEB-10 1 1 NO
    804 B F A SBT_TAPE 20-FEB-10 1 1 NO
    805 B A A SBT_TAPE 20-FEB-10 1 1 NO
    806 B F A SBT_TAPE 20-FEB-10 1 1 NO
    807 B A A SBT_TAPE 20-FEB-10 1 1 NO
    808 B F A SBT_TAPE 20-FEB-10 1 1 NO
    809 B A A SBT_TAPE 21-FEB-10 1 1 NO
    810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
    811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
    812 B A A SBT_TAPE 21-FEB-10 1 1 NO
    813 B F A SBT_TAPE 21-FEB-10 1 1 NO
    818 B A A SBT_TAPE 21-FEB-10 1 1 NO
    819 B F A SBT_TAPE 21-FEB-10 1 1 NO
    820 B A A SBT_TAPE 21-FEB-10 1 1 NO
    821 B F A SBT_TAPE 21-FEB-10 1 1 NO
    822 B A A SBT_TAPE 21-FEB-10 1 1 NO
    823 B F A SBT_TAPE 21-FEB-10 1 1 NO
    824 B A A SBT_TAPE 22-FEB-10 1 1 NO
    825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    827 B A A SBT_TAPE 22-FEB-10 1 1 NO
    828 B F A SBT_TAPE 22-FEB-10 1 1 NO
    833 B A A SBT_TAPE 22-FEB-10 1 1 NO
    834 B F A SBT_TAPE 22-FEB-10 1 1 NO
    835 B A A SBT_TAPE 22-FEB-10 1 1 NO
    836 B F A SBT_TAPE 22-FEB-10 1 1 NO
    837 B A A SBT_TAPE 22-FEB-10 1 1 NO
    838 B F A SBT_TAPE 22-FEB-10 1 1 NO
    839 B A A SBT_TAPE 22-FEB-10 1 1 NO
    840 B F A SBT_TAPE 22-FEB-10 1 1 NO
    841 B A A SBT_TAPE 23-FEB-10 1 1 NO
    842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    844 B A A SBT_TAPE 23-FEB-10 1 1 NO
    845 B F A SBT_TAPE 23-FEB-10 1 1 NO
    850 B A A SBT_TAPE 23-FEB-10 1 1 NO
    851 B F A SBT_TAPE 23-FEB-10 1 1 NO
    852 B A A SBT_TAPE 23-FEB-10 1 1 NO
    853 B F A SBT_TAPE 23-FEB-10 1 1 NO
    854 B A A SBT_TAPE 23-FEB-10 1 1 NO
    855 B F A SBT_TAPE 23-FEB-10 1 1 NO
    856 B A A SBT_TAPE 24-FEB-10 1 1 NO
    857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    859 B A A SBT_TAPE 24-FEB-10 1 1 NO
    860 B F A SBT_TAPE 24-FEB-10 1 1 NO
    865 B A A SBT_TAPE 24-FEB-10 1 1 NO
    866 B F A SBT_TAPE 24-FEB-10 1 1 NO
    867 B A A SBT_TAPE 24-FEB-10 1 1 NO
    868 B F A SBT_TAPE 24-FEB-10 1 1 NO
    869 B A A SBT_TAPE 24-FEB-10 1 1 NO
    870 B F A SBT_TAPE 24-FEB-10 1 1 NO
    871 B A A SBT_TAPE 24-FEB-10 1 1 NO
    872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    874 B A A SBT_TAPE 24-FEB-10 1 1 NO
    875 B F A SBT_TAPE 24-FEB-10 1 1 NO
    880 B A A SBT_TAPE 24-FEB-10 1 1 NO
    881 B F A SBT_TAPE 24-FEB-10 1 1 NO
    882 B A A SBT_TAPE 25-FEB-10 1 1 NO
    883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    885 B A A SBT_TAPE 25-FEB-10 1 1 NO
    886 B F A SBT_TAPE 25-FEB-10 1 1 NO
    891 B A A SBT_TAPE 25-FEB-10 1 1 NO
    892 B F A SBT_TAPE 25-FEB-10 1 1 NO
    893 B A A SBT_TAPE 25-FEB-10 1 1 NO
    894 B F A SBT_TAPE 25-FEB-10 1 1 NO
    895 B A A SBT_TAPE 25-FEB-10 1 1 NO
    896 B F A SBT_TAPE 25-FEB-10 1 1 NO
    897 B A A SBT_TAPE 25-FEB-10 1 1 NO
    898 B F A SBT_TAPE 25-FEB-10 1 1 NO
    899 B A A SBT_TAPE 25-FEB-10 1 1 NO
    900 B F A SBT_TAPE 25-FEB-10 1 1 NO
    901 B A A SBT_TAPE 25-FEB-10 1 1 NO
    902 B F A SBT_TAPE 25-FEB-10 1 1 NO
    903 B A A SBT_TAPE 26-FEB-10 1 1 NO
    904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    906 B A A SBT_TAPE 26-FEB-10 1 1 NO
    907 B F A SBT_TAPE 26-FEB-10 1 1 NO
    912 B A A SBT_TAPE 26-FEB-10 1 1 NO
    913 B F A SBT_TAPE 26-FEB-10 1 1 NO
    914 B A A SBT_TAPE 26-FEB-10 1 1 NO
    915 B F A SBT_TAPE 26-FEB-10 1 1 NO
    916 B A A SBT_TAPE 26-FEB-10 1 1 NO
    917 B F A SBT_TAPE 26-FEB-10 1 1 NO
    918 B A A SBT_TAPE 27-FEB-10 1 1 NO
    919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    921 B A A SBT_TAPE 27-FEB-10 1 1 NO
    922 B F A SBT_TAPE 27-FEB-10 1 1 NO
    927 B A A SBT_TAPE 27-FEB-10 1 1 NO
    928 B F A SBT_TAPE 27-FEB-10 1 1 NO
    929 B A A SBT_TAPE 27-FEB-10 1 1 NO
    930 B F A SBT_TAPE 27-FEB-10 1 1 NO
    931 B A A SBT_TAPE 27-FEB-10 1 1 NO
    932 B F A SBT_TAPE 27-FEB-10 1 1 NO
    933 B A A SBT_TAPE 28-FEB-10 1 1 NO
    934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
    935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
    936 B A A SBT_TAPE 28-FEB-10 1 1 NO
    937 B F A SBT_TAPE 28-FEB-10 1 1 NO
    942 B A A SBT_TAPE 28-FEB-10 1 1 NO
    943 B F A SBT_TAPE 28-FEB-10 1 1 NO
    944 B A A SBT_TAPE 28-FEB-10 1 1 NO
    945 B F A SBT_TAPE 28-FEB-10 1 1 NO
    946 B A A SBT_TAPE 28-FEB-10 1 1 NO
    947 B F A SBT_TAPE 28-FEB-10 1 1 NO
    948 B A A SBT_TAPE 01-MAR-10 1 1 NO
    949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    951 B A A SBT_TAPE 01-MAR-10 1 1 NO
    952 B F A SBT_TAPE 01-MAR-10 1 1 NO
    957 B A A SBT_TAPE 01-MAR-10 1 1 NO
    958 B F A SBT_TAPE 01-MAR-10 1 1 NO
    959 B A A SBT_TAPE 01-MAR-10 1 1 NO
    960 B F A SBT_TAPE 01-MAR-10 1 1 NO
    961 B A A SBT_TAPE 01-MAR-10 1 1 NO
    962 B F A SBT_TAPE 01-MAR-10 1 1 NO
    963 B A A SBT_TAPE 02-MAR-10 1 1 NO
    964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    966 B A A SBT_TAPE 02-MAR-10 1 1 NO
    967 B F A SBT_TAPE 02-MAR-10 1 1 NO
    970 B A A SBT_TAPE 02-MAR-10 1 1 NO
    971 B F A SBT_TAPE 02-MAR-10 1 1 NO
    972 B A A SBT_TAPE 02-MAR-10 1 1 NO
    973 B F A SBT_TAPE 02-MAR-10 1 1 NO
    974 B A A SBT_TAPE 02-MAR-10 1 1 NO
    975 B F A SBT_TAPE 02-MAR-10 1 1 NO
    976 B A A SBT_TAPE 03-MAR-10 1 1 NO
    977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    979 B A A SBT_TAPE 03-MAR-10 1 1 NO
    980 B F A SBT_TAPE 03-MAR-10 1 1 NO
    983 B A A SBT_TAPE 03-MAR-10 1 1 NO
    984 B F A SBT_TAPE 03-MAR-10 1 1 NO
    985 B A A SBT_TAPE 03-MAR-10 1 1 NO
    986 B F A SBT_TAPE 03-MAR-10 1 1 NO
    987 B A A SBT_TAPE 03-MAR-10 1 1 NO
    988 B F A SBT_TAPE 03-MAR-10 1 1 NO
    989 B A A SBT_TAPE 04-MAR-10 1 1 NO
    990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    992 B A A SBT_TAPE 04-MAR-10 1 1 NO
    993 B F A SBT_TAPE 04-MAR-10 1 1 NO
    996 B A A SBT_TAPE 04-MAR-10 1 1 NO
    997 B F A SBT_TAPE 04-MAR-10 1 1 NO
    998 B A A SBT_TAPE 04-MAR-10 1 1 NO
    999 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
    1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
    1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
    1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
    1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
    1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
    1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
    1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
    1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
    1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
    1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
    1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
    1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
    1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
    1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
    1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
    1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
    1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
    1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
    1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
    1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
    1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
    Backup Set 804 20-FEB-10
    Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
    Edited by: user12019850 on 22-Mar-2010 11:03 AM

  • Incrementally updated backup and EMC NMDA

    Hello Everyone,
    I'm kind of a newbie in setting up networker module for oracle, to backup database to tape. We use the oracle's suggested backup strategy to backup DB to Disk first using the incrementally updated backups with recovery set to 3 days (RECOVER COPY OF DATABASE WITH TAG ... UNTIL TIME 'SYSDATE-3') , which helps us to recover DB to any point in time using the backup files in disks vs. going to tape. After backup to disk, we backup recovery area to tape nightly. However, we do want to maintain backup Retention Policy of 1 month. Couple of questions,
    1. If i set RP to recovery window of 31 days in RMAN, then backups don't obsolete at all. this forces me to set RP in networker and they don't recommend setting RP in both RMAN and networker. how is this done generally to obsolete backups from tape as well as rman (catalog in CF) with above strategy. perhaps in this case i should set RP in netwoker and set RP in RMAN to none and rely on crosscheck and delete expired commands to sync with RNAM catalog.
    2. Wondering if nightly backup of recovery area to tape is going to take incremental from previous day and NOT full backup. The reason i ask is, i do not want the tape to do full backup of FRA every day cause full backup datafiles change once in 3 days based on the until time set. is there an option do set in networker to do incremental only or that's the default.
    Thanks in Advance!
    11gR2, 4 Node RAC, Linux, NMDA 1.1, Networker 7.6 sp1

    Loic wrote:
    You do a full backup of the FRA on tape ?No, I do a full backup of the database on tape. Using RMAN together with Veritas NetBackup.
    I mean if you use incremental updated backup it'll not work on tape... Because the level 0 backup that will be updated with the backup of the day after will be on tape and will not be updated.The incrementally updated backup is in the FRA only, on disk (both the image copy and the following backup sets that are used for recovery of the image copy). Never gets written to tape or updated on tape.
    Why don't you use then normal incremental backup ? That will have no problem with the tape backup even if level0, or level1,2 becomes reclaimable... ?I think I do :-)
    Maybe:
    To keep that you can put the redundancy to 2 out of 1 copy. Like this even with one copy on disk and tape it'll say keep the 2 copies.
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;I'll think about that.

  • INCREMENTAL MERGE BACKUP & RECOVERY

    INCREMENTAL MERGE BACKUP & RECOVERY
    =====================================
    1) 개요
    RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
    즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
    물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
    2) 장점
    - Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
    - Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
    3) Syntax
    - Backup
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
    * 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
    위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
    RMAN> Delete Obsolete;
    위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
    -Recovery
    RMAN> switch database to copy;
    문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
    4) Retention Policy에 따른 Syntax 변화
    * 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
    하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
    - Recovery Window of 2
    Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
    왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
    - Redundancy 2 이상
    Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
    DAY 1)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
    DAY 2)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
    DAY 3)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
    DAY 4)
    RMAN> Delete Obsolete;
    - 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
    RMAN> Delete Obsolete redundancy 1
    - 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
    Reference:
    Article-ID: Note 351455.1
    Title: Oracle Suggested Strategy & Backup Retention
    Article-ID: Note 303861.1
    Title: Incrementally Updated Backup In 10G
    글 수정:
    hunlee

    I would always include an archivelog backup:
    ... with tag 'fullbackup’ database plus archivelog delete all input;
    And at the end:
    delete obsolete noprompt;
    That delete incrmental backups already applied to the basic image copies.
    Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
    recover
    copy of database
    with tag 'fullbackup until time 'sysdate-11';
    This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
    Werner

  • Error using rman with cumulative backup

    Hi,
    Can anyone help?
    Current system configuration : Oracle 8.0.4 & Veritas Netbackup.
    Encounter error when allocate 2 channel for cumulative backup using rman. Using a single channel works fine.
    RMAN-08010: channel t1: including datafile 1 in backupset
    RMAN-08008: channel t2: starting datafile backupset
    RMAN-08502: set_count=152 set_stamp=432319182
    RMAN-08010: channel t2: including datafile 7 in backupset
    RMAN-08010: channel t2: including datafile 20 in backupset
    RMAN-08010: channel t2: including datafile 13 in backupset
    RMAN-08010: channel t2: including datafile 15 in backupset
    RMAN-08010: channel t2: including datafile 16 in backupset
    RMAN-08011: channel t1: including current controlfile in backupset
    RMAN-00569: ================error message stack follows================
    RMAN-03007: retryable error occurred during execution of command: backup
    RMAN-07004: unhandled exception during command execution on channel t2
    RMAN-10032: unhandled exception during execution of job step 2: ORA-06512: at li
    ne 153
    RMAN-10035: exception raised in RPC: ORA-19624: operation failed, retry possible
    ORA-27015: skgfcls: failed to close the file
    Additional information: 7023
    ORA-19502: write error on file "bk_152_1_432319182", blockno 3713 (blocksize=512
    ORA-27010: skgfwrt: write to file failed
    Additional information: 7043
    ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 408
    RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE
    ATE
    Thanks in advance
    null

    Hi,
    first of all you must have all the archivelogs since you want to recover your table from the previous backups.
    anyways if you want to recover your table then you need to perform incomplete recovery to the point where you loss the table for that you need to restore and recover your database.you likely to loose all the transcation which occurs to the point where you you loose your table.
    thanks..

  • Does SAP support incremental/delta backups?  if so which note describes it

    I'm just about to test incremental/delta backups on udb 9.5 fp1.  Now to my question:
    Does SAP support incrmental/delta backups?
    Is there a note, I couldnt get a hit on OSS
    Are there any gotcha's?  such as do I need to move read only tables to a new talbespace?
    Any info on this is greatly appreciated.
    Anke

    Hi Anke,
    You can specify whether you want to perform a full, incremental or incremental delta backup and the frequency via DB13 or the planning calender in DBACOCKPIT.
    SAP Note 1269697 DB6: Backup Performance
    should be of use to you and please also see our administration guide available at our main page
    https://www.sdn.sap.com/irj/sdn/db6 under Administration. Specifically check the guide
    "Data Recovery and High Availability Guide and Reference" mentioned in Chapter 8.3.5 Advanced Backup Techniques
    There is not a specific SAP note relating to incremental/delta backups but they can be scheduled via DB13 and so, they are supported.
    Regards,
    Paul

  • Incremental RMAN Backup to tape.

    Hi,
    We have 2.2 TByte Oracle Dataware House. At weekends, we would like to take inceremental level 0 backup to tape and then incemental level 1 to disk daily.
    So that we expect to reduce disk space for backup. We also handle the cover risk of direct path load by mains of incremental level backup.
    But, I would like to know that, taking incremental level 0 to tape causes performance problems. Rman try to discover changes between the incemental level 0 on the tape and incemental level 1 on the disk.
    Should we take both incremental level 0 and incremental level 1 to disk or tape?
    I need your recomendations.
    Thank you.

    Thank you Satish Kandi for your reply,
    As far as understand accourding to document that you refer,
    if we configure well adjustment for channel of disk and tape io buffers,
    and multiplexing, then we can take backup incemental level 0 to tape.
    We don't want to use encryption and compression in order not to consume CPU resources.
    In fact, we should try and obsorve the performance.
    Thank you.

  • Differential Incremental Backup or Incrementally Updated Backup?

    DB Version:11g
    DB Size:450Gb
    DB type: OLTP (storing retail warehouse transactions)
    To implement a proper backup strategy, we are currently weighing the Pros and Cons of Differential Incremental Backup and Incrementally Updated Backup.
    I understand that , for Incrementally Updated Backup , the level 0 backup must be stored in FRA. We don't want to configure FRA as of now.
    Which backup strategy would you choose for a similair environment?

    I don't think that 11g RMAN level 0 backup need to use FRA: can you provide us the link to Oracle doc ?
    When designing your backup strategy you need to define:
    RTO: recovery time objective
    RPO: recovery point objective.
    See http://download.oracle.com/docs/cd/B19306_01/server.102/b14210/hadesign.htm
    To meet a low RTO objective, you may need to use incrementally updated backup because it should be faster to recover from incrementally updated backup compared to differential incremental backup.

  • Incrementally Updated Backups -- do you Backup to TAPE ?

    Incrementally Updated Backups on disk provide
    a. only a single image of the database
    b. as of only a particular point in time (the last incremental update)
    c. no protection against disk/storage failure as the backups are on the same server as the database
    Your Incrementally Updated Backups should go to Tape or to another Disk Area on another server or Virtual Tape Library frequently.
    You may find the need to "restore and recover the database as of 3 days ago OR as of the last critical processing date" which cannot be done if you incrementally update your backup every day.
    A backup on disk doesn't protect you from disk failure.
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

    Look in the FAQ for SuperDuper at: <http://www.shirt-pocket.com/forums/showthread.php?t=3942&highlight=time+capsul e>
    where you'll find a discussion of what you can do.

  • Incremental Hot backup question

    This question originated from a different post of mine, but is somewhat different so I'm starting it up as a separate topic.
    Each night we do an incremental hot backup around 4am. Yesterday I dropped a tablespace successfully and removed the original datafile along with it. Autobackup backed up the control file before and after the drop. Then when the incremental backups ran last night at 4am everything went just fine.
    So up to this point we're all good.
    However, in the flash recovery area where it writes the backups (backupsets, datafiles, etc) it still has a file for that tablespace... except that it did not appear to be updated like all the reset were. This is fine, but that file is taking up space on the box and the unix backup script that copies everything to a separate box still picks it up (that script copies everything.. and the author of the code doesn't want to hard code any names)
    Can I just remove this file without causing the backup to be upset? Or do I need to do something else to accomplish this goal? And if so, what (still a newbie so be specific)?
    Thanks in advance.

    The first thing you need to do is to provide a complementary crystal ball in order to be able to guess nasty little details, like the contents of that script.
    Even 'incremental hot backup' is an ambiguous term. One would expect a RMAN backup, but as you didn't use various RMAN commands to establish all of your files have been backed up, and you talk about 'backupsets' and seem to discuss a standalone datafile: The only thing I see is lots of fog, and the need to tear the information out of you.
    No business for volunteers.
    Sybrand Bakker
    Senior Oracle DBA
    Experts: those who did read documentation.

  • Sybase cumulative backup vs traditional log backup

    In ASE 15.7 SP100 or higher versions, cumulative backups are supported. My question is, can both cumulative backup and log backup run at the same time for a database?
    For example, say, at time t1, we have a completed full backup (full1) of database foo, and
    at time t2, we have the first log backup completed, log1.
    Now, a cumulative backup is running, and another log backup (log2) starts, and finishes at time t3 while the cumulative backup is still running.
    The cumulative backup (cml1) finishes at time t4.
    Another log backup (log3) finishes at time t5.
    Is it a valid scenario (to let log2 and cml1 run at the same time), or does an application (which performs Sybase backups using 3rd party API) need to prevent such concurrent cumulative and log backups?
    If it is valid to run both concurrently (does not result in data corruption), then
    to restore the database up to a time between t2 and t3, we will use full1 + log1 + log2 upto the target time.
    to restore the database up to a time between t4 and t5, we will use full1 + cml1 + log3 upto the target time.
    Please correct me if I am wrong.
    Thanks,
    Ali

    Dear Mr Razib,
    full dump and transaction log dump
    full, cumulative dump and transaction log dump
    Both of these approaches are ok and will allow you to restore a database including rollforward of transaction to the desired point in time. (cumulative dumps only will not work of course, you always need a full dump as a starting point). These backup strategies are suitable for a production system.
    Wheras these backup strategies :
    full dump and cumulative dump
    multiple full dumps
    are ok and supported , too, but it will not allow you to restore a database to any desired point in time. The point of recovery will in any case be the time of the last full or cumulative dump.
    Taking only database dumps (full or cumulative) is propbaly not suitable for production systems. But this is a decision the system owner has to take.
    With kind regards
    Tilman Model-Bosch

  • Is it possible to take incremental logical backups via EXPDP in Oracle 10g

    Guys,
    I am curious that can EXPDP be used to take the incremental logical backups. If so then please let me know how it is possible.
    Regards
    Asif

    There is no incremental specification clause like the one in the export command (INCTYPE). If you ever used the export incremental option, IMO it was not actually an incremental export, it was just enough for a table to change one row to consider the complete Table to be exported on the next exp execution. Not quite a practical approach, overall considering that regularly the more sized tables are those that frequently change.
    ~ Madrid

  • Concept about Incremental Updated backup

    I am going through Backup portion of Oracle. However, I am not able to understand the concept about the incremental Updated backups, its advantages and disadvantages.
    Can anyone here help me out to get my concept clear.
    Thanks in advance .

    916438 wrote:
    I am going through Backup portion of Oracle. However, I am not able to understand the concept about the incremental Updated backups, its advantages and disadvantages.
    Can anyone here help me out to get my concept clear.
    Thanks in advance .http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta2011.htm#RCMRF111

  • Create Incremental Full Backup

    Hey, I thought I created an incremental full backup with attached rman script.
    But at the point of restoring the database it comes up, that I just have an incremental backup of the source database.
    Whats wrong in my configuration ? I like to have a daily full backup of the database where just the changes to the full backup are backed up. But the backupfile should always be a full backup.
    I am using 10gR2 Standard Edition
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/app/control_%F';
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/app/LEVEL0_%u_%T';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/10gR2/db_1/dbs/snapcf_db01.f'; # default
    # Database RAC Logswitch
    sql 'alter system archive log current';
    # Fullbackup Database - Perform incremental level 0 backup
    run {
    BACKUP incremental level 0 format '/backup/app/%d_Level0_%T_%U' database PLUS ARCHIVELOG format '/backup/app/%d_A
    rchivelog_%T_%U';
    }

    An Incremental Backup is a fresh backup of all the changes that have occurred in the database since the last backup.
    Thus, a Level 1 Incremental Backup is a smaller backup than the preceding Level 0 Backup.
    However, when you say :
    I like to have a daily full backup of the database where just the changes to the full backup are backed up. But the backupfile should always be a full backup.You seem to want an Incrementally Updated Backup. That is a backup strategy where your Backup itself is updated.
    I am not sure if this is available in the Standard Edition.
    Here's documentation on Incrementally Updated Backups : at 4.4.3 Incrementally Updated Backups: Rolling Forward Image Copy Backups
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref408
    While this is the "normal" Incremental Backups : at 4.4 RMAN Incremental Backups
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref383
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

Maybe you are looking for

  • URGENT ::: How to add UserName Token to SOAP Message Header.

    Hi, I created a webservice client using CLIENTGEN utility of weblogic from the WSDL file. When I am trying to call a webservice which is hosted on TOMCAT server, I am getting the following exception:: 5/12/2008 06:09:02 com.sun.xml.wss.impl.filter.Du

  • Multi Language- Picklist fields are displayed only one language for Reports

    Hi! I am working on Siebel On Demand with Multi Language (English and Spanish) and it works well for web interface, the automatic translation for picklist works properly. However when I create any report (with any Record Type) the fields setup with p

  • Where is this $%!*& libXinerama.so.1 ?

    Hey ! I got problem running KDE. For exemple, when I start konqueror from wmaker it tell me : [nc@amaroli nc]$ konqueror konqueror: error while loading shared libraries: libXinerama.so.1: cannot open shared object file: No such file or directory [nc@

  • Sampel XPRESS code to call Lockinfo

    Does anyone have a piece of sample XPRESS code to check for locks and the user locking the object on a user or configuration object? I've tried this several ways and am just doing something wrong. Any help would be appreciated. Thanks.

  • Updating Metadata with a sidecar.xml file...

    ... forces the app to be redownloaded again in ACV even if we have not made any modification in the articles. Why modifying the sidecar.xml file creates this unnecessary and time consuming process ?