I have been assigned a project where sql server is running on a single server with single raid 1 volume. This setup has worked fine until hardware failure resulted in about a day worth of downtime for small business. There is no strict budget for this project, but don't want to go too crazy.
First option I looked at is SQL Server Cluster with two nodes. Hardware is already available and I have tested the setup in test environment with a great success. However, that still leaves me with storage as a single possible point of failure.
What would be a good option to go along with sql server clustering failover?
Software: Windows Server 2012 and Microsoft SQL Server 2012
Note: I do understand that besides storage failure there is also a possibility of network card or switch failure that would cause as much downtime, however, just for the sake of it let's assume it is taken care of.
Always on would let you have separate storage for each node. (http://msdn.microsoft.com/en-us/library/ff877884(v=sql.110).aspx) However this gets trickier in win10 with the new storage HA features.
You haven't mentioned what you're using for storage, but if you're using a SAN you could also use SAN replication with your SQL cluster.
If you don't already have the various pieces for that, however, Always On might be a better option. (Like Jim B suggested.)