Disaster Recovery through cloning drives in sql server 2014 enterprise
Firstly, you need to determine what the acceptable Recovery Point Objective (total data loss) and Recovery Time Objective (time taken to restore the system) is for each database on your production server.
If the amount of data loss your business is willing to accept is less than the interval that your disks are replicated to your DR site then this won't work as a strategy. If it takes longer to clone and provision the disks for your DR server than the RTO, then this solution won't work.
Download Brent Ozar's First Responder Kit, which includes a High Availability and Disaster Recovery worksheet to help you determine and design a suitable DR solution for your databases.
There are many options within SQL Server itself for providing DR capabilities that might be better suited than SAN replication (although that is always an option). Log Shipping, for example, is a simple, low-cost solution that might achieve lower RPO and RTO than hourly SAN replication and can be simpler than having to clone LUNs and attach them to the SQL Server.