Re: FRA

I guess I am a pretty big fan of using the FRA in 10.2 and 11.x for backups. Configured correctly, it eliminates the need to write scripts to manage and delete old archivelogs and backups, since the oldest files get deleted to make space for new files when the FRA reaches 100%. With backup optimization on, the subsequent backup from disk to tape via a MML is greatly reduced in size. Overall, it replaces a lot of home-grown scripting and management we have all developed over the years. You don't have to mark anything obsolete or delete via RMAN if it is configured correctly. Set up right, it is "Self-managing."
My biggest complaint about the FRA is that you cannot archive directly into compressed backupsets. So if you use the FRA as your log_archive_dest_n, the archivelogs can take up comparatively more space than database backups. 

Regards,

Jeremiah Wilton
Blue Gecko, Inc.
http://www.bluegecko.net

On Dec 11, 2009, at 7:23 AM, Allen, Brandon wrote:
Jay, I would say there isn't much point in using an FRA unless you want to use it for Flashback Database, or if you want to use it to segregate backup/archivelog space between multiple databases running on the same file system, or you want to use the "backup recovery area" command in order to manage subsequent backups from disk to tape.
If you haven't already, I'd suggest searching MOS for "flash recovery area" and reading some of the articles on "benefits" and managing space issues, (e.g. 315098.1). Make sure you understand the part about not just clearing files at the OS level - you have to delete them through RMAN, or crosscheck them after deleting at the OS, in order to make the space available for other files again. 

--
http://www.freelists.org/webpage/oracle-l

Other related posts: