S2D (Storage Space Direct) – Concept & Planning

S2D (Storage Space Direct) adalah Storage dengan konfigurasi Software-defiened dan Shared-nothing storage.

Definisi:

  • Software-defined: S2D menggunakan server yang tersedia secara umum, untuk membuat setorage alternative yang lebih terjangkau harganya.
  • Shared-nothing: Konfigurasi S2D akan menggunakan disk yang terpasang langsung pada server. HA (High Availability) dicapai dengan menggabungkan disk dari server-server yang digunakan kedalam storage pooling

Server Topology:

Server Topology V1.0

S2D configuration topology:

S2D ConfigurationTopology V1.0

Memilih disk yang sesuai dengan kebutuhan

S2D mendukung 3 tipe drive yang bisa digunakan, yaitu:

S2D Disk Support.png

Skenario Storage Disk

S2D memiliki fitur build-in server-side cache, yang berguna untuk mendorong performa read and write pada storage. S2D akan secara otomatis memilih disk memiliki performa paling tinggi, dan sisanya akan digunakan untuk kapasitas penyimpanan. Kombinasi yang memungkinkan adalah:

1. Performa

S2d Disk Performa.png2. Keseimbangan antara performa dan kapasitas

S2d Disk Balance.png

3. Kapasitas

S2d Disk Kapasitas.png

Storage Space Direct Hardware Requierment

Basic requirements

All systems, components, devices, and drivers must be “Certified for Windows Server 2016” per the Windows Server Catalog.

The fully configured cluster (servers, networking, and storage) must pass all cluster validation tests per the wizard in the Failover Cluster snap-in or with the Test-Cluster cmdlet in PowerShell.

In addition, the following requirements apply.

Additional requirements for Storage Spaces Direct Servers

  • Minimum of 2 servers, maximum of 16 servers
  • All servers should be the same make and model

CPU

  • Minimum of Intel Nehalem or later compatible processor

Memory

  • 4 GB of RAM per terabyte (TB) of cache drive capacity on each server, to store Storage Spaces Direct metadata. Note that RAM sizes use base-2 numbering (where 1 GB = 1,024 MB), while drives are advertised using base-10 numbering (where 1 TB = 1,000 GB). For example, if each server has 2 x 1.6 TB (advertised capacity) cache drives, you should keep 2 x 1.6 x 4096 MB = 13,107 MB (12.8 GB) of memory available for Storage Spaces Direct internal use.
  • Any memory used by Windows Server, VMs, and other apps or workloads.

Networking

  • Minimum of 10 Gbps network interface for intra-cluster communication
  • Recommended: Two NICs for redundancy and performance
  • Recommended: NICS that are remote-direct memory access (RDMA) capable, iWARP or RoCE

Drives

For more help choosing drives, see the Choosing drives topic.

  • Use local-attached SATA, SAS, or NVMe drives.
  • Every drive must be physically connected to only one server.
  • All servers must have the same drive types (if one server has NVMe, they all require NVMe. If one has HDD, they all require HDD)
  • Recommended: All servers have the same drive configuration (type, size, firmware)
  • SSDs must have power-loss protection, i.e. they are “enterprise-grade”
  • Recommended: Cache drives must have high write endurance: at least 3 drive-writes-per-day (DWPD) or at least 4 terabytes written (TBW) per day. To learn more, see Understanding drive writes per day (DWPD), terabytes written (TBW), and the minimum recommended for Storage Spaces Direct.
  • Recommended: Add capacity drives in multiples of the number of NVMe or SSD cache devices.
  • Drives can be 512n, 512e, or 4K native – they all work equally well.
  • Use a separate, dedicated drive or RAID 1 mirror for Windows Server (200 GB is a recommended minimum size).
  • Not supported: Multi-path IO (MPIO) or physically connecting drives via multiple paths.

Minimum number of drives

  • If there are drives used as cache, there must be at least 2 per server
  • There must be at least 4 capacity (non-cache) drives per server

Disk kombination.png

[!NOTE] This table provides the minimum number of drives required for bare-metal deployments. If you’re deploying Storage Spaces Direct using virtual machines and virtualized storage, such as in Azure, this requirement is waived because your “drives” aren’t expected to ever fail. In this case, the requirement is just two “drives” per server. In Azure, we recommend using premium data disks for better performance.

Maximum

  • Maximum of 1 petabyte (1,000 TB) of raw capacity per storage pool

Host-bus adapter (HBA)

  • Simple pass-through SAS HBA for both SAS and SATA drives
  • SCSI Enclosure Services (SES) for SAS and SATA drives
  • Any direct-attached storage enclosures must present Unique ID
  • Not Supported: RAID HBA controllers or SAN (Fibre Channel, iSCSI, FCoE) devices

Sumber: https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-overview

 

Konfigurasi akan dilanjutkan di Storage Space Direct – Configuration Part1 Part2

Bila membutuhkan infomasi lebih lanjut mengenai Storage Space Direct, silahkan menghubungi info@Gulver.id atau 081311 268 268

Blog ini juga tersedia di:
http://gulver.id/blog/
http://hyper-v.id
http://mugi.or.id/leonardoirawan/

Leave a Reply

Your email address will not be published. Required fields are marked *