In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/01 Report--
This article introduces how to compare Microsoft S2D, VMware vSAN and EMC ScaleIO in SDS genre. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.
In the field of SDS (Server SAN), special commercial products, there are three genres:
1. The kernel layer of the operating system is implemented. The representative product is Storage Spaces Direct (S2D) of Microsoft Windows 2016.
2. Hypervisor kernel layer is implemented, and the representative product is VMware vSAN
3. The user state layer is implemented. There are many such products. Today, we take the ScaleIO of EMC as a representative.
Today, we intend to compare the latest versions of these three typical products to take a look at the current implementation level of different products with different architectures, so that we can refer to them when choosing models.
Each of the three schools has its own characteristics and has its own market strategy. Compared with the three major mobile operating systems, I think S2D is like Microsoft's windows phone. Although the software is relatively closed, the hardware is relatively open (servers that support windows 2016 can be used), and other mobile phone manufacturers can also use it except Microsoft. VSAN is more like Apple, which only supports authenticated hardware and pushes the all-in-one machine, because the experience is as good as iPhone. And ScaleIO, the most open, more like Android, basically no special requirements for hardware, but also open source.
However, I have introduced a lot of vSAN and ScaleIO before, and I believe readers are very familiar with them, but I have not introduced this S2D before and need to preheat it.
S2D is a new feature of windows 2016, which evolved from the storage spaces of windows 2012. The addition of a direct means that you can directly use the server's disk instead of sharing the disk, which is now the mainstream form of all SERVER SAN.
The deployment method is more flexible than vSAN, and it supports both super-converged deployment and separate deployment.
The network needs to support the RDMA function, up to 16 nodes. Use the latest file system ReFS v2 instead of NTFS.
Support SSD or NVMe to do Cache.
Data protection supports 2 copies or 3 copies, as well as a check code similar to RAID 5 and 6, and the key can also be mixed.
This flexible way of data protection can achieve a balance between performance and capacity.
ReFS is a new generation of file system introduced by windows 2012, which is further improved on windows 2016 and will completely replace NTFS in the future. S2D needs ReFS support. ReFS has richer metadata, stronger fault tolerance, and real-time layering ability.
It can support 3-layer configuration, and the same media and different data protection methods can also be divided into different layers.
In terms of fault tolerance, like other SERVER SAN products, it supports uninterrupted operation in the event of disk, node or even cabinet failures.
Deployment requires a minimum of 2 nodes and a maximum of 16 nodes.
The nodes communicate with each other by SMB 3.0protocol. In the case of HCI deployment, Hyper-V uses cluster shared volumes to directly use the ReFS file system, and if it is a separate deployment, other Windows servers access storage resources through SMB 3.0.
OK, with a preliminary understanding of S2D, let's take a look at the comparison of these three products. First of all, I still recommend the comparison of whatmatrix websites, which is more detailed.
First of all, let's take a look at the overall rating of the site. VSAN scored 149. Scaleio scored 122, while S2D scored 115.
VSAN scores highest in terms of architecture, data availability, data services, and management.
Let's take a look at the specific comparison one by one.
Let's take a look at the overall situation. As we can see, S2D is only version 1.0, so it's normal to score low, because the latter two have a history of more than five versions.
Let's take a look at the architecture comparison. We see that because both S2D and vSAN are integrated into the kernel, there is a higher degree of automation. In terms of deployment mode, vSAN only supports super-fusion deployment, while others support layer-2 deployment. Moreover, we see that all three support physical machine access. S2D uses SMB3 protocol and can only support windows SQL server payload, while vSAN uses iSCSI protocol and supports most workloads, including oracle RAC, while ScaleIO supports windows and Linux payloads through private protocols (clients need to be installed). They do not provide general file services, but can rely on upper-level software or third-party software. In the underlying data layout, only vSAN uses object storage file systems, while the other two are block pools. In terms of scalability, ScaleIO supports 1K nodes, while vSAN has only 64, but S2D has only 16. Everyone supports all-flash and mixed mode, and only ScaleIO supports pure disk mode.
Then, let's take a look at data availability. In terms of disk protection, S2D and vSAN both support multiple copies or RAID, while ScaleIO only supports 2 copies. S2D currently does not provide snapshot support and can only take advantage of Hyper-V and Windows's own snapshot mechanism. Backup is not provided by everyone, and they all rely on the backup capability of the upper operating system or VM. Remote replication capability, S2D supports synchronous and asynchronous, vSAN supports dual active, while ScaleIO does not support remote replication (you can add RecoverPoint to achieve it).
Let's take a look at the comparison of data services. Re-deletion and compression are currently only supported by vSAN, but all-flash memory is required. In terms of QoS, everyone supports it, but only S2D can set a minimum threshold, that is, it can guarantee the performance of critical business (see not all QoS can ensure the performance of critical business).
Finally, let's look at management. Everyone supports GUI, but some functions of S2D still need to be done on the command line. S2D and vSAN support VM policy deployment because they are integrated into the kernel, while ScaleIO cannot support policy deployment because it does not support the vVol feature.
We can see that the functions of these three forms of SDS are relatively perfect and can meet the needs of ordinary customers. However, if you want more automation, the form of the integrated kernel will be better, if you want more open, more extensible, then user-mode SDS is a better choice.
Although Microsoft S2D has the lowest overall score, it has many advantages:
1. The License fee is low. Because it is included in the windows 2016 data center version, you can use it for free at a lower cost.
2. A wide range of hardware choices. Almost all hardware is supported, as long as windows 2016 supports it. If you think about it, the servers and accessories on the market will certainly find ways to be compatible with windows, otherwise they won't sell. Therefore, S2D's hardware compatibility is actually the best.
3. Flexible deployment. Support for two deployment methods, support for hyperfusion and separation deployment, and integrated into the kernel of hypervisor and OS, you can take advantage of many of the features of windows and hyper-v.
Therefore, when choosing, you can't look at the score, but also need to look at your application scenario.
As for the future, I think the future of S2D is also very optimistic. The future must be an era of hybrid clouds, and SDS needs to have the ability to access public clouds. Although AWS share is the highest, the growth rate of Azure is frighteningly high. The seamless connection between S2D and Azure, with the popularity of Azure Stack, this tightly coupled collaboration advantage may outweigh the loose coupling advantage of AWS and VMware.
That is, in the future, S2D will be fully integrated into Hyper-V,Windows,Azure, or even SQL Server,Exchange load. Microsoft is the only hybrid cloud vendor that can provide end-to-end software stack, and must have insurmountable advantages in automation and collaboration.
At present, the biggest problem is that S2D is just version 1.0. from experience, to be more mature, you usually need to iterate more than three versions, but S2D must also be released with OS, that is, it may not be mature until windows 2022 (assuming a version every 3 years), and the time window is a bit long. However, this is not a problem, and it is not impossible to release S2D alone, depending on Microsoft's attitude towards S2D.
This is the end of the comparison of Microsoft S2D, VMware vSAN and EMC ScaleIO in the SDS genre. I hope the above content can be of some help and learn more knowledge. If you think the article is good, you can share it for more people to see.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.