Do you truly understand what data recovery means? And what HA means?
SQL HA and DR solution (e.g. mirroring or cluster) is not the only thing you need.
They help to achieve HA/DR but often are combined and not alone.
You have to use a combination of various sql and non-sql software and hardware to achieve given HA and DR goals.
Also, there should be a list of what types of failures you plan to protect from.
E.g. user deleted data by mistake - from that type of failure you can recover from e.g. database snapshot.
From disk failure you can recover from backup, mirror, replication, replicated storage.
Disaster could be for example:
- accidental data deletion (that also makes data unavailable to users)
- partial storage corruption
- storage failure (total)
- server failure (e.g. motherboard)
- network failure
- site failure
- multiple sites failure
You can combine cluster with SAN replication, cluster with replication, various network redundancy solutions, storage redundancy solutions, special security (physical and logical), etc.
Each of which can participate in HA or DR or both.
There are also fine details you should know about each solution component and how that affects availibility and data recovery.
So, to bring that all up together into one simple table with e.g. 20 columns x 20 rows
and fill those 400 fields - if that is what you are asking, you will probably not get it.
Microsoft Certified Master: SQL Server 2008
XDetails Addin - for SQL Developers
blog.sqlxdetails.com - Transaction log myths