Overall Satisfaction with Windows Server Failover Clustering
We have Setup Windows Server Failover Clustering for our SQL Server Always On so that our databases are configured on Failover mode. In case any of our servers failing to respond this service will move our databases from the primary server to the disaster recovery server. Our Information technology department uses it and the user across the organization is not aware of what we have deployed or what is our architecture.
- Failover Priority setting , i.e. High, medium , low.
- online services movement.
- Online data movement across clusters.
- No downtime,
- Easy role movement
- Quorum settings should be improved
- San environment should be improved
- Logging of Cluster events should be improved
- SQL Server Roles deployment
- SQL Server databases on different disks
- Nodes on different Blade servers
- Zero Downtime
- Asynchronous updates
- Roles deployment
SQL Server uses a feature called Failover Clustering and it should be deployed on the Failover Cluster, SQL Server creates its own roles on the failover cluster of windows, and Windows Server failover cluster could be used to failover to the primary and secondary servers using the roles.
Do you think Windows Server Failover Clustering delivers good value for the price?
Yes
Are you happy with Windows Server Failover Clustering's feature set?
Yes
Did Windows Server Failover Clustering live up to sales and marketing promises?
Yes
Did implementation of Windows Server Failover Clustering go as expected?
Yes
Would you buy Windows Server Failover Clustering again?
Yes