{"id":8348,"date":"2014-03-28T06:51:43","date_gmt":"2014-03-28T04:51:43","guid":{"rendered":"\/?page_id=8348"},"modified":"2026-02-17T06:56:47","modified_gmt":"2026-02-17T04:56:47","slug":"shared-nothing-architecture-vs-shared-disk-architecture","status":"publish","type":"page","link":"https:\/\/www.evidian.com\/products\/high-availability-software-for-application-clustering\/shared-nothing-architecture-vs-shared-disk-architecture\/","title":{"rendered":"Shared Nothing vs. Shared Disk Architecture: Choosing the Best HA Cluster"},"content":{"rendered":"
\n
\n\t

Shared Nothing vs. Shared Disk Architecture: Choosing the Best HA Cluster<\/h1>\n

SafeKit SANless Clustering: Benefits of Shared Nothing Architecture over Shared Disk<\/h2>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div><\/div>
\n
\n\t
<\/div>
\n\t\t\t\n\t\t\n\t\t\t\n\t\t\t\ud83e\uddd1 Contact us\t\t<\/span>\n\t\t\t<\/a>\n\t<\/div>\n<\/div><\/div><\/div>
\n\t\t\t\n\t\t\n\t\t\t\n\t\t\t\ud83c\udf81 SafeKit free trial\t\t<\/span>\n\t\t\t<\/a>\n\t<\/div>\n<\/div><\/div><\/div>
\n\t\t\t\n\t\t\n\t\t\t\n\t\t\t\ud83c\udfc5 Free certification\t\t<\/span>\n\t\t\t<\/a>\n\t<\/div>\n<\/div><\/div><\/div>
\n\t\t\t\n\t\t\n\t\t\t\n\t\t\t\ud83d\udcb0 Perpetual license cost\t\t<\/span>\n\t\t\t<\/a>\n\t<\/div>\n<\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/div>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div>
\n
\n\t

Shared nothing architecture vs shared disk architecture for high availability clusters<\/h2>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div>
\n
\n\t

Overview<\/h3>\n

This article explores the pros and cons of shared nothing architecture vs shared disk architecture for high availability clusters. We are looking at hardware constraints, impact on application data organization, recovery time, simplicity of implementation.<\/p>\n

\"Shared<\/p>\n

The following comparative tables explain in detail the difference between shared disk architecture and SafeKit, a software clustering product implementing a shared nothing architecture.<\/p>\n<\/div>\n<\/div><\/div><\/div>

\n
\n\t

What is a shared disk architecture?<\/h3>\n

A shared disk architecture (like with Microsoft failover cluster<\/a>) is based on 2 servers sharing a disk with an automatic application failover in case of hardware of software failures.<\/p>\n

This architecture has hardware constraints: the specific external shared storage, the specific cards to install inside the servers, and the specific switches between the servers and the shared storage.<\/p>\n

A shared disk architecture has a strong impact on the organization of application data. All application data must be localized in the shared disk for a restart after a failover.<\/p>\n

Moreover, on failover, the file system recovery procedure must be executed on the shared disk. This increases the recovery time (RTO).<\/p>\n

Finally, the solution is not easy to configure because skills are required to configure the specific hardware. Additionally, application skills are required to configure application data in the shared disk.<\/p>\n<\/div>\n<\/div><\/div><\/div>

\n
\n\t

What is a shared nothing architecture ?<\/h3>\n

A shared nothing architecture (like with SafeKit<\/a>) is based on 2 servers replicating data in real-time with an automatic application failover in case of hardware of software failures.<\/p>\n

There are two types of data replication: byte level file replication vs block level disk replication<\/a>. We consider here byte level file replication because it has many advantages against block level disk replication.<\/p>\n

The shared nothing architecture has no hardware constraints: the servers can be physical or virtual with any type of disk organization. Real-time file replication (synchronous<\/a> for having 0 data loss) is made through the standard network between servers.<\/p>\n

This architecture has no impact on application data organization. For instance, if an application has its data in the system disk, real-time file replication is working.<\/p>\n

Recovery time (RTO) in the event of a failover is reduced to the application restart time on the secondary server's replicated files.<\/p>\n

Finally, the solution is very simple to configure as only the paths of directories to replicate are configured.<\/p>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div>

\n
\n\t

Pros and cons of shared nothing architecture vs shared disk architecture<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Shared nothing architecture<\/strong><\/p>\n

\"Shared<\/td>\n

Shared disk architecture<\/strong><\/p>\n

\"Shared<\/td>\n<\/tr>\n

Product<\/strong><\/td>\n<\/tr>\n
SafeKit on Windows and Linux<\/a><\/td>\nClustering toolkit for shared disk<\/td>\n<\/tr>\n
Extra hardware<\/strong><\/td>\n<\/tr>\n
No - Use internal disks of servers<\/td>\nYes - Extra cost with a shared bay of disks<\/td>\n<\/tr>\n
Application data organization<\/strong><\/td>\n<\/tr>\n
0 impact on application data organization with SafeKit.<\/p>\n

Just define directories to replicate in real-time<\/a>.<\/p>\n

Even directories inside the system disk can be replicated.<\/td>\n

Impact on application data organization.<\/p>\n

Special configuration of the application to put its data in a shared disk.<\/p>\n

Data in the system disk cannot be recovered.<\/td>\n<\/tr>\n

Complexity of deployment<\/strong><\/td>\n<\/tr>\n
No - install a software on 2 servers<\/td>\nYes - require specific IT skills to configure OS and shared disk<\/td>\n<\/tr>\n
Failover<\/strong><\/td>\n<\/tr>\n
Just restart the application on the second server.<\/td>\nSwitch the shared disk.<\/p>\n

Remount the file system.<\/p>\n

Pass the recovery procedure on the file system.<\/p>\n

And then restart the application.<\/td>\n<\/tr>\n

Disaster revovery<\/strong><\/td>\n<\/tr>\n
Just put the 2 servers in 2 remotes sites connected by an extended LAN.\n<\/td>\nExtra cost with a second bay of disks.<\/p>\n

Specific IT skills to configure mirroring of bays across a SAN.\n<\/td>\n<\/tr>\n

Quorum and split brain<\/strong><\/td>\n<\/tr>\n
Application executed on a single server after a network isolation (split brain).<\/p>\n

Coherency of data after a split brain.<\/p>\n

No need for a third machine or a quorum disk or a special heartbeat line for split brain.<\/p>\n

More information on heartbeat, failover and quorum<\/a><\/td>\n

Require a special quorum disk or a third quorum server to avoid data corruption on split brain<\/td>\n<\/tr>\n
Suited for<\/strong><\/td>\n<\/tr>\n
Software editors which want to add a simple high availability option to their application<\/a><\/td>\nEnterprise with IT skills in clustering and with large database applications<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div>
\n
\n\t

<\/a>Video comparing a shared disk architecture and a shared nothing architecture when considering disaster recovery<\/h2>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div>
\n
\n\t

Video content<\/h3>\n

This video first illustrates the work to be done with a shared disk architecture when the two servers of a high availability cluster must be placed on two remote sites.<\/p>\n

Next, the video demonstrates the same use case with the SafeKt shared nothing architecture.<\/p>\n<\/div>\n<\/div><\/div><\/div>

\n
\n\t