Hi Nicolai,
Really not a big fan of FILESPERSET=1 here, as we would get hundreds of images per database backup, and this leads to greater catalog growth. We prefer to have a few larger streams depending on database size.
Our dedupe rates are still in the mid-high 90% bracket for the databases themselves. Archive logs dont dedupe well so they go to advanced disk, meaning we dont chew up lots of valuable dedupe space.
Currently looking at revamping how the archive log backups are triggered, as we have too many small backups, and want fewer larger backups.
Working with DBA's to start to use thresholds on the archive log file systems, including logic for ASM file systems
Thanks for your comments tho :-)