| RMAN obsolete backups not obsolete? [message #452342] |
Wed, 21 April 2010 07:49  |
WJKovacs
Messages: 9
Registered: April 2010
|
Junior Member |
|
|
I'm running Oracle 10.2.0.4, using RMAN to backup my databases (redundancy set to 1 full database copy as the backup files are moved to tape daily through 3rd part tool) and I have flashback enabled with a retention of 12 hours (although in OEM it indicates the Flashback Time is more than 38 hours based on current date and time and the maximum flash back date and time).
Since enabling flashback, I've noticed that when I run a report obsolete command in RMAN it returns something like the following:
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 1653 21-APR-2010 01:07:34
Backup Piece 1653 21-APR-2010 01:07:34 /global/dev/backup/flash_recovery_area/MPID/backupset/2010_04_21/o1_mf_annnn_BACKUP_MPID_000007_0_5wwwqdjv_.bkp
If I then list the backup I see that the backup file in question is an archive log backup:
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ --------------------
1653 13.99M DISK 00:00:19 21-APR-2010 01:07:34
BP Key: 1653 Status: AVAILABLE Compressed: YES Tag: BACKUP_MPID_000007_042110010005
Piece Name: /global/dev/backup/flash_recovery_area/MPID/backupset/2010_04_21/o1_mf_annnn_BACKUP_MPID_000007_0_5wwwqdjv_.bkp
List of Archived Logs in backup set 1653
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- -------------------- ---------- ---------
1 50955 172277149 20-APR-2010 01:06:22 172278743 20-APR-2010 01:21:20
1 50956 172278743 20-APR-2010 01:21:20 172279590 20-APR-2010 01:36:23
1 50957 172279590 20-APR-2010 01:36:23 172280224 20-APR-2010 01:51:24
------------------MORE ARCHIVE LOGS FOLLOW------------------
Now, I know I don't need these files for my recovery as the database backup occurred after these archive files were generated (backup scheduled to run 01:00, duration of 5 minutes and ass part of the backup all archive logs are removed from disk after they have been backed up so the files listed above were archive files created after the backup on April 20th). BUT I never had these show as obsolete until I enabled flashback. On my other databases where I have the same policies and backup jobs but I don't have flashback enabled, I don't see any obsolete backup files.
Is it the case then, that the information in the archive logs is also in the flashback files and therefore RMAN sees the archive log backups as obsolete based on a 1 copy redundancy policy (the other copy being date in the flashback files)? As well, if I run the report later in the day, more archive log backup files are shown as redundant further leading me to believe there is a connection between the obsolete report and flashback.
Any insight would be appreciated. Thanks.
|
|
|
|
| Re: RMAN obsolete backups not obsolete? [message #452362 is a reply to message #452342] |
Wed, 21 April 2010 12:00  |
WJKovacs
Messages: 9
Registered: April 2010
|
Junior Member |
|
|
As I mentioned earlier, later in the day I have another "obsolete" file:
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 1652 21-APR-2010 01:07:00
Backup Piece 1652 21-APR-2010 01:07:00 /global/dev/backup/flash_recovery_area/MPID/backupset/2010_04_21/o1_mf_annnn_BACKUP_MPID_000007_0_5wwwot9m_.bkp
Backup Set 1653 21-APR-2010 01:07:34
Backup Piece 1653 21-APR-2010 01:07:34 /global/dev/backup/flash_recovery_area/MPID/backupset/2010_04_21/o1_mf_annnn_BACKUP_MPID_000007_0_5wwwqdjv_.bkp
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
