Seagate 9ZM173-579 2TB SAS Constellation HDD: Specs and Array Replacement
Constellation is a name Seagate stopped using years ago, which is exactly why this drive needs explaining. If your array documentation or asset register says Constellation, you are maintaining a system from a specific era, and knowing where that name sits in Seagate’s history tells you what you can replace it with.
The Seagate 9ZM173-579 is a 2TB SAS 7200RPM 3.5-inch nearline drive from the Constellation ES line.
Where Constellation sits in Seagate’s enterprise history
Seagate has run three enterprise families over the past two decades, and the names map onto distinct roles rather than just marketing refreshes.
Cheetah was the 15K performance line, built for transactional latency, with small capacities and high power draw. It is fully legacy now but still needed as spares for older SAN and server platforms.
Constellation was the nearline capacity family that ran alongside and after it — 7200 RPM, built for 24/7 duty, aimed at backup, archive and bulk storage rather than IOPS. Constellation ES specifically denotes the enterprise storage variant.
Exos is the current family, and it absorbed both roles: high-capacity nearline drives carry the Exos name today.
The practical implication is that a Constellation drive and an Exos nearline drive are the same class of product from different generations. Where a system takes one, the other is usually a viable functional equivalent at matching capacity and interface — though in an existing array, capacity uniformity matters more than family name.
9ZM173-579 specifications
| Part Number | 9ZM173-579 |
| Manufacturer | Seagate |
| Product Family | Constellation ES |
| Capacity | 2TB |
| Interface | SAS |
| Rotational Speed | 7200 RPM |
| Form Factor | 3.5 inch LFF |
| Drive Class | Nearline |
| Condition | Refurbished, function-tested |
| Warranty | 30-day TechSellerUSA warranty |
Why capacity uniformity beats capacity upgrade
The temptation when replacing a failed 2TB drive is to fit something larger, on the reasoning that capacity is cheap and you may as well. In an array, this does not work the way people expect.
A RAID group uses the smallest member capacity across every drive. Fit a 6TB drive into a group of 2TB members and the array uses 2TB of it. The remaining 4TB is stranded — not available, not usable, and not refundable.
Expanding the group properly means replacing every member and rebuilding, one drive at a time, with a full rebuild between each. On 2TB members that is a long process during which the array is repeatedly degraded, and it only yields the extra capacity once the last drive is done.
For a system that is working, replacing like for like is faster, cheaper and lower risk. Save the capacity upgrade for a planned migration rather than doing it accidentally one failure at a time.
SKU: 9ZM173-579  | Refurbished & function-tested  | 30-day warranty
View Details & Request a Quote →2TB is a manageable rebuild window
One genuine advantage of a system built on 2TB members: rebuild times are measured in hours rather than the day-plus that 12TB and 14TB drives can require.
That shortens the exposure window considerably. During a rebuild the array is degraded and every surviving drive is under sustained read load, and the shorter that period, the lower the chance of a second failure landing in it.
It also means RAID 5 remains defensible at this capacity in a way it is not at 12TB, though RAID 6 is still the safer choice on any array holding data you would miss. The calculation shifts with drive size, and 2TB sits on the comfortable side of it.
Where drives have been running for years, however, the population is ageing together — and correlated age is what drives correlated failure. A spare on the shelf matters regardless of rebuild speed.
SAS on a nearline drive
This is a SAS drive rather than SATA, which for a capacity drive buys three things: dual-port path redundancy so a single cable or expander failure does not isolate it, deeper command queuing that keeps the system responsive while a rebuild reads every drive at once, and richer error telemetry so predictive failure warnings arrive with more notice.
On a single-path backup target none of that applies and SATA is a legitimate saving. Behind a redundant controller pair or in a shared array, SAS is the correct specification — and if the array was built with SAS drives, keeping the backplane consistent avoids the odd behaviour that shows up when SAS and SATA are mixed behind the same expander.
Ordering
We supply the 9ZM173-579 refurbished and function-tested with a 30-day warranty, single spares or in volume. Browse the full Seagate range or our complete enterprise hard drives catalogue, and see the compatibility guide if you need carrier or firmware requirements confirmed for an OEM chassis.
Common questions
What is Seagate Constellation?
Constellation was Seagate’s nearline capacity family — 7200 RPM drives built for 24/7 duty in backup, archive and bulk storage. Constellation ES denotes the enterprise storage variant. The current equivalent family is Exos.
Can I fit a larger drive to gain capacity?
Not usefully. A RAID group uses the smallest member capacity, so a 6TB drive in a group of 2TB members gives you 2TB and strands the rest. Expanding properly means replacing every member with a full rebuild between each.
Is RAID 5 acceptable with 2TB drives?
More defensible than at 12TB, because rebuild times are hours rather than a day or more and the exposure window is correspondingly shorter. RAID 6 remains the safer choice on any array holding data you would miss.
Can an Exos drive replace a Constellation one?
They are the same class of product from different generations, so at matching capacity and interface an Exos nearline drive is usually a functional equivalent. In an existing array, capacity and interface uniformity matter more than the family name.
Tell us your array model and how many drives of this part number are in service, and we will advise on spares.
