• Instead of using Netapp and Snap - you want to implement replication across to the DR site for your image files. This way, all image files are immediately written to the DR site. You would also set it up as bi-directional replication so that any files written on the DR site are replicated across to your production site.

    For the databases, the options I would pursue are SQL Server 2012 Always On clustering. If that is not available and you cannot upgrade yet, then straight database mirroring. If you have to rely on Netapp (or any SAN technology), then you should be looking at the mirroring capabilities on the SAN. With Netapp, you can setup the LUNs supporting the databases with a mirror that can be replicated to your DR site (note: you still have to copy that data across the first time - and copying a compressed backup file for database mirroring will take less time).

    Netapp's (or any SAN's) snap technology is not going to be frequent enough to prevent data loss. Additionally, you have to be concerned about the timing of the database backups and the snap clone - or you could end up with the database having entries referring to image files that do not exist, or image files that do not have an entry in the database.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs