If there were an easy way to define the "perfect" backup and recovery solution don't you think it would be the default option in Oracle?
The reality is every database has potentially different B&R requirements, which means standardizing on one method throughout your company can be a gross oversimplification and therefore compromise your recovery. That's not to say you shouldn't. I just mean you have to know the consequences.
If you want something simple and consistent, my starting point would be:
- All databases in archivelog mode.
- All databases use block change tracking. http://www.oracle-base.com/articles/10g ... al_backups
- All databases use incrementally updated backups. http://www.oracle-base.com/articles/10g ... ed_backups
- Pick a recovery window (like 7 days) and apply the incremental backups to the image copies keeping them at the right age to allow for your recovery window (like 7 days old).
- After the first image copy backup, you will never need to do a full backup again. Just do incrementals and apply them to the backup image copies.
That is about as simple as you can make things, while keeping the backups efficient and quick.
Like I said, standardizing can be an issue, so don't follow anyones advice without using your brain!