I'd suggest you discuss that with your database ppl if you have them but you can read here in really simple way what cluster puts on the table:
An Introduction to SQL Server Clustering
One very important aspect of clustering that often gets overlooked is that it is not a complete backup system for your applications. It is only one part of a multi-part strategy required to ensure minimum downtime and 100% recoverability.
The main benefits that clustering provides is the ability to recover from failed server hardware (excluding the shared disk) and failed software, such as failed services or a server lockup. It is not designed to protect data, to protect against a shared disk array from failing, to prevent hack attacks, to protect against network failure, or to prevent SQL Server from other potential disasters, such as power outages or acts of God.
Clustering is just one part of an entire strategy needed to help reduce application downtime. You will also need to purchase a shared disk array that offers redundancy, make tape backups, put the server behind a firewall, make sure your network connections have redundancy, use battery backup, and locate the server in a secure facility, among many other steps you can take. So donxxx8217;t think that clustering is all you need for creating a highly available SQL Server. Clustering is just one part and database mirroring is another.
I want to deploy BES COnfiguration Database Mirroring in Prod
