SAS (Serial Attached SCSI)
This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| SAS (Serial Attached SCSI) | |
|---|---|
.png) | |
| Name | SAS (Serial Attached SCSI) |
| Type | Storage interface |
| Introduced | 2004 |
| Designer | Logical Unit Numbers, T10 |
| Predecessor | Parallel SCSI |
| Successor | NVMe (coexistence) |
SAS (Serial Attached SCSI) is a point-to-point serial protocol for connecting storage devices, designed for enterprise-class data centers and server environments. It was standardized by the T10 committee and adopted by vendors including IBM, Dell, Hewlett-Packard, Seagate, and Western Digital to replace Parallel SCSI and to interoperate with SATA devices. The specification emphasizes reliability, scalability, and backward compatibility with legacy SCSI command sets, targeting deployments in SANs, RAID arrays, and high-availability clusters.
Introduction
SAS emerged as an industry response involving committees and vendors such as the T10 committee, IBM, EMC, Hewlett-Packard, Seagate, and Western Digital to provide a serial replacement for Parallel SCSI. The standard supports features from earlier SCSI efforts formalized in ANSI documents and aligns with server platforms from Cisco, Dell, and HPE. SAS positions itself alongside technologies promoted by Intel, AMD, and Broadcom in data center ecosystems and often integrates with storage architectures from NetApp, Hitachi, and Fujitsu. Major system integrators like Lenovo and Supermicro adopted SAS interfaces in blade servers, rackmount arrays, and converged infrastructure promoted by VMware, Microsoft, and Red Hat.
History and Development
Development traces through the T10 working group and standards activity involving ANSI and INCITS, with vendors such as Seagate and IBM participating in specification drafts. Early commercialization involved adopters including Dell, HP, and EMC integrating controllers from LSI Logic and Adaptec, while research labs at universities collaborated with industry partners like Intel and Broadcom on signaling and protocol improvements. As multi-core CPU platforms from AMD and Intel evolved, so did SAS controller firmware and drivers from Microsoft, VMware, Red Hat, and Oracle to support hot-swap and multipath configurations. Milestones include the transition milestones where vendors such as Hitachi, Fujitsu, and Lenovo moved from Parallel SCSI arrays to SAS backplanes and JBOD enclosures.
Architecture and Protocol
SAS uses a layered model developed by the T10 committee and implemented by vendors including LSI, Broadcom, and Marvell, incorporating the SCSI command set standardized in ANSI documents. The architecture supports point-to-point links, expanders, and dual-port devices for redundancy in systems from Dell, HP, and IBM, and interoperates with SATA drives produced by Seagate, Western Digital, and Toshiba through protocol translation. Controllers from Adaptec, LSI, and Broadcom implement PHY, link, transport, and application layers to work with host systems running Microsoft Windows Server, Red Hat Enterprise Linux, VMware ESXi, and Solaris. Fabric elements such as expanders and wide ports enable topologies used by NetApp, EMC, and Hitachi storage arrays to achieve multipath configurations with software from Veritas, SUSE, and Canonical.
Performance and Features
SAS generations (SAS-1, SAS-2, SAS-3, SAS-4) increased serial link rates, adopted by vendors like Seagate, Western Digital, and Toshiba to improve throughput and IOPS in appliances from Dell EMC, HPE, and IBM, while enterprise OS vendors including Microsoft, VMware, and Red Hat updated drivers. Features such as full-duplex signaling, NCQ introduced in collaboration with SATA initiatives, and dual-port redundancy are leveraged in RAID arrays built by Promise Technology, Areca, and Broadcom-based controllers. Advanced features including zoned namespace concepts in related storage technologies and compatibility strategies with NVMe promoted by Intel and Samsung influence SAS deployment decisions in hyperscale environments operated by Google, Facebook, Amazon Web Services, and Microsoft Azure.
Connectors, Cables, and Physical Layer
SAS physical interfaces and connectors were specified in standards maintained by T10 and implemented by manufacturers such as Amphenol, TE Connectivity, and Molex, and are used in server chassis from Supermicro, Dell, and HPE. Cables and backplane designs by Foxconn, Quanta, and Avaya accommodate signal integrity requirements validated by test labs at UL and Intertek and follow practices employed by OEMs like Lenovo and Fujitsu. Connector types (SFF-8482, SFF-8087, SFF-8643, and newer SFF variants) are procured by vendors including Intel, Broadcom, and Marvell for enterprise systems from IBM, Dell, and HP, while channel specifications guide board-level implementations by ASRock Rack, Gigabyte, and Supermicro.
Compatibility and Interoperability
SAS supports interoperability with SATA drives made by Seagate, Western Digital, Toshiba, and Samsung through the use of SATA device protocols and translators implemented by controller vendors such as LSI, Adaptec, and Broadcom. Enterprise ecosystems from VMware, Microsoft, and Red Hat include multipath and driver stacks to manage failover and load balancing with controllers from Intel, Marvell, and Broadcom. Storage vendors including NetApp, EMC, Hitachi, and HPE provide validated compatibility matrices for arrays, and integrators like Cisco and Dell reference interoperability lists when certifying servers for enterprise solutions with software from Oracle, SAP, and IBM middleware.
Applications and Use Cases
SAS is widely used in enterprise RAID arrays from Dell EMC, HPE, and IBM, in storage enclosures from NetApp and Hitachi, and in high-availability clusters managed by VMware, Microsoft, and Red Hat. Hyperscale datacenter operators such as Google, Amazon, Facebook, and Microsoft have evaluated SAS for dense storage tiers, whereas backup and archival solutions from Veritas, Veeam, and CommVault rely on SAS-connected tape libraries and disk libraries from Quantum and Spectra Logic. Workloads in virtualization platforms from VMware, container orchestration by Kubernetes, and database systems from Oracle, Microsoft SQL Server, and PostgreSQL use SAS for predictable latency and enterprise-grade reliability.
Security and Management Features
Management capabilities include support for SCSI Enclosure Services and SES implementations used by vendors like HP, Dell, and IBM for enclosure monitoring, while SNMP traps and Redfish support are implemented by Supermicro, HPE, and Lenovo for system management. Firmware management and secure firmware update workflows are handled by vendors such as Broadcom, LSI, and Intel with ecosystem tools from Microsoft, Red Hat, and VMware to maintain chain-of-trust in enterprise deployments. Access controls, secure erase features, and drive-level encryption—implemented by drive manufacturers including Seagate, Western Digital, and Toshiba—are integrated into management stacks used by NetApp, EMC, and Hitachi for compliance with standards referenced by auditors at PwC, KPMG, and Deloitte.
Category:Computer storage interfaces