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

Similar Messages

  • 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

  • Retention Policy to delete both backup sets and archivelogs automatically

    I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
    Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
    Thanks.

    One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
    Werner

  • Reg retention policy in Windows server Backup

     
    Please let me know how long time the backups will be maintained in Windows server Backup.
    Is there any place where I can go and modify the retention policy?

    The statements
    "If the backup storage location is full, Windows Server Backup automatically deletes the oldest backup"
    and
    "If you do not delete the corresponding shadow copy, the backup sets will be always reserved."
    are contradictory.  As explained in the "Overview" section of the source you linked, the first statement is correct.  It is not necessary that the server admin take any action to delete shadow copies in order to implement a retention
    policy.  When the backup destination drive gets full, WSB "automatically deletes the oldest backup version" (http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx)
    This all said, this behavior and the source cited are for Windows Server 2008. 
    The automatic disk space management behavior seems to have changed in Server 2012 (for example see this link: http://technet.microsoft.com/en-us/library/jj614621.aspx).  Unfortunately I've not been able to determine
    specifically how it is different.

  • Retention policy for archivelogs in the flash recovery area

    I am using the flash recovery area for all my backup files (archive logs, data and control files). I want to use the redundancy retention policy because it is easy to calculate the space requirement. However, I am not clear how the retention policy applies to archive logs.
    Say I set the retention policy to be "keeping 3 backups". How does it affect the archive logs? Will archive logs in the flash recovery area be deleted automatically or I need to do it manually. If they are deleted automatically just like dataset files, what is the "retention policy" for them? I do not have a tape device so all archive logs are going to be stay in disk.
    Thanks.

    I am using the flash recovery area for all my backup
    files (archive logs, data and control files). I want
    to use the redundancy retention policy because it is
    easy to calculate the space requirement. However, I
    am not clear how the retention policy applies to
    archive logs.
    RMAN> show retention policy
    2> ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups found
    RMAN> list backup
    2> ;
    RMAN>AS documentation says
    "Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
    First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
    log backups that are older than the oldest datafile or control file backup that must be retained."
    Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
    consider it here that i am getting archived before any taking backup i.e backup database in order to make
    archive older then the oldest datafile.
    SQL> show parameter control_file_record_keep_time
    NAME                                 TYPE        VALUE
    control_file_record_keep_time        integer     7
    SQL> create table a1 as select * from all_objects
      2  /
    Table created.
    SQL> create table a2 as select * from all_objects
      2  /
    Table created.
    C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    03/17/2008  03:44 PM    <DIR>          .
    03/17/2008  03:44 PM    <DIR>          ..
    03/17/2008  03:44 PM         9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
                   1 File(s)      9,750,528 bytes
                   2 Dir(s)  62,714,875,904 bytes free
    Now i take backup
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups found
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
    does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
    be useful for recovery process.
    now back to pavillion
    RMAN> delete obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted archive log
    archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
    G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
    Deleted 1 objects
    RMAN> delete backup
    2> ;
    using channel ORA_DISK_1
    RMAN> list backup
    2> ;
    C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
    03_17
    03/17/2008  03:59 PM    <DIR>          .
    03/17/2008  03:59 PM    <DIR>          ..
                   0 File(s)              0 bytes
                   2 Dir(s)  62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
    then the oldest datafile backup.
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
    SQL> create table a3 as select * from all_objects
      2  /
    Table created.
    SQL> create table a4 as select * from all_objects
      2  /
    Table created.
    C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
    03_17
    03/17/2008  04:09 PM    <DIR>          .
    03/17/2008  04:09 PM    <DIR>          ..
    03/17/2008  04:09 PM         9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
                   1 File(s)      9,751,552 bytes
                   2 Dir(s)  62,563,205,120 bytes free
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting compressed full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
    is not older then oldest datafile backup.
    But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
    backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
    retetnion policy from the period of 2.
    RMAN> backup database
    2> ;
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           240    17-MAR-08
      Backup Piece       231    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
    KP
    Backup Set           241    17-MAR-08
      Backup Piece       232    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
    KP
    Archive Log          403    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram

  • Retention Policy for Tasks

    I am helping a client with their Exchange Online archiving policies.  Everything was working well until we realized that Tasks were getting archived according the default archiving policy.  I do not see the option to create a Default Retention
    Policy for Tasks.  It is not listed in the Default Folders drop down menu.  Another article indicated that they had the same issue and had to set the Default Policy to never archive and then setup individual policies for folders they did want archive
    in order to protect the Tasks folder.  However, I only seem to able to create "Archiving Policies" as a personal option.  I do not get the option to create an Archiving policy default folders.  The only option I see for Default folders
    is "Delete and Allow Recovery" or "Permanently Delete".  Move to Archive is not listed.   Please Help.

    The Default tag applies to Tasks folder as well. If you want to prevent items in that folder from being moved to the Archive mailbox, create a new Personal tag with the move to archive option, and apply it to the folder. As the retention options for the
    Tasks folder are not exposed to the end user either via Outlook or OWA, you will have to use EWS based script.
    You can refer to this article for more info:
    http://blogs.technet.com/b/exchange/archive/2013/05/20/using-exchange-web-services-to-apply-a-personal-tag-to-a-custom-folder.aspx

  • RMAN RETENTION POLICY FOR ORACLE8I

    Dear all,
    How to config RETENTION POLICY for oracle8i(CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;), same 9i ?
    Thanks for advance !
    Chara

    In ORACLE 8i, there are NO stored RMAN parameters (I believe, 9i was the first version to add this feature).
    Instead, in ORACLE 8i you had to specify all channel parameters, formats etc in a run block ... So, the good news is, in ORACLE 8i these parameters should be already "hardcoded" in the RMAN scripts ... in other words, nothing to transfer on a database level ...

  • 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 specific backupset

    Hi,
    Actually I am envolved in a Proof Of Concept for Exadata. My customer wants to set a specific rentention for one backupset. These are the steps followed and the problem:
    1. Perform a "backup as backupset" for database to disk.
    2. Perform a "backup backupset" to tape for the backup of step 1.
    3. Change the retention policy only for the backup of step 2 and set it to be kept until sysdate+x days.
    Does anyone know how can be this done?
    Best regards.

    You will need to create two different backup one to device type DISK with default retention and another backup to device type SBT_TAPE with specific retention.
    The SAME backup (backupset) cannot have two different retention (even if it's a copy). The copy of backupset belongs to a Backup which already has it own retention.
    see this example:
    RMAN> backup current controlfile ;
    Starting backup at 17-OCT-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=10 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ORA_DISK_1: starting piece 1 at 17-OCT-12
    channel ORA_DISK_1: finished piece 1 at 17-OCT-12
    piece handle=/u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp tag=TAG20121017T145951 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
    Finished backup at 17-OCT-12
    RMAN> backup backupset from tag TAG20121017T145951 ;
    Starting backup at 17-OCT-12
    allocated channel: ORA_SBT_TAPE_1
    channel ORA_SBT_TAPE_1: SID=10 device type=SBT_TAPE
    channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
    channel ORA_SBT_TAPE_1: input backup set: count=14735, stamp=796921191, piece=1
    channel ORA_SBT_TAPE_1: starting piece 1 at 17-OCT-12
    channel ORA_SBT_TAPE_1: backup piece /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp
    piece handle=BKP_CONTROL_ORCL_14735_1_20121017_2 comment=API Version 2.0,MMS Version 5.5.1.0
    channel ORA_SBT_TAPE_1: finished piece 1 at 17-OCT-12
    channel ORA_SBT_TAPE_1: backup piece complete, elapsed time: 00:00:04
    Finished backup at 17-OCT-12
    RMAN> list backup;
    BS Key  Type LV Size
    14667   Full    1.11M
      Control File Included: Ckp SCN: 142367578    Ckp time: 17-OCT-12
      Backup Set Copy #1 of backup set 14667
      Device Type Elapsed Time Completion Time Compressed Tag
      DISK        00:00:02     17-OCT-12       YES        TAG20121017T145951
        List of Backup Pieces for backup set 14667 Copy #1
        BP Key  Pc# Status      Piece Name
        14667   1   AVAILABLE   /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp
      Backup Set Copy #2 of backup set 14667
      Device Type Elapsed Time Completion Time Compressed Tag
      SBT_TAPE    00:00:02     17-OCT-12       YES        TAG20121017T145951
        List of Backup Pieces for backup set 14667 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        14668   1   AVAILABLE   44531                   BKP_CONTROL_ORCL_14735_1_20121017_2
    RMAN> change backuppiece 14668 keep forever logs;
    using channel ORA_DISK_1
    using channel ORA_SBT_TAPE_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of KEEP command at 10/17/2012 15:02:24
    RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECEIn example above the BACKUPSET 14667 have two BACKUPPIECE (14667,14668) if you change retention of BACKUPSET 14667 you will change retention of both BACKUPPIECE.
    I don't recommend do this ,but is a poor option:
    RMAN> delete backuppiece 14667;
    using channel ORA_DISK_1
    using channel ORA_SBT_TAPE_1
    List of Backup Pieces
    BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
    14667   14667   1   1   AVAILABLE   DISK        /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted backup piece
    backup piece handle=/u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp RECID=14667 STAMP=796921192
    Deleted 1 objects
    RMAN> list backup;
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    14667   Full    1.11M      SBT_TAPE    00:00:02     17-OCT-12
            BP Key: 14668   Status: AVAILABLE  Compressed: YES  Tag: TAG20121017T145951
            Handle: BKP_CONTROL_ORCL_14735_1_20121017_2   Media: 44531
      Control File Included: Ckp SCN: 142367578    Ckp time: 17-OCT-12
    RMAN> change backupset 14667   keep forever;
    using channel ORA_DISK_1
    using channel ORA_SBT_TAPE_1
    keep attributes for the backup are changed
    backup will never be obsolete
    backup set key=14667   RECID=14667 STAMP=796921193
    RMAN > list backup;
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    14667    Full    1.11M      SBT_TAPE    00:00:02     17-OCT-12
            BP Key: 14667   Status: AVAILABLE  Compressed: YES  Tag: TAG20121017T145951
            Handle: BKP_CONTROL_ORCL_14735_1_20121017_2   Media: 44531
            Keep: BACKUP_LOGS        Until: FOREVER
      Control File Included: Ckp SCN: 142367578    Ckp time: 17-OCT-12Edited by: Levi Pereira on Oct 17, 2012 4:02 PM

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

  • April 2015 Pricing change for Azure Online Backup questions

    The webpage for Azure Online Backup pricing indicates that for protected devices over 5GB/month there will be a new model (i.e. free workloads are still free).
    It indicates that its $10 per instance protected in 500GB blocks + storage.
    The functional thing about azure online backup was the predicable model - As long as I monitored storage I knew what I would be paying since all other costs were included. The "+ storage" doesn't really give me any idea what will be billed.
    Now the question is how complex is it?
    What is the storage type? Blob? Page Blob/Disk?
    What is the geo status? LRS, ZRS? GRS?
    Do I pay for ingress, egress? Express-Route traffic?
    Is there storage transaction fees?
    The pricing web page really needs to provide a more complete set of info that what is currently there.
    thanks!
    -N 
    neilgo

    we are in the process of updating the pricing page with a list of FAQs that should happen by next week. Please bear with us.
    Shreesh

  • Best method for incremental offsite backups?

    I currently have multiple Macs and a Windows PC running XP.  I also have a 1TB Time Capsule, so all the Macs are backed up via Time Machine.  However, I want to have offsite backups as well, so I purchased 2 matching Seagate GoFlex 3TB drives.  My plan was to backup up verything, then have one drive offsite and another at home away from the computers.
    However, it takes a very long time to move the drives from machine to machine, backing up all the files.  I would like to find a good solution to do an initial backup, then do incremental backups after that.  It would also be great if I could hook the drives into the network, so I didn't have to move them around to the various computers.
    So, I have a few questions:
    Can I hook up the external drive to the Time Capsule via the USB port, point Time Machine to the external drive and do a backup that way?  If so, will it screw up my regular Time Machine backup to the Time Capsule?  Will it just do an incremental the next time I hook up the external drive to the Time Capsule?
    If Time Machine is not the answer, is there third party software to do it?
    How do I handle the Windows machine backup?
    Is there a better option than doing incrementals?
    Keep in mind--I've tried cloud solutions like Carbonite and Mozy, and neither worked for me based on the large multimedia files I use.  I could never upload fast enough to make it practical.  That's why I went to external drives for offsite backup.   I also don't want to leave the external drives hooked up--just hook them up long enough to do the backups.
    Any suggestions would be appreciated.

    I would suggest CrashPlan.  They offer a mode that allows you to use your own computers (or even your own local devices) as the backup destination.  CrashPlan runs on Windows and Macs.
    I currently use CrashPlan to backup my laptop to a in house Mac mini.  I think that as long as your Macs and PCs can see the Seagate GoFlex 3TB drives, either attached to the TimeCapsule, or attached to any Mac or PC in the house, then CrashPlan on any device at home should be able to incrementally backup each system.  And if the GoFlex is attached to a system in the house that is running a CrashPlan server, you could even use CrashPlan to backup a laptop while you are away on vacation or business trips.
    You will be using your own local (hopefully faster) home network, which should be much better than the Carbonite and Mozy options which require pushing your data out of the house using your generally much slower up-link broadband connection.
    NOTE:  CrashPlan (again the free option) can specify a computer that you control (yours, or a family member, or friend) can be used as the backup target.
    An alternative for Macs ONLY would be SuperDuper (shareware) and/or Carbon Copy Cloner (donationware), which do very good incremental backups.  Generally both are used with direct attached external disks, and they make bootable clones.  HOWEVER, both of them can be used to backup over the network.  In the case of SuperDuper, you would mount the remote volume and then backup into a .dmg container file.  For Carbon Copy Cloner you can backup over an ssh connection to a directory subtree on a remote system.  I think it should be possible for Carbon Copy Cloner to use a container file (similar to SuperDuper).
    Sorry, but I do not know what backup utilities are good on Windows.
    Finally, you might be able to roll your own using rsync.  In fact Carbon Copy Cloner uses rsync as its copy engine, and the rsync buried in CCC is generally the most up-to-date rsync for Mac OS X.  Not sure if rsync is available for Windows, but if it is, then that might be something to think about.
    Message was edited by: BobHarris

  • RETENTION POLICY in RMAN question

    Is a good practice to set up a RETENTION POLICY for the full backups (level 0) and another RETENTION POLICY for the incremental backups (level 1)? If yes, why and how could I do this ?
    Thanks for your responses,
    Christine.

    It is from the doc
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1007.htm#sthref279
    From the perspective of a retention policy, a datafile backup is a full or level 0 backup of an individual datafile or control file. It does not matter whether the backup is a datafile image copy, a proxy copy, or part of a backup set. For datafile copies and proxy copies, if RMAN determines that the copy or proxy copy is not needed, then the copy or proxy copy can be deleted. For datafile backups in backup sets, RMAN cannot delete the backup set until all of the individual datafile backups within the backup set are obsolete.
    Besides affecting full or level 0 datafile and control file backups, the retention policy affects archived redo logs and level 1 incremental backups. First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived logs and incremental level 1 backups that are not needed to recover the oldest datafile or control file backup that must be retained.

  • Archive Log Backups Retention Policy

    How can I define Retention Policy for archive log backups?

    The question asked and answer you have marked as "Correct answer" is misleading.
    For archived log deletion policy, look below.
    Configuring the RMAN Environment
    For the actual question posted "How can I define Retention Policy for archive log backups?", look below link.
    http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318
    Also, did you start the thread to clear your doubt or test the other forum users?
    Thank you!!

  • 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

Maybe you are looking for

  • [GeForceFX] GeForce FX 5200 TDI128LF - No DVI

    Hello, I just purchased a GeForce FX5200 TDI128LF with DVI out.  I have attached it to my IBM P260 monitor using a DVI cable and when I flip the switch for DVI input on my monitor there is no signal.  I've powered down, re-started, disconnected the V

  • Customer Downpayment

    Hi, The billing document contains two items: The first item invoices the customer for certain per cent of the total order value. The second item displays the down payment amount that has to be off-set but in my process downpayment amount is not refle

  • How to prevent pending task in GP Runtime

    Hi experts, What should I do when I don't a pending task to be in  GP Runtime when the result state is Terminated. Thanks.

  • Stuck in 1X again...

    So suddenly this week, my phone started dropping from 3G to 1X regularly again....seems it disappears for a little while then comes back. Has anyone found an actual FIX for this or is VZW still ignoring it?I've done resets, battery pulls and full on

  • My snap chat app has just started to close down when I open it. WHY?

    snap chat has just stopped working. the app closes down when i open it. why?