My impression was that backups done via Netapp's snap manager for sql could be done very often, very fast and that for databases in full recovery, its an either or proposition -- you can't back these databases up with native sql because you'll break the netapp log chain.

One thing we haven't tested is the IO freeze time. One of our data files in in line to be split up, but currently that one is 1.1TB. You also have to make sure backups run with sql snap manager don't step on eachother -- can't have a log backup overlap a full backup etc.

Add in the possibility that the database might be migrated off of Netapp in a year or two and its quite an investment to go that route now.