Just to clarify a small thing.
When the manual says "RMAN retains all archived logs" it means also the backups of archive logs, right?
What I intend to do is archive the current log every 30 minutes, backup the archive log and delete it using an rman script.
If I got it right, rman will maintain all backups of archive logs that are needed for recovery of a database backup maintained according to retention policy.
BACKUP as compressed backupset ARCHIVELOG ALL FORMAT 'location/_%U' delete input;
This will backup the archive logs, deletes the archive logs which has been backed up and maintains the "backupset" which contains the archive logs according to the retention policy.
Note: "compressed" key word is used for backup compression to save space.
Hope this is clear to you.
REDUNDANCY specifies how many full or level 0 backups of each data file and control file that RMAN should keep.
Its not specific for the Archive log files. because for the recovey of database you need backup as well as archive.
you can deleted the Archive log files aftet the database backup level 0 or level 1 with the command (delete all input)
and schedule your level 1 backup daily for the best practics.
Hope this help
The question asked and answer you have marked as "Correct answer" is misleading.
For archived log deletion policy, look below.
For the actual question posted "How can I define Retention Policy for archive log backups?", look below link.
Also, did you start the thread to clear your doubt or test the other forum users?
Actually there is a specific setting for what i asked.
OEM --> Availability --> Backup Settings --> Policy --> Archived Redo Log Deletion Policy --> Delete archived redo log files after they have been backed up the specified number of times
I believe that would be a function maintained by OEM to tell it how to generate the actual rman backup commands -- not a configuration of rman itself.
Never confuse a GUI tool with the things that the GUI tool manages. If in doubt about the difference, ask yourself how you would accomplish the task if you didn't have the GUI. And yes, people can manage Oracle databases quite nicely without the GUI.
I believe it's the same as the rman ARCHIVELOG DELETION POLICY and not a function maintained by OEM.
The original question was "How can I define Retention Policy for archive log backups?" (emphasis mine)
ARCHIVELOG DELETION POLICY "does not apply to archived redo log files in backup sets" (CONFIGURE)