EOSL maintenance — run hardware past End of Life (EOL) for years
End-of-Service-Life is a manufacturer decision, not a technical reality. A storage platform that has run stably for 7 years doesn't automatically fail because the OEM ends maintenance. But this is exactly when the drama starts: OEM extensions are refused or only offered as overpriced custom-support packages, software updates slow down, and internal pressure builds for an early refresh. We offer the alternative: full maintenance for EOSL hardware, with OEM parts, equivalent SLA tiers, and honest per-system risk assessment.
Short answer
Hardware past end of life (EOL) or end of service life (EOSL) can be operated safely with third-party maintenance: TechCare Solutions keeps maintaining end-of-life servers, storage and network hardware from all 28 covered manufacturers, with SLAs up to 24×7×4, original spare parts and typically 30–70 % below what manufacturers still charge after EOSL. The hardware keeps running until a replacement makes economic sense, instead of being forced by the manufacturer's date.
End of Life, End of Sale, EOSL: what the terms mean
Manufacturers use these terms inconsistently. For maintenance, one date matters most: when the manufacturer stops providing support.
- End of Sale (EOS)
- The manufacturer stops selling the product new. Support, maintenance contracts and spare parts remain available, usually for another three to five years.
- End of Life (EOL)
- Umbrella term for the end of a product's life from the manufacturer's point of view. Depending on the vendor, EOL means end of sale or end of support. The hardware itself keeps working as before.
- End of Service Life (EOSL)
- From this date the manufacturer provides no support at all: no maintenance contract, no parts replacement, no firmware fixes. For operations, this is the date that matters. Also called End of Support (EOS).
- Last Day of Support (LDoS)
- Cisco's name for the EOSL date. After it, neither a SMARTnet renewal nor TAC support or RMA replacement is available.
- What happens after EOSL
- The hardware keeps running. Failures are no longer fixed by the manufacturer but by a third-party maintenance provider like TechCare, with original spare parts and the same SLA. You can look up your devices' dates in the EOSL tracker.
What TechCare's EOSL maintenance delivers
EOSL maintenance is not a stop-gap with reduced service scope. You get full maintenance — the one constraint EOSL technically introduces is the missing OEM software-patch cycle, which we cannot replace (but is often irrelevant on a mature hardware generation).
Parts even for 8-10 year-old generations
We stock certified OEM and refurbished components for EOSL hardware in DACH depots. Disk arrays of past generations, older storage processor modules, multi-generation ECC RAM, backplanes, PSUs. For extremely rare components (mainframe-class, specialty boards) we set up per-contract pre-stock arrangements.
Realistic per-system lifespan forecast
At contract start you get a per-system assessment: how long is continued operation recommended, what are the typical failure modes for this model, when should you actively plan the refresh. This assessment is vendor-independent and based on our DACH service database — not on marketing pressure to refresh.
Engineers who know EOSL generations
Our field engineers have hands-on experience with generations like VNX2, EqualLogic PS, IBM Storwize V7000 G2, Cisco Catalyst 6500, HPE EVA, NetApp FAS2200 hundreds of times over. This know-how is systematically lost at OEMs once a model hits EOSL — internal specialists retrain on new generations or leave the company.
SLA tiers like for active hardware
EOSL at TechCare doesn't mean reduced service. If your system needs a 24×7×4 SLA, you get 24×7×4 — even on a 9-year-old EqualLogic cluster. The prerequisite is spare-parts availability, which we verify before contract. If we can't hold the SLA, we say so up front — not at escalation time.
From EOSL notice to active contract
When the manufacturer announces an EOSL date for one of your platforms, you typically have 12 to 18 months lead time. Ideal: come to us 6 months before EOSL, then we build spare-parts staging unhurriedly.
- 1
EOSL risk audit
Send us the list of EOSL-affected systems. We perform a risk audit: technical serviceability, spare-parts availability, typical failure rates, critical single points of failure. From this we produce a per-system recommendation: continue operation (with or without pre-stock), replace quickly, or migrate in a planned sequence.
- 2
Define spare-parts strategy
For every system to keep operating we define: which components are in standard depot, which get centrally pre-stocked, which may be stored on-site with the customer. For very rare components there can be a pool agreement across TechCare customers running the same platform.
- 3
Contract with clear EOSL clauses
Contracts for EOSL maintenance have specifics: defined SLA tiers, documented fallback scenarios for unobtainable parts, honest exit clauses if the platform suddenly becomes technically untenable. We use standard templates negotiated with DACH mid-market — no hidden escalation costs.
- 4
Handover and pre-stock build-up
Contract start typically lines up exactly with your OEM contract expiration. In the first 4 to 8 weeks we build pre-stock — depending on component availability. For very old generations this can take longer; in that case we bridge with a best-effort SLA tier and replenish over time.
- 5
Quarterly lifecycle reviews
On EOSL hardware a one-time lifecycle assessment isn't enough — risk evolves. In quarterly reviews we check: any failures, how is parts availability changing, any new signals of systematic weak points. This produces an ongoing recommendation: continue or start refresh planning.
Why EOSL maintenance via TechCare, not OEM custom support
When a manufacturer ends official maintenance, OEM options are usually two: no renewal at all (you're uncovered), or a custom-support contract priced 50 to 200 percent above the original maintenance fee, depending on OEM. These custom-support contracts are economically calibrated to drive refresh sales — not to economically operate EOSL hardware. On a 6-year-old EqualLogic, OEM custom support per year can exceed the hardware's original price.
We price EOSL maintenance differently because we have no refresh business. Our model: for every system build a realistic risk profile, stage parts to match, offer clear SLA tiers. On hardware with well-known weak points (e.g. backplanes of generation X, disks from a known batch with elevated failure rate), we're often cheaper than OEM custom support because we know what to stock — the OEM prices high in bulk because it no longer actively maintains generation-specific detail knowledge.