Five risks, five architectures
Pick the failure you are trying to avoid, and the technology argument becomes much shorter.
Immutability, longevity, retention, recovery and legacy replacement are separate problems. Most estates need two or three of them, rarely all five at once.
These five pages describe what each approach does not cover as well as what it does.
Where each tier earns its place.
Archive requirements are usually described in terms of a product category, which is why so many of them get solved badly. "We need WORM" and "we need an archive" can each mean at least three different things depending on which failure the buyer is actually worried about. Naming the risk first narrows the field faster than any feature comparison. What follows sorts our work into five risks. Each links to a page that goes into the mechanisms, the trade-offs and the residual exposure in detail.
Start from the risk, not the product
| The risk | Where to read next |
|---|---|
| Data can be altered or deleted early, including by a privileged account | Immutable and WORM storage |
| Data survives but nothing can read it in fifteen years | Long-term data archiving |
| A retention rule exists on paper and nothing enforces the clock | Regulatory data retention |
| Copies exist but recovery misses the time the business was promised | Backup and recovery storage |
| The platform holding the archive is out of support or unreadable | Archive migration and modernisation |
How the five areas fit together
They are layers of the same estate rather than alternatives. Enforcement decides what cannot be removed. Longevity decides what remains readable. Retention decides how long the clock runs and who set it. Recovery decides how fast a copy returns. Migration is what happens when one of the first four was solved on a platform that has now aged out.
Working from left to right in that order avoids the most expensive mistake, which is buying capacity that enforces nothing. If you are not sure which of the five applies, an assessment sorts it, and the technologies section covers the components underneath.
Explore solutions
Solution
Immutable, WORM & Ransomware-Resilient Storage
Hardware WORM media, appliance retention lock, S3 Object Lock and offline media each defeat a different attacker. Choosing between them is an architecture decision, not a purchasing one.
Learn moreSolution
Long-Term & Active Archiving
Data outlives the media, the drives, the software and usually the team. Designing for that horizon means planning refresh cycles and recall times up front, not discovering them during an audit.
Learn moreSolution
Regulatory Retention & Compliance
Aban Smart works with records and compliance teams to express retention rules as storage-level controls, with the audit trail an assessor will ask to see.
Learn moreSolution
Backup & Recovery Storage
This is about the storage sitting underneath your backup application: how fast it gives data back, how much of your history it should hold, and how you prove any of it before the day it matters.
Learn moreSolution
Archive Migration & Modernisation
Copying twenty years of files onto newer media is arithmetic. Keeping retention clocks, ownership, checksums and application stub paths intact across the move is the work that actually decides the outcome.
Learn moreFrequently asked questions
Whichever one an auditor, an incident or a support expiry has already raised. Where nothing external is forcing the order, enforcement and recovery come first, because both are cheap to specify at design time and expensive to retrofit. Longevity and migration matter most for estates that already hold years of data on ageing media.
Related pages
Turn your requirement into a defensible architecture
Share the workload, capacity, retention, access, and resilience requirements. Aban Smart will identify the next discovery inputs and the appropriate engagement path.