Turkbear,
you misunderstand. I'd never be that daft.
What I was alluding to was the fact that RMAN produces backup files (naturally without stopping the db) and also a backup control, spfile and relevant archive logs.
These can be written to disk (obviously) and then with a simple batch file copied away to safe storage. I believe that the software Ken's alluding to is that which plugs in to RMAN and lets it write to a particular vendor's mass storage device (quirks and all) with neither the intervening storage time nor usage.
If your backup piece was say 30 gig, and you only have 20 odd available, your storage requirement would temporarily balloon over all available space pending the copy to NAS followed by deletion of the on-disk backup piece. Also the system has to write all that data twice, once to disk by RMAN, and then disk to NAS by batch file. For a few gig, this is not an issue, but if Ken has some heavyweight backup pieces, it might be enough to justify the vendor's fees.
See what I mean now Turkbear?
Regards
T