Enterprise Storage
Seagate Mozaic 3+ and HAMR Explained: More Capacity per Bay, Better Planning
A practical explanation of high-density HDD technology, with capacity-per-bay arithmetic, current Mozaic context and the compatibility and recovery checks buyers need.
Mozaic 3+ uses HAMR to increase how much data can fit in a familiar HDD form factor. The practical benefit is more capacity per bay. It does not remove compatibility checks, guarantee SSD-like response or make backup and recovery easier by itself.
When every drive bay is occupied, growth can force a bigger enclosure, another shelf or a denser set of disks. High-density recording is interesting because it changes that choice. It can delay a physical expansion, but the right comparison includes performance, protected capacity and the time needed to recover a much larger dataset.
What HAMR Actually Changes
Density Starts at the Recording Surface
- Recording Medium
- Assisted Write
- More Bits per Area
- More TB per Bay
This is a conceptual chain, not a drawing of the internal mechanism. Denser recording changes capacity; whole-system performance still needs its own assessment.
HAMR means heat-assisted magnetic recording. A very small region of the recording medium is heated briefly during writing so that data can be recorded in a denser, stable magnetic structure. Mozaic combines this with its media, writer, reader and controller technologies.
That does not mean the entire disk enclosure runs at the local write temperature. Keep the drive sealed, follow the host's airflow requirements and monitor operating temperature normally. An open-drive illustration is not an installation instruction.
HAMR, CMR and SMR Answer Different Questions
| Term | What It Describes | Buying Meaning |
|---|---|---|
| HAMR | Assistance used during magnetic writing | A route to greater recording density |
| CMR | Conventional, non-overlapping track arrangement | Check the exact supported drive and workload |
| SMR | Overlapping, shingled tracks | Host-management and write behaviour may need a different design |
| Mozaic | Seagate's platform and generation naming | Not a substitute for an exact model number |
The terms are not mutually exclusive categories. For example, Seagate's referenced Exos M 30 TB and 28 TB data sheet identifies those models as CMR, while the platform uses HAMR. Do not copy that specification onto another capacity, SKU or generation without checking it.
From Mozaic 3+ to 4+: Read the Availability Carefully
In its 03-Mar-26 announcement, Seagate described Mozaic 4+ qualification and production with two hyperscale cloud providers, supporting capacities up to 44 TB.
That is significant platform progress, but it is different from proving that any customer can order a qualified 44 TB drive for any existing NAS. Supply channel, firmware, exact model and host certification remain separate questions. A cloud provider's qualified deployment is not a blanket home-NAS compatibility statement.
A Capacity-per-Bay Example You Can Actually Use
To isolate the arithmetic, compare twelve equally sized drives under the same simplified RAID 6 assumption: two drives' worth of capacity reserved for parity. These are planning examples, not a recommendation that every enclosure supports every drive shown.
| Drive Size | Raw Total | RAID 6 Nominal Data Capacity | Relative to 20 TB Drives |
|---|---|---|---|
| 20 TB | 240 TB | 200 TB | Baseline |
| 24 TB | 288 TB | 240 TB | 20% more nominal data capacity |
| 30 TB | 360 TB | 300 TB | 50% more nominal data capacity |
Formatting, metadata, spares and operating free space reduce the usable working total. If both systems use the same chassis, denser drives can increase capacity without adding bays. But the extra terabytes still need protection, and ten data drives remain ten data drives rather than an automatically larger pool of independent spindles.
Use the RAID calculator for other drive counts and protection layouts. Keep raw capacity, protected capacity and the capacity you intend to fill as three distinct numbers.
Capacity Storage and Fast Working Storage Have Different Jobs
Place Data Where Its Workload Fits
- Applications / AI
- Active Working Set
- Capacity Storage
- Independent Backup
Latency-sensitive work and large retained datasets need not use the same storage tier. Keep a recovery copy regardless of the recording technology.
A large retained video library or backup repository can benefit from dense HDD capacity. An application repeatedly reading small random blocks may care more about latency and IOPS. An AI workflow can need both: capacity for original footage and datasets, and faster storage for active indexing or model-related work.
Do not interpret an “AI storage” description as a promise that a drive performs inference or recognises objects. The application and compute platform do that work. Map the hot working set, the retained source files and the recovery copies before deciding which tier needs SSDs and which needs economical capacity.
The Exos X24 guide explains host checks and full-copy times, while the NAS speed-versus-price guide helps separate network and storage bottlenecks.
Compare Cost per Usable TB and the Recovery Window
A useful ownership calculation includes drives, enclosure, controllers, power, cooling, support and the backup system, divided by comparable usable capacity. Use the same protection, retention and workload assumptions on both sides. A quoted power-per-TB improvement against an old reference drive is not a guaranteed reduction for your complete rack.
Recovery time deserves the same discipline. At an assumed constant 200 MB/s, moving 30 TB takes about 41.7 hours before overhead or verification. A larger drive may reduce bay pressure while making a full copy a longer operation. Measure the actual route and agree how the business will work during it.
What to Do Before Buying Denser Drives
- State the working capacity, growth and protection requirement.
- Confirm the exact model, recording layout, interface and host qualification.
- Compare the complete system cost and power against comparable usable capacity.
- Test the intended workload rather than inferring speed from terabytes.
- Verify migration, independent backup and restoration within the required time.
Choose denser HDDs when they solve a supported capacity problem at a sensible total cost. Choose a different tier or architecture when latency, concurrency or recovery time is the real constraint. The recording technology is valuable because of the design it enables, not because it removes the need to design.
Frequently Asked Questions
What is Mozaic 3+?
It is Seagate's high-density HDD technology platform built around heat-assisted magnetic recording and supporting media, write/read and control technologies. It is a platform name, not one universal drive capacity or NAS compatibility approval.
Does HAMR mean the entire hard drive becomes extremely hot?
No. The write process heats a tiny recording region briefly. The drive still needs normal operating-temperature control and suitable airflow, but the local write mechanism must not be confused with the temperature of the whole enclosure.
Is HAMR the opposite of CMR?
No. HAMR describes assistance used to write magnetic data; CMR and SMR describe different track arrangements. A HAMR-based product can be CMR. Check the exact drive data sheet rather than assuming from the platform name.
Are 44 TB drives automatically available for any NAS?
No. Seagate announced Mozaic 4+ production with selected hyperscale providers. That does not establish local retail availability, stock or support in a particular NAS. Qualify the exact model and host.
Does a higher-capacity drive make AI run faster?
Not by itself. Capacity can hold larger datasets, recordings and archives. Model execution, indexing and active data access also depend on compute, memory, latency, bandwidth and application design.
How should I compare energy savings?
Use measured or specified watts for the complete system divided by comparable usable capacity, with the same protection and workload assumptions. Include controllers, fans and other infrastructure. A vendor's reference comparison is not a universal saving.
What matters before moving to denser HDDs?
Host qualification, exact SKU, recording layout, usable capacity, workload, cooling, migration method and a timed restore plan. A higher raw capacity is only one part of the decision.
