I was going to suggest setting up a database mirror. This would allow you to failover to the mirrored database with minimum downtime. If the SAN version of the DB is on the same SQL instance as the primary version then the SAN version would need a different DB name. After failover you would have to break the mirroring and rename the database to the original version.

However, having seen the suggestion to use log shipping I think that probably needs the lowest skill level to get it working. As already mentioned it will need some down-time at point of cutover, but you should be looking at less than 5 minutes.

I would only use replication for this if I wanted to make things really complicated...