Hitachi Vantara HUS · AMS · HNAS · HCP Maintenance
side by side.

HUS · Hitachi Unified Storage

HUS 110 · HUS 130 · HUS 150 · HUS VM

AMS · Adaptable Modular Storage

AMS 2100 · AMS 2300 · AMS 2500 (older, deep EOSL)

HNAS · NAS platform

HNAS 3080 · 3090 · 4040 · 4060 · 4080

HCP · Content Platform / object storage

HCP G10 · G11 · G20 · S10/S30 (HCP-S object tier)

Components

SAS 600 GB / 1.2 TB / 1.8 TB · NL-SAS 2/3/4/6/10 TB · cache · controllers · 8/16G FC · 1/10 GbE

EOSL status of legacy platforms

Hitachi Vantara has largely withdrawn from classic storage hardware maintenance. For HUS, AMS and older HNAS generations, often no renewal is available at all, or only at rates designed to economically force a refresh. That's exactly the problem: when HUS 130 or AMS 2500 still serve productive workloads — and they often do — refresh pressure is purely commercial. TPM breaks this coupling.

We stock legacy-specific components in depth — SAS and NL-SAS disks of all generations (including older 600 GB / 1 TB / 2 TB drives), cache modules for HUS and AMS, controller boards for HNAS 3000 and 4000 generations, replica components for HCP clusters. For very old AMS 2100 components we work with certified refurbishing partners. HCP runs as an object storage cluster — node failures are a standard maintenance use case.

The full OEM-vs-TPM matrix (spare parts, SLA tiers, language, sub-outsourcing, compliance docs, reporting) is the same for every Hitachi Vantara line — see the Hitachi Vantara battle card.

BAIT/MaRisk documentation package, DORA Art. 28 contract template, ISO 27001 and GDPR-compliant media handling apply identically to every Hitachi Vantara line — details on the Hitachi Vantara battle card.

Same four steps for every Hitachi Vantara line: inventory → fixed-price quote in 48 h → contract (BAIT/MaRisk/DORA hooks) → hand-over with spare-parts provisioning. Details on the Hitachi Vantara battle card.

Which Hitachi legacy platforms do you service?

HUS (110, 130, 150, HUS VM), AMS (2100, 2300, 2500), HNAS (3080, 3090, 4040, 4060, 4080) and HCP (G10, G11, G20 plus S10/S30 as object tier). Including all disk and cache configurations, controller boards and connectivity components.

How high is the saving on EOSL Hitachi legacy?

For AMS and HUS we typically see 60 to 70 percent savings — Hitachi often no longer offers regular renewal here. For a HUS 130 with 24×7×4, TechCare is roughly 60–65% below Hitachi's last terms (with high refresh markup). HNAS 4060 similar. HCP G10/G11 slightly higher absolute due to cluster architecture.

Can you still get disks for AMS and HUS?

Yes. SAS disks (600 GB, 1.2 TB, 1.8 TB) and NL-SAS disks (2 TB, 3 TB, 4 TB, 6 TB) for HUS are in our warehouse. For AMS 2100/2300 the specific 600 GB / 1 TB FC and SATA disks have become rare — we use certified refurbishing partners. AMS 2500 is better covered due to later generation.

Does HCP continue to work as an object storage cluster without a Hitachi contract?

Yes. HCP clusters are self-managed — object storage logic, replication between tenants, compliance features (versioning, WORM, retention) continue to work without licensing. Code updates to newer HCP versions require an active Hitachi contract. Usually no issue with stable HCP workloads (typically SharePoint archives, compliance data).

What about BlueArc heritage in HNAS?

HNAS (Hitachi NAS Platform) is based on the BlueArc architecture acquired by Hitachi in 2011 — an FPGA-accelerated NFS/SMB filer. Maintenance-relevant: HNAS hardware is BlueArc-specific, not generically replaceable. We stock cluster nodes and FPGA cards for 3000 and 4000 generations.

Which SLA levels for legacy fleets?

HUS, AMS and HNAS have often become tier-2 or secondary storage — 5×9 NBD is economically appropriate. For productive HUS VM or HNAS 4040+ as primary NAS, we recommend 24×7×4. HCP clusters are typically well covered with 5×9 NBD due to cluster redundancy.