HSM: Nadiifinta ugu horeysay ee Mainframes, Cloud iyo S3

If you think “tiering” ayaa ku yaalaa sida cache-ka SSD iyo warshadaha cloud ... salaysan: aad u isticmaali karaa si ay u isticmaali karaa. Waxaad ka mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Hierarchical Storage Management (HSM) Waayo, waxaa laga yaabaa in ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Waayo, waxaa laga yaabaa in ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Waxaa laga yaabaa in ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Waa in la Marka: The Marka: The , iyo shuruudaha **way waa in uu u baahan tahay in uu ku yaalaa in ay ku yaalaa "innovation". 😄 Haku media interfaces scale What is HSM, really? Sida loo yaqaan HSM? HSM (Hierarchical Storage Management) waa mid ka mid ah macluumaadka ugu horeysay ee warshadaha: Users aad u aragto file ah. Admins aad u aragto ka mid ah "disk full" ticket. Dhammaan waxay ka mid ah in la mid ah la mid ah la mid ah la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah in la mid ah. make expensive storage look bigger by quietly moving data to cheaper tiers—without breaking the namespace Qalabka Qalabka Qalabka Qalabka , with some kind of Waayo, waxa uu ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa. HSM is policy-driven data placement across a storage hierarchy recall path The five moving parts of classic HSM (and why each matters) 1) A primary tier: where “now” lives Sida loo yaqaan 'Storage' waxaa loo yaqaan 'Storage': HDD, SSD, NAS high-perf, scratch, ama nidaamka file parallel Qalabka dhismaha iyo dhismaha ugu badan optimized for workflows shaqeeyaan Dhammaan waa Waxaad u baahan tahay in ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Haku 2) Secondary tiers: where “later” lives HSM waxaa laga yaqaan 'HSM' waxaa laga yaqaan 'HSM' waxaa laga yaqaan 'HSM' iyo 'HSM' waxaa loo yaqaan 'HSM'. Qalabka Disc Pool Shuruudaha Object Taageerada library Qalabka optical ama midabka kale oo ka mid ah wax soo saarka Qalabka dhismaha waaweyn ee dhismaha dhismaha iyo dhismaha dhismaha. . what belongs where and when 3) A policy engine: the brains (and the source of most arguments) Warbixiinta iyo Clash of Clans waa mid ka mid ah: Qiimee Haku warshad (mtime, atime, “Last referenced”) size (file ugu badan waa kandidaate ugu horeysay ee migration) path/project (ka mid ka mid ah /project/foo/ waa mid ka mid ah qaab foo) Shuruudaha (User / Group-based policies) Qalabka dhismaha (Heat / Heat / Cold Heuristics) Mashaariyo cusub oo ka mid ah: Tag / metadata (object systems) Shuruudaha workflow (job completed, project closed) - Shuruudaha workflow (job completed, project closed) Shuruudaha ugu soo saarka (Retention, Legal Holding) Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka A good policy engine is not just migrating data—ee ay ka caawinayaa in la taabto in la taabto wax soo saarka iyo wax soo saarka in wax soo saarka. Qalabka 4) A recall mechanism: how the illusion stays intact Sida loo yaqaan “Don’t break users”. In file-centric HSM, recall waa mid ka mid ah: file stub / placeholders oo ku salaysan name, size, timestamps, permitts, iwm. file system hooks/events sida "open()" la xira stage-back automatically gaabinta / gaabinta sida loo yaqaan "one scan doesn't recall the planet" In HSM / lifecycle-centric-object-centric, kharashka waa in la mid ah: Shuruudaha / Rehydrate Jobs Shuruudaha dhismaha ah ee bucket/work area Warbixinta Window Access wax soo saarka ah oo ka mid ah "transparent recall" Sida loo yaqaan "HSM" waxaa laga yaqaan "HSM" waxaa laga yaqaan "HSM" oo loo yaqaan "HSM". Iska dhismaha ah. Getting it back safely, predictably, and at scale 5) A migration engine: the muscle and the traffic cops Sida loo yaqaan 'Bytes' waxaa loo yaqaan 'Bytes' iyo waxaa loo yaqaan 'Bytes' waxaa loo yaqaan 'Bytes' iyo 'Bytes' waxaa loo yaqaan 'Bytes' iyo 'Bytes' oo loo yaqaan 'Bytes'. Moveers (waxanka dhismaha / hosts) Qalabka iyo Priority Qalabka parallel Qalabka bandwidth warshadaha media (wax ka mid ah tape / robotics) logic retry, audit, iyo raaxaysta ah Waxaad ka mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ah mid ka mid ah mid ah mid ah mid ah mid ka mid ah mid ah mid ah mid ah mid What HSM is (because people keep using the word wrong) not Haku HSM is not backup Waxaa laga yaabaa in ay ka mid ah dhismaha / dhismaha. HSM waa in ay ku saabsan xisaabinta dhismaha iyo dhismaha qiimeeyo. Backup Markaas ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah: HSM waxay ka soo xiriir data ka mid ah primary ka mid ah free space (wax yar) Backup waxaa loo isticmaali karaa ka mid ah wax soo saarka korontada (wax ka mid ah wax soo saarka korontada) If your “HSM” deletes primary data but you don’t have independent recovery history, waxa ay ku saabsan HSM—ee waa . Shirkadda IT HSM is not caching Shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha. Haku Inta badan oo ka mid ah mid ka mid ah macluumaadka. Caching HSM relocates entire files/objects Caching wuxuu ku yidhi, "Haddii ka mid ah ka mid ah ka mid ah. " HSM wuxuu ku yidhi: "Haddii ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa." Waxaad ka soo xiriir (wax yar), laakiin waxaa laga yaabaa wax badan oo dhan. The simplest way to think about HSM Qalabka A governed lifecycle for data placement: Sida loo yaqaan "Hot vs. Cold" Qalabka dhismaha ugu horeysay ee shuruudaha Nadiifinta Semantics ayaa ka mid ah loo isticmaali karaa Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka dhismaha dhismaha oo aad u baahan tahay in ay ku saabsan data iyo in ay ka mid ah HSM-ka ugu horeysay ayaa loo yaqaan "Stubs" iyo "Tape Robots". HSM-ka dhismaha ugu horeysay ayaa loo yaqaan 'life cycle rules', 'object metadata' iyo 'restore workflows'. Shirkadda ugu horeysay ee loo yaqaan 'Bobby Traps'. HSM vs ILM: same family, different job titles HSM vs ILM: same family, qalabka kala duwan Qalabka Mix Up and Waayo, waxaa laga yaabaa in ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Hierarchical Storage Management (HSM) Information Lifecycle Management (ILM) Waan ku saabsan sidaas: HSM waa mid ka mid ah macluumaadka. Ilm waa shuruudaha ah oo ka mid ah shuruudaha iyo shuruudaha, oo ka mid ah shuruudaha iyo shuruudaha. Qalabka waa isticmaalka: that aligns the Sida loo isticmaali karaa Haku iyo Sida loo isticmaali karaa in ay ka mid ah wax soo saarka, waxaa loo isticmaali karaa in ay ka mid ah wax soo saarka. SNIA’s ILM is an ongoing strategy Qalabka policies processes supporting infrastructure The lifecycle view: ILM starts before storage gets involved Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Creation / Ingest (how waa la xira org, wax metadata / tags waxaa laga yaabaa) Active use (Who can access it, qalabka adeegga) Shuruudaha / Shuruudaha (Distribution, replication, copies, versions) Shuruudaha (backup, snapshots, replication, integrity / fixity) (records, archives, research collections) Long-term retention Shuruudaha (shuruudaha legal, warqad dhismaha, qiyaasta qiyaasta) Shuruudaha (shuruudaha, shuruudaha, shuruudaha) HSM waa mid ka mid ah dhismaha oo ka mid ah "move it to cheaper storage" layer of execution - oo ka mid ka mid ah dhismaha oo ka mid ah wax ka mid ah, oo ka hor, oo ka mid ah oo ka mid ah xawaaraha legal ah. Practical translation (the one you actually use in architecture meetings) HSM = the machinery (execution layer) HSM waa mid ka mid ah macluumaadka kala duwan oo loo yaqaan tiering: Shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay. Shuruudaha dhismaha iyo dhismaha dhismaha dhismaha dhismaha Workflows Recall / Restore (wax yar, rehydrate, kharashka tareenka) Shuruudaha iyo dhismaha (shuruudaha dhismaha, dhismaha dhismaha) Warshadaha Media (tape libraries, volume catalogues, robotics control) Tracking State (Resident / Offline, kharashka in la soo saarka, dhismaha, iwm) HSM wuxuu ku yidhi, "Waax yar oo dhan, oo ka mid ka mid ah in ay ka mid ah?" ILM = the governance layer (intent + accountability) Ilm waa mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah: Shuruudaha dhismaha (shuruudaha dhismaha 7 sano, dhismaha dhismaha dhismaha 7 sano, dhismaha dhismaha dhismaha dhismaha dhismaha) Qalabka dhismaha iyo dhismaha dhismaha iyo dhismaha dhismaha iyo dhismaha dhismaha iyo dhismaha Shuruudaha xayawaanka (freeze disposition and sometimes freeze movement) Qalabka (public, internal, restricted, sensitive) Risk and cost management (ka mid ah class storage waa in ay ku salaysan, tolerances recovery) Shuruudaha (Defensible Deletion, Transfer, or Preservation) Shuruudaha dhismaha (who approves, who changes, who signs off) Haku Policy Qalabka Ilm wuxuu ku yidhi, "Waa'iid ka mid ah wax soo saarka, oo aan ku dhigi doonaa?" Where people go wrong: buying “ILM” as if it’s a product Inta badan oo ka mid ah shuruudaha waxaa loo yaabaa "ILM" sida buugga feature. Problem waa in ay ILM waa mid ka mid ah feature, waa mid ka mid ah nidaamka mid ka mid ah: warqad dhismaha (ka dhismaha dhismaha, dhismaha dhismaha) wax soo saarka ah (approvals, audits, exceptions, incident handling) Tooling (metadata / tagging, analytics, mobile engines, dhismaha ku salaysan) Waxaad ka mid ah ka mid ah wax soo saarka ah oo ka mid ah wax soo saarka iyo wax soo saarka iyo wax soo saarka. iyo — oo la soo saarka shuruudaha oo ku yaalaa in la soo saarka si ay u soo saarka shuruudaha iyo shuruudaha. (If they claim they do, they’re selling you optimism.) coordination accountability How they fit together in a modern stack Sida loo isticmaali karaa in loo isticmaali karaa in your article: : retention, access rules, acceptable latency, cost constraints, compliance obligations. ILM defines intent HSM waxaa loo yaqaan 'Migration', 'Level Transitions', 'Restore Workflows' iyo 'Enforcement Mechanisms'. *Diiwaanka : **ILM wuxuu ku yidhi: "Koolka waa in ay ku salaysan 25 sano, in ay ku salaysan, oo ay ku salaysan in ay ku salaysan ammaanka, iyo in ay ku salaysan in ka badan 24 saacadood." HSM waxaa loo isticmaali karaa: "Saacadda 90 maalmood, xawaaraha la soo saarka la soo saarka ah / archive; si loo isticmaali karaa wax soo saarka workflow; si loo isticmaali karaa wax soo saarka ah; si loo isticmaali karaa log; si loo isticmaali karaa wax soo saarka." ILM is the ‘why’ and the ‘rules of the road.’ HSM is the ‘how’—the engine that moves data across tiers in a way that matches those rules, especially in file-centric and hybrid environments. A quick timeline: mainframe → open systems → HPC → clustered file → object/cloud Mainframe roots (late 1970s through the 1980s): policy before it was cool Mainframe HSM wasn’t born as a “nice-to-have.” It showed up because Direct Access Storage Device (DASD) was expensive, data growth was relentless, and nobody was volunteering to manually babysit data sets at 2 a.m. IBM’s Hierarchical Storage Manager (HSM) (later Ka dibna ) waxaa la aasaasay in 1978 si ay u isticmaali karaa dhismaha dhismaha dhismaha automated for data sets using simple, repeatable criteria. DFHSM DFSMShsm Ma rabtaa HSM Automated space management: periodic, policy-driven cleanup and migration so primary pools didn’t stay “full forever.” Hierarchical “levels” of storage: data sets moved from primary volumes to cheaper tiers (including Migration Level 2 (ML2), typically on tape and usually not mounted/online). Stability Operational: warshadaha warshadaha (waxanka batch), warshadaha dhismaha, iyo warshadaha warshadaha tababarka ah oo ku yaalaa. **Other HSM-type products in the same era \ IBM wasn’t the only one chasing the same outcome. A major “HSM-adjacent / competing” line on z/OS was (hoos Broadcom), oo ka mid ah archive, space release, iyo go'aanka oo ka mid ah shuruudaha shuruudaha - oo ka mid ah waxa uu ka mid ah wax soo saarka ah ee "data management suite" ah oo ka mid ah IBM's DFSMS-ga integrated pathway. CA Disk Backup and Restore Waayo, ma ahaatee, waa mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. Open systems in the 1980s: UNIX grows up, libraries get robotic (and HSM becomes a “stack”) As UNIX spread through labs, engineering shops, and early enterprise environments, HSM stopped being a single platform feature and turned into a vendor ecosystem: file services up top, media automation underneath, and a policy engine trying to keep disk from being treated like an infinite resource (spoiler: it wasn’t). HSM ayaa ka dhigi karaa in ay ka mid ah dhismaha. Robotic tape libraries iyo jukeboxes optical waxaa laga yaqaan 'infrastructure' ah, oo ay ku saabsan science-fair props. Media managers and volume services start to matter , because someone has to track cartridges, drives, mounts, and “where the heck did that volume go?” as much as the file system This is where EMASS shows up as a true “HSM stack” EMASS FileServ waa layer shahaado HSM / file-space-ka ah, xafiiska ah oo ku habboonay xayawaanka file-level iyo xayawaanka "doodaan sida ay ku yaalla" ah. Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Markaas ah: FileServ waa "HSM brain for files", VolServ waa "robot wrangler for media." Sida loo yaqaan "Archiving as a File System" waxaa ka mid ah HSM-ka. ADIC AMASS dhismaha shuruudaha xawaaraha ka hor si aad u isticmaali karaa macluumaadka ugu horeysay oo loo isticmaali karaa for disk - by presenting archive behind a file system-like abstraction over tape/optical libraries. Key point: In the 1980s open-systems world, HSM becomes a layered architecture: file services + movers + volume/media management + robotics. That blueprint is basically the ancestor of today’s “lifecycle + object + cloud” designs—just with more SCSI and fewer REST APIs. The 1990s supercomputer/HPC era: HSM becomes “mass storage” (and gets serious) HPC ka dhiso HSM si ay u adeegsanay "disk space janitor" si ay u dhismaha data full-throttle.When users are running multi-node jobs that can chew through terabytes like popcorn, HSM waa in ay ka mid ah si ay u dhismaha xafiiska - waa in ay u dhismaha computing without turning the storage budget into a crime scene. (High Performance Storage System) waa mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid IBM HPSS Qalabka HPC-era HSM ayaa loo isticmaali karaa Shuruudaha Parallel: shuruudaha badan oo ku yaalaa dhismaha dhismaha ah si ay u qiyaasta dhismaha dhismaha dhismaha ah (wax yar oo ka mid ah dhismaha dhismaha dhismaha ah). Shuruudaha bandhigga High: disk cache / layer cajiib ah oo ka mid ah oo ku habboonay si ay u adeegsanay macluumaadka iyo I / O. Taageerada metadata + kharashka kharashka: nidaamka waa in la heli karaa files kandidaad ka badan, si ay u habboonay oo dhan. Workflow integration: batch schedulers, project spaces, scratch vs. archive, and predictable recall behavior—because science runs on deadlines and coffee. Representative products in the 1990s HPC “mass storage” lane — described in HPC proceedings as acting like a virtual disk, automatically migrating files to cheaper storage via a programmable migration strategy. NSL UniTree SGI DMF (Data Migration Facility) – waxaa laga yaabaa sida nidaamka dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha. EMASS FileServ / VolServ - waxaa lagu soo bandhigay oo dhan ee shaqada ee warshadaha NASA sida caawin dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha. (NASA Ames in-house HSM) — an internal HSM effort that NASA evaluated directly against commercial alternatives like FileServ, DMF, and UniTree, which tells you how strategic (and competitive) this space was in the 90s. NAStore Why this era matters: Sida loo yaqaan "HSM" waxay ku yaqaan "IT housekeeping" oo ku yaqaan "core scientific infrastructure" - oo ka mid ah HPC, wareegga waa mid ka mid ah dhismaha. Late 1990s through the 2010s: stubs, DMAPI, clustered file systems, and enterprise sprawl This is the era where HSM stopped being a niche “supercomputer thing” and turned into something normal people had to run—across messy fleets of UNIX, Windows, tape, disk, and (eventually) object targets. The big shift wasn’t a new idea. It was integration: better file-system hooks, better policy engines, and storage platforms that finally accepted they were part of a bigger workflow. This is the era where HSM stopped being a niche “supercomputer thing” and turned into something normal people had to run—across messy fleets of UNIX, Windows, tape, disk, and (eventually) object targets. The big shift wasn’t a new idea. It was integration: better file-system hooks, better policy engines, and storage platforms that finally accepted they were part of a bigger workflow. UNIX and friends: DMAPI, policy engines, and real automation In UNIX, HSM waxaa ka mid ah sida nidaamka file iyo dhismaha clustered/parallel ayaa ka soo dejisan in ay ka soo dhawriyaan HSM oo ka mid ah oo ka mid ah: Nala soo bandhigay namaha (tusaale ah ee file ah, ma ahaatee "host this opinion") Qalabka dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha ah ee dhismaha Coordinated movers (so recalls/migrations don’t fight each other) Waxaa laga yaabaa in ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah. IBM Storage Scale / General Parallel File System (GPFS) is a good example of the “policy engine becomes first-class” pattern—rules select files and trigger actions like placement and migration. And when you bolt it to IBM High Performance Storage System (HPSS) via the GPFS HPSS Interface (GHI), you get the late-90s/2000s reference architecture: file system emits events, a daemon handles them, movers push/pull data to deep archive under Information Lifecycle Management (ILM) control. Other HSM products that fit this UNIX/clustered file-system phase: — classic UNIX HSM architecture (stubs, policies, movers, tape integration) that was widely used in research/media environments. Sun SAM-QFS / Oracle HSM SGI DMF (Data Migration Facility) - waaweyn ee HPC iyo "big archive" shops; file-centric HSM la soo bandhigay mover ah. (TSM) for Space Management (later Spectrum Protect for Space Management) — enterprise-grade HSM-style migration/purge/recall integrated with broader data protection tooling. IBM Tivoli Storage Manager — in media/entertainment and big unstructured workflows, it became a go-to “keep it online-ish, but pay archive prices” solution. Quantum StorNext Storage Manager Lustre ecosystems HSM - By the 2000s, nidaamka file parallel sida Lustre ka dhismaha dhismaha "hot" ee nidaamka file iyo dhismaha "cold" ee ka mid ah connector HSM. Windows: HSM grows a second head (and a lot of opinions) Windows HSM is absolutely real, but it has always had more “please don’t poke my file handles” energy than UNIX. (OTG → Legato → EMC era) is the canonical Windows HSM story: stubs/placeholders on NTFS, automatic migration of inactive files, and transparent recall. (Same core behavior as UNIX HSM, just with more ways for apps and scanners to accidentally recall your archive.) DiskXtender IBM HSM for Windows waa mid ka mid ah mid ka mid ah mid ka mid ah: HSM for New Technology File System (NTFS) oo ka mid ah dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha. Enterprise sprawl: HSM ideas leak into “adjacent” domains Ka dib ka mid ah 2000s ka mid ah 2010s, wax soo saarka sidoo kale ka soo dejisan wax soo saarka HSM-ka ah oo ka mid ah macluumaadka non-traditional: E-mail/groupware archiving (ex: Zarafa Archiver) — macluumaadka lifecycle waxaa loo isticmaali karaa macluumaadka mail. Compliance + tiering platforms (ex: ) — rule-based movement plus retention behavior. PoINT Storage Manager Heterogeneous data movers (e.g.: Moonwalk) - "waxinta data soo saarka badan" ee nidaamka file mixed/object/tape. Zarafa Archiver PoINT Storage Manager Haku Not all of these are classic file-system HSM. But they’re clearly in the same evolutionary branch: policy-driven movement, long-term retention, and keeping access predictable while storage gets cheaper per terabyte and more complicated per environment. If you want, I can also add a tight one-paragraph “what changed operationally” closer for this section (stub storms, recall throttling, namespace governance, and why clustered metadata made the whole thing less fragile). 2010–2020: Policy Engines, Cloud Tiers, and the Death of “Just Buy More Disk” NAS / file platforms that added object/cloud tiering (2015–2020) — policy-based movement/tiering from OneFS (NFS/SMB) to object targets like S3/Azure (and OneFS-to-OneFS cloud). This is basically “HSM for NAS admins who don’t want to say HSM.” Dell EMC Isilon / PowerScale CloudPools — ONTAP feature that keeps hot data on SSD and tiers colder data to an object store (public or private), driven by policy. NetApp FabricPool Vendor-neutral policy engines for unstructured data (2013–2020) Komprise Intelligent Data Management — file analytics + policy-driven layering / "wax yar" ee data non-structured ka mid ah nidaamka storage (file iyo object). — policy-based NAS file migration/tiering; later versions explicitly talk about S3-compliant storage support, which makes it a good “bridge to object” entry in this era. Data Dynamics StorageX StrongLink — macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka maclu Tape gets modern interfaces (2015–2020) IBM Spectrum Archive (LTFS) - "tape as a file system" qiyaastii waa mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. QStar Archive Manager + Network Migrator – waxay ku yaalaa archive ka dib ka mid ah file shares ama buckets S3 iyo waxaa loo isticmaali karaa mid ka mid ah macluumaadka kala duwan si ay u soo saarka data kala duwan (tape/object/cloud). Atempo Miria – qalabka archiving/migration-ka sareeya ee dhismaha ugu weyn ee dhismaha ugu weyn ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha ugu horeysay ee dhismaha. Cloud-adjacent “stub & tier” services (late 2010s) Azure File Sync (Cloud Tiering) — soo saarka namaha ka mid ah wax soo saarka (saarka-saarka-saarka) iyo soo saarka file ka mid ah wax soo saarka oo ku saabsan warshad-saarka iyo warshad-saarka. — early 2010s example of “use cloud as the capacity tier,” long before everyone pretended they invented hybrid tiering. Microsoft StorSimple (hybrid storage appliances) On-prem S3 object platforms that leaned into lifecycle (2015–2020) These are good to mention as for modern HSM/lifecycle systems: Haku — lifecycle policies / auto-tiering patterns in S3-land. Cloudian HyperStore Scalability (RING / Artesca lifecycle tooling) - S3 lifecycle policy management wuxuu ku soo bandhigay sida platforms-objects la dhiso "HSM-like" automation. The 2020s: HSM doesn’t die — it gets absorbed into object and cloud semantics In 2020s, HSM waxay ka dhigi karaa. . Modern platforms increasingly treat tiering as a Markaad ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah. assimilated native capability Waxaa kale oo ka mid ah dhismaha ee Tani waxaa loo yaabaa , driven by Haku iyo . Same mission, different wardrobe. disk → nearline → tape hot → cool → cold → archive lifecycle rules storage classes API-first workflows What “modern HSM” looks like now (on-prem and cloud): transition based on age, tags, prefix, versions, or compliance rules. Lifecycle policies are built into object storage Qalabka shuruudaha cloud + qiyaasadaha shuruudaha waxaa laga yaabaa xawaaraha: shuruudaha waxay ku yaabaa in ay ku yaalaa "cold" iyo in ay ku habboonay (latency + cost). , often expressed as config, rules, or JSON—less “the one admin who knows,” more “repeatable automation.” Policy engines are everywhere the control plane shifted. Instead of POSIX stubs and DMAPI events, you’re dealing with . Recall isn’t “open() blocks for a bit.” It’s “restore job, wait window, then access.” Why this matters: object metadata, restore workflows, and billing-aware decisions Cloud & object: HSM becomes “lifecycle” This is where the big public platforms normalized the pattern: transitions objects between classes, including archival tiers. Amazon S3 Lifecycle Azure Blob lifecycle waxaa loo isticmaali karaa mid ka mid ah hot/cool/cold/archive. brings similar semantics to S3-compatible private clouds. Ceph RGW lifecycle + storage classes The punchline: macluumaadka lifecycle waa , with the bonus feature of “your finance team now gets to participate.” HSM by another name On-prem vendors meet that world halfway (and sometimes sprint into it) Inta badan oo ka mid ah "archive" ah oo ka mid ah HSM ka mid ah interfaces-object-native: : positioned as a modern scale-out approach aimed at the scaling pain points of older mass-storage / HSM architectures—policy, lifecycle, and massive namespace management without the classic bottlenecks. Versity ScoutAM / ScoutFS Qalabka ActiveScale Quantum: S3 object-oriented storage waxa uu ku saabsan "object-as-capacity-layer" designs, oo ka mid ah pattern-cold-storage-sharing ku saabsan semantics S3. Spectra Logic (StorCycle + BlackPearl): lifecycle/policy orchestration plus a object-facing deep-archive front door (wax ka mid ah tape-backed), oo waa mid ka mid ah HSM si ay u soo saarka ah API. : “deep archive + object semantics” approach—tape economics with modern access patterns, showing how the archive tier is increasingly presented as S3/object rather than POSIX-only. GRAU DATA XtreemStore Other 2020s “HSM-type” products worth name-dropping Haddii aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan tahay in aad u baahan yahay. File/NAS platforms adding object tiering (HSM baked into the filesystem) NetApp FabricPool Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qumulo / similar modern NAS platforms (varies by feature set, but the theme is “policy + tier target”) Policy engines that sit above storage (HSM becomes “data management”) , , -style tools that analyze, classify, and move unstructured data across heterogeneous targets (NAS ↔ object ↔ cloud ↔ tape gateways). Komprise StrongLink Data Dynamics Tape/object gateways and archive orchestration , , and similar “front end the archive, automate the moves” stacks that bridge file workflows into object/tape-backed retention. QStar Atempo **So no—HSM waxay ku yaalaa. \ Waxa uu ku yaalaa in la yaqaan "HSM" marka "Lifecycle Management" waa sida loo yaabaa in aad ku yaalaa slide-deck oo aan la yaabaa. How parallel and clustered file systems supercharged HSM Sida loo yaqaan "parallel and clustered file systems" waxaa loo yaqaan "HSM" HSM-ka Classic waxaa loo isticmaali karaa ... ka dib markii ay u isticmaali karaa. model-ka ugu horeysay ayaa loo isticmaali karaa mid ka mid ah worldview-ka ah: server-ka file-ka, namespace-ka, set-ka movers-ka, iyo macluumaadka user-ka. Ma ahaatee, waxaa lagu soo bandhigiisa in ay ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah. Haku Waayo, in ay ku saabsan HPC iyo macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka macluumaadka: The classic HSM bottlenecks (a greatest-hits album) HSM is fundamentally metadata-driven. You can’t migrate what you can’t , and you can’t recall safely if multiple clients disagree about state (“online,” “offline,” “partial,” “staged,” “stubbed,” etc.). Metadata coordination pain: find Shuruudaha wax soo saarka: wax soo saarka ah ee wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax soo saarka wax saarka wax soo saarka wax soo saarka. Taageerada mover single-node: dhismaha ugu horeysay ayaa sidoo kale ka mid ah ka mid ah macluumaadka mover. That is cute until your computer can read faster than your movers can stage. “last access time” is a terrible policy input when 2,000 nodes touch a file once each in a burst. Congratulations, your HSM policy just got gaslit by parallel I/O. Distributed access patterns the policies weren’t built for: Parallel and clustered file systems didn’t magically “fix” HSM. What they did was by giving it the primitives it always needed. turn HSM from a fragile add-on into a native capability What clustered/parallel file systems changed 1) A real shared namespace (one truth, not 50 interpretations) In a clustered file system, clients don’t each maintain their own fantasy about file state. There is one namespace, one set of attributes, and one consistent view of whether data is resident, stubbed, migrated, or staged. That matters because HSM is basically a : state machine Is the file resident? Is it partially resident? Is there a stub? Is it in recall? Is it pinned? Ma rabtaa in ay ku saabsan migration? Clustered file systems make that state . authoritative 2) Centralized policy evaluation at scale Shuruudaha HSM waa mid ka mid ah kharashka nidaamka si ay u adeegsanayo wax soo saarka ah: scan metadata select candidates execute actions track results Marka loo isticmaali karaa macluumaadka macluumaadka, macluumaadka macluumaadka waxaa loo isticmaali karaa mid ka mid ah macluumaadka macluumaadka macluumaadka iyo macluumaadka macluumaadka. IBM Storage Scale / GPFS waa mid ka mid ah: macluumaadka macluumaadka waxaa loo isticmaali karaa macluumaadka macluumaadka macluumaadka iyo ka mid ah macluumaadka macluumaadka macluumaadka. across storage pools, not “hope the right server runs the right script.” evaluate → select → act 3) Distributed movers (throughput scales with the cluster) Once you stop treating movers as a couple of “special servers,” you can scale them: Muuqaalka more parallel streams Qalabka ugu fiican bandwidth fewer hot spots In HPC, this is everything. If your archive tier can’t stage fast enough, the compute nodes sit idle. That’s not an IT problem—that’s a “we’re lighting money on fire” problem. Qalabka Qalabka Qalabka Qalabka Qalabka : you can rate-limit recalls, schedule migrations in off-peak windows, and avoid letting one project’s workflow melt the system. throttling and fairness 4) Better event hooks and workflow integration The other major improvement is —HSM responding to , not just periodic scans. event awareness what users do DMAPI-style event models (where the file system generates events like open/read on migrated files) let HSM do: Shuruudaha dhismaha (“you touched it, we will stage it”) controled recall (xaabinta, gaarka, priority) (detect hot bursts vs long-term reuse) smarter policy This is where the system becomes operationally sane: you stop relying solely on cron-like sweeps and start reacting to real access patterns. The “true hierarchy” pattern: file system + deep archive integration Once you have clustered metadata + policy + events, you can build cleaner hierarchies where the file system is the user-facing layer and the archive system is the deep tier. Sidaa waxaa laga yaabaa in la pattern demonstrates: GPFS loo soo saarka DMAPI, daemon event waa loo isticmaalaa, iyo movers dhismaha go'aansho / go'aansho under an ILM framework. In practice, GPFS provides the namespace and policy control plane, while HPSS provides the deep archive and tape-scale logistics. GPFS/HPSS Interface (GHI) HPSS What this enabled in the real world (the part people actually care about) Filesystem Parallel/Clustered waxay ka caawinayaa HSM ka badan. : less fragile Fewer “who owns this file state?” inconsistencies Better control of recall storms (queueing + throttling + prioritization) Policy engines that operate across the whole namespace A path to scale bandwidth by scaling movers and network, not by begging one server to work harder And that’s why HSM survived into the 2020s: once clustered platforms made policy + metadata + movers coherent, HSM stopped being a bolt-on and started being a —even when the backend tier became object storage or cloud instead of tape. foundational pattern UNIX vs Windows: same goal, different pain UNIX vs Windows: same goal, different pain Sida loo yaabaa, UNIX iyo Windows HSM waxay ku dhigi karaa mid ka mid ah: . In practice, the two worlds evolved different mechanics—and different failure modes—because their file semantics and application ecosystems behave very differently. keep the namespace “whole,” push cold data to cheaper tiers, and recall it when needed UNIX HSM: predictable semantics, better hooks, fewer surprises (usually) UNIX-style HSM tends to work well because it can lean on a few friendly realities: 1) File system event models and hooks Macluumaadka UNIX ayaa ka horumariyo in ka mid ah "file this was touched" integration points. event models where the file system can emit events when a process opens/reads a migrated file. That enables a clean pattern: DMAPI-style user opens file file system notices it’s offline/stubbed HSM gets an event recall is queued/throttled file becomes resident again This is why UNIX/HPC HSM implementations often feel more “native” to the platform: the recall path can be tightly coupled to file system behavior instead of being a bolt-on filter driver. 2) “Stub + recall” fits POSIX expectations better POSIX-ish tools generally tolerate the concept that: stat() works even if the file’s data blocks aren’t local permissions/ownership behave consistently errors are interpretable (“file not resident,” “staging,” etc.) HPC workflows can be structured to (pre-stage) before compute runs stage explicitly Even when it’s annoying, it’s at least . UNIX admins can also script around it with relative confidence—because UNIX tooling is built on the assumption that storage might be slow, remote, or transient. Qalabka 3) Control knobs are aligned with ops realities UNIX/HPC HSM stacks ka mid ah in aad ka mid ah macluumaadka macluumaadka: Qalabka throttling prefetch/stage policies Pinning/Never-migrate Flag project-based policies by path, owner, group, filesystem This makes it easier to run HSM as part of a larger workflow rather than as an after-the-fact clean-up crew. Windows HSM: the same concept, but the ecosystem fights you Windows HSM waa shaqeeyey, laakiin waxaa laga yaabaa in ay ku habboon karo oo ah software waaweyn. —even when it’s hosted on a file server and the “disk” is a tape library in a trench coat. storage is always fast and always local 1) Applications often assume fast random access forever Inta badan oo ka mid ah Windows-ka (ka mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah: “File Open” oo ku yaalaa “instant read” lots of small random reads Qalabka Metadata no tolerance for multi-minute recall latency That’s rough when your “cold tier” is tape or deep archive. UNIX/HPC users expect “stage first.” Windows users expect “it’s a file, therefore it should open.” Those are not compatible religions. 2) The hidden villains: indexers, AV scanners, and ‘helpful’ background services Windows environments are full of well-meaning automation that touches files just enough to trigger recalls: crawling a share Indexing services Anti-virus waxaa la socdaan oo dhan oo aad u aragto doing “light reads” eDiscovery / DLP / compliance agents Backup / DR tooling xisaabinta iyo xisaabinta files In HSM land, "light touch" waxaa ka mid ah "call the entire file."This waa where administrators learn to fear anything that does recursive scans. 3) Backup software + stubs = confusion (unless you’re careful) Stub files and placeholders are central to Windows HSM. But backup systems can: back up the stub (useless) instead of the data (bad) trigger recalls to back up full content (worse: recall storm) mis-handle reparse points / offline attributes depending on vendor So Windows HSM almost always requires : explicit backup integration planning decide whether backups operate on the primary tier only Qalabka waxaa laga yaqaan backup to trigger recall. whether archived content is protected separately at the archive tier 4) “Transparent recall” is technically true… operationally messy IBM’s documentation for Windows HSM is very explicit that it supports —ee waa mid ka mid ah macluumaadka user. Shuruudaha waa in uu ku yaalaa in la xira: users iyo apps waa in la xira in la xira in la mid ah oo ka mid ah oo ka mid ah oo ka mid ah oo ka mid ah in Explorer. stubs/placeholders and transparent recall behavior Practical bottom line: where each platform shines UNIX HSM is usually best when: workloads are batch/HPC/media pipeline you can pre-stage or schedule recall policies can be aligned to projects, paths, and compute workflows clustered/parallel file systems provide strong hooks and metadata scale Windows HSM is usually best when: the goal is file-share capacity relief wax soo saarka waa mid ka mid ah mid ah wax soo saarka you can tightly control indexers/AV/backup behaviors the organization accepts that “archive tier” means “slower, sometimes a lot slower” What changes when cloud storage shows up? What changes when cloud storage shows up? Cloud doesn’t kill HSM. It . changes who’s driving Classic HSM lived in your data center: you owned the tiers, the robotics, the movers, the recall queue, and the “why is staging slow” war room. When cloud shows up, the into the storage service itself—and your “tiers” become with and . HSM control plane shifts upward storage classes lifecycle policies restore workflows In other words: the same game, but now the referee is also your invoice. 1) HSM becomes “lifecycle + class transitions” Instead of “disk → tape” being a local design choice, cloud platforms formalize the hierarchy as and let you define : classes transition rules (“after X days, move to cheaper tier”) Storage class transitions Shuruudaha caadiga ah oo ku yaalaa age/prefix/tags/versions (immutability, legal holds, object lock—depending on platform) Retention & governance hooks This is textbook HSM behavior, just expressed as platform policy. For example, can automatically transition objects to archival tiers, and can transition blobs across hot/cool/cold/archive in a similar rule-driven model. Amazon S3 Lifecycle Azure Blob lifecycle management 2) “Recall” becomes a restore workflow (and it’s no longer just “slow”… it’s a process) In classic HSM, recall usually meant: queue the request, fetch from tape, stage to disk, let the app proceed. The pain was mostly time. In cloud, recall is often an explicit with: restore operation (API call / lifecycle action / console workflow) A restore request (hours can be normal in archival tiers) A waiting period (sometimes you specify how long it should be restored) A temporary accessibility window Cudarada Cudarada Cudarada Cudarada Cudarada Cudarada Cudarada So your old “tape delay” becomes . It’s not just latency—it’s orchestration. S3’s lifecycle + archival tiers are a good example: you can transition objects into archive classes, but you also inherit the restore semantics and operational constraints of those tiers. a workflow dependency 3) Metadata and inventory suddenly matter a lot more In HSM-ka dhismaha, "Waa'aalo ah waa?" waxaa ka mid ah dhismaha mid ah. Object metadata / tags Prefixes Inventory reports Qalabka Analysis Versioning state Waayo, waxaa loo isticmaali karaa in ay u isticmaali karaa macluumaadka macluumaadka macluumaadka macluumaadka. Waayo, waxaa laga yaabaa in ay ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah. Haku 4) Billing becomes an HSM constraint (and sometimes the dominant one) Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Media adeegyada operational burden Qalabka Cloud: Qalabka Retrieval request cost (some archival tiers) early deletion penalties qiimeeyo / qiimeeyo qiimeeyo (wax yar oo ka mid ah qiimeeyo ah iyo off-cloud) API rate limits and per-request overhead Qalabka ugu horeysay ee loo yaabaa in ay ka mid ah wax soo saarka ah oo ka mid ah wax soo saarka ugu horeysay ee loo soo saarka. “Ma rabtaa in uu ku yaalaa, ama waxaan ku raaxaysaa in ka soo saarka ah?” “Can we stage locally and batch restores?” “Ma rabtaa, version, ama waxaan bixiyaan oo dhan?” Your archive tier is no longer a passive “cheap basement.” It’s an active financial instrument. 5) Hybrid becomes the default architecture Most shops don’t flip a switch from “HSM” to “cloud.” They end up with hybrid patterns: On-prem file system + cloud/object as capacity tier Cloud-native object + on-prem cache/edge Tape/object gateways oo ku yaalaa interface S3 sida ay ku salaysan tape economics This is exactly why modern vendors pitch “lifecycle management” rather than “HSM”: the tiers can be anywhere, and the orchestration spans multiple control planes. 6) Ceph RGW and S3-compatible ecosystems: cloud semantics without hyperscalers In Ceph RGW iyo macluumaadka kale oo ku saabsan S3-ka, ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah oo ka mid ah macluumaadka caadiga ah. iyo ku yaalaa by platform. policy is expressed in object terms The big operational shift (the part your app teams will absolutely notice) Cloud turns “recall latency” into a three-part problem: Time (wax yar) Money (Retrieval + request + posibly egress) (who triggers restore, how long it stays restored, what workflows depend on it) Process Sida loo isticmaali karaa, waxaa loo isticmaali karaa in aad u isticmaali karaa. about “what tier is this in?” In cloud, tier choice hits , and nobody likes surprises—especially the kind that show up as a four-figure line item labeled “retrieval.” Haku performance and budget at the same time Sidebar: Cloud HSM Anti-Patterns (a.k.a. how to accidentally finance your provider’s next yacht) Sidebar: Cloud HSM Anti-Patterns (a.k.a. how to accidentally finance your provider’s next yacht) Here are very common ways teams create iyo Sida loo isticmaali karaa in ay ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah: six recall storms retrieval bills Let’s just run a recursive scan.” Someone points an indexer, antivirus, DLP tool, or discovery crawler at an object-backed namespace (or file gateway) and it “helpfully” touches everything. If those touches trigger restores/reads, you’ve just scheduled a surprise mass recall. Treating archive like a slower version of standard storage Teams transition data to archive tiers and keep the same application behavior—random reads, lots of small GETs, frequent reprocessing. Archive tiers are not “cheap disk.” They’re a cost/latency contract with consequences. No restore orchestration (aka “YOLO restore”) Restores kicked off ad hoc by users/apps without queueing, throttling, or prioritization. Result: clogged restore pipelines, missed deadlines, and a bill that looks like a phone number. Life-cycle rules without lifecycle governance “After 30 days, shove it to Glacier/Archive” sounds smart until Legal needs it tomorrow, or the workflow still references it weekly. Lifecycle must align with , not wishful thinking. actual access patterns Ignoring minimum storage durations / early deletion penalties Some archive tiers have minimum retention periods. Transitioning too aggressively (or deleting/overwriting too quickly) can trigger charges that make your “savings” evaporate. Egress amnesia The archive data might be cheap to store, but pulling it out—especially cross-region or out of cloud—can be expensive. If your plan is “restore everything back on-prem for processing,” congrats, you’ve invented a budget bonfire. One-line fix mindset: Trate cloud archive sida tape la API: plan restores, batch reads, control scanners, and make lifecycle decisions based on measured access—not optimism. What changes as we move from POSIX to Object Storage? Sidee waxaa laga yaqaan 'POSIX to Object Storage'. Sida loo yaqaan 'HSM' waa mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. where everything is a Marka aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay in aad u baahan yahay. Marka: The , iyo "call" waa mid ka mid ah qaadi ah workflow. POSIX world file namespace is optional API waa interfaces Markaad ka mid ah dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha, dhismaha. POSIX-first HSM (classic): “keep the illusion alive” Traditional HSM is built around the POSIX contract: Files iyo directories waa experience user. Pathnames waa idinka (move / rename waa mid ah) are enforced through the file system Permissions/ownership Qalabka loo isticmaali karaa open/read/close iyo u baahan tahay in ay ku saabsan data. So classic HSM optimizes for one thing above all: preserve the illusion that the file is still “right there.” How it does that the file still exists in the directory tree, but the payload has been migrated. Stubs/placeholders: touch the file, HSM stages it back (often via file system hooks/events). Transparent recall: path patterns, uid/gid, project directories, file size, atime/mtime, “don’t migrate these extensions,” etc. Policies are file-centric: The strengths: Shuruudaha macluumaadka ah ee app (in theory) Users stay productive in familiar tools Works beautifully for workflows that are mostly sequential and predictable Qiimeeyaasha: Stub storms (indexers, crawlers, AV, qalabka backup) Metadata-heavy scanning at scale “Transparency” waxay ku yaalaa riskiisa shaqeeyaan oo aan ku saabsan wax kasta oo dhan. Object-first lifecycle (modern): “stop pretending, start governing” Object storage isn’t trying to be a file system. It’s an Sida loo yaqaan identity waa: API-driven key/value store with metadata (often a prefix-based pseudo-directory) Bucket + key Plus tags/metadata Plus versioning state Qalabka Qalabka Qalabka Qalabka Apps waa in la "open() file". , often in chunks, often repeatedly, often via distributed clients. GET an object What lifecycle looks like in an object world Motors lifecycle waxaa loo isticmaali karaa: (days since creation/last modified) Age (“everything under this keyspace”) Prefix Tags (“Project=NDNP”, “Retention=7Y”, “LegalHold=True”) Warshadaha (wax yar, warshadaha warshadaha) Markaas ka mid ah dhismaha, waxaad ka heli karaa: (hot → cool → cold → archive) Storage class transitions Shuruudaha wax soo saarka ah ee shuruudaha wax soo saarka ah ee shuruudaha wax soo saarka. Sometimes copy-on-restore patterns (wax yar oo dhan) Shuruudaha Object waa ka mid ah "calling transparent" iyo "data governance stateful". The big differences that matter operationally 1) Namespace identity changes (paths vs keys) In POSIX, the path is —Renaam iyo go'aansho waa mid ka mid ah oo ka mid ah dhismaha. everything The "directory" waa mid ka mid ah codsiga key prefix. “Rename” waa mid ka mid ah copy + delete (wax yar) identity and policy control tend to ride on , not directory trees tags/metadata 2) Metadata becomes your control plane Classic HSM waxay isticmaali karaa file attributes iyo file system metadata scanning. Object lifecycle relies on: object metadata / tags Qalabka Inventory analytics on access patterns, size distribution, version churn If you don’t invest in , lifecycle becomes guesswork—and guesswork becomes cost. inventory + visibility 3) Access patterns shift from stateful IO to stateless requests Haku: Open / Read / Write / Khariidadda wax soo saarka ah metadata madadaalo Sequential Streaming waa caadiga ah ee HPC / media Qalabka IO: stateless GET/PUT retries are normal Customer-ka ugu horeysay ee Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Sida loo yaqaan "Remember Storm" waxaa loo yaabaa. In Object Land, waxa ay ka mid ah "wax ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah. 4) “Recall” changes meaning Sida loo isticmaali karaa HSM: Recall = faahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaahfaah In object lifecycle: “recall” might mean: from an archive class for temporary access restore into a hotter class permanently rehydrate into a new location/work bucket for processing copy into a POSIX cache via a gateway materialize Waxaad ka soo xiriir in la soo xiriir in la soo xiriir oo la soo xiriir. . workflow timing + cost + durability + governance 5) Security and governance models shift Shuruudaha POSIX waxaa loo yaqaan 'File System Layer' (UID / GID, ACLs). Shuruudaha Object waxaa ku saabsan: Qalabka Policy bucket/key ka mid ah ACLs object (wax yar oo ku saabsan platform) tagging/attribute-based controls Sida loo isticmaali karaa, waxaa loo isticmaali karaa "only this team can recall/rehydrate" ama "this dataset can't leave cold tier". 6) Hybrid gateways reintroduce POSIX—but with new failure modes Qalabka badan oo loo isticmaali karaa: File Gateways ka mid ah Objects Qalabka Qalabka Qalabka S3 Qalabka caching oo "ku salaysan sida NAS" Markaas oo dhan, waxaa loo isticmaali karaa mid ka mid ah macluumaadka dhismaha: Qalabka POSIX waxaa loo isticmaali karaa sida loo yaqaan 'all is local'. Shuruudaha dhismaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha ugu horeysay ee shuruudaha. Waxaad ka soo xiriir storms + request storms + surprise bills Net effect: HSM becomes less about illusion and more about governance Classical HSM waa badan: “Make the file system pretend the data is nearby.” Qalabka dhismaha dhismaha dhismaha dhismaha dhismaha “Manage where data lives over time, and make access a controlled workflow.” Transparency isn’t the default goal anymore— predictability is. What “winning” looks like in the 2020s Qalabka ugu fiican ee shuruudaha waa: Qalabka dhismaha iyo dhismaha dhismaha iyo dhismaha dhismaha iyo dhismaha dhismaha Shuruudaha dhismaha + dhismaha (si kastaba haweenka waa ku habboon ah, haweenka haweenka) Integraas ka mid ah macluumaadka workflow (gaarka, warshadaha, dhismaha, xawaaraha xawaaraha) Shuruudaha Access Hybrid (Caching/Gateways iyo Garde Rails, oo "surprise restore roulette") Waayo, waxaa laga yaabaa in ay ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah. So where is HSM headed next? Sidee waxa uu ka mid ah HSM? HSM waa mid ka mid ah "a new tier". . a new operating model Waayo, HSM waa mid ka mid ah mid ka mid ah : si ay u qaadi file-ka dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha dhismaha Markaas ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah. QEEBE how decisions are made, how they’re enforced, and how you prove they’re working Sidaa waxa uu ku yaalaa. 1) Policy-as-code: fewer tribal rituals, more repeatable engineering The future HSM stack looks less like “a GUI full of rules nobody dares touch” and more like : infrastructure code Shuruudaha ku yaqaan 'Rules Declarative' (wax ka mid ah Git) Versioned, peer-reviewed, and traceable (“who changed this and why?”) Tested against real datasets or synthetic inventories (“what would this migrate if we turn it on?”) Shuruudaha iyo shuruudaha iyo shuruudaha Sida loo yaqaan 'HSM Policy' waxaa loo yaqaan 'HSM Policy'. Si aad u isticmaali karaa sida tusaaleyo config one-off, sidoo kale aad qaadi karaa: production traffic rules Mashaariinta Mashaariiska Qalabka Qalabka Qalabka Qalabka Qalabka Waxaa kale oo ka mid ah wax soo saarka ah oo ka mid ah wax soo saarka iyo wax soo saarka. Policy-as-code waxay ku yaalaa HSM ka "admin craft" . operational engineering 2) Observability becomes non-negotiable (because lifecycle without visibility is just gambling) HSM Classic waxaa ka mid ah ka mid ah dhismaha dhismaha ah iyo dhismaha dhismaha dhismaha. : telemetry Ma rabtaa in aad u aragto (si kasta oo dhan): Inventory: dhismaha, dhismaha, dhismaha by tier / class Heat: Frequency Access, Access Recent, dhismaha burst Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Shuruudaha Mover: bytes / sec, concurency, garoonka Shuruudaha Qalabka: Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka: "Saacad oo ka mid ah waxaa laga yaqaan 'policy' iyo oo ka mid ah waxa ay ku salaysan?" Waxaad ka heli karaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa in ay ku yaalaa. The new rule is: . tiering decisions must be telemetry-driven, not vibes-driven 3) Workflow integration: “recall” becomes an orchestrated event, not an accident In HSM classical, isticmaalka la tusaaleyo file iyo nidaamka dhismaha. The future looks like : event-driven orchestration Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Priority (wax ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah) Qalabka dhismaha waaweyn ee dhismaha dhismaha Window pre-stage oo ku saabsan Job Schedulers (HPC) or batch processing dhismaha automatic (“wax yar”, “data available”, “recovery scheduled”) Markaas ka mid ah "callback transparent", go'aanka waxaa la soo bandhigay : predictable recall Qalabka Latitude Qalabka Qalabka Qalabka workflow The systems that win will treat “getting data back from cold tier” like a first-class pipeline step—not an unpredictable side effect of someone clicking a folder. 4) Business signals become policy inputs (ILM finally earns its keep) Sida loo yaqaan ILM waxay ku yaalaa filosoofiyada slide-deck iyo waxaa laga yaqaan 'praktika'. Qalabka dhismaha waxaa laga yaabaa in ka mid ah Markaad ka mid ah wax soo saarka: business events Project shuruudaha → shuruudaha soo saarka / archive Publication/release → replicate + retain inta badan Shuruudaha Laakiin → lock / block deletion / change tiering behavior Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka Qalabka waxaa laga yaabaa in ay ka mid ah wax soo saarka ah oo ka mid ah wax soo saarka ah. Shuruudaha qiyaastiisa → qiyaastiisa qiyaastiisa iyo re-encrypt/re-tag Sida loo yaqaan 'HSM: policies driven by Markaas ka mid ah timestamps. meaning 5) A shift in what HSM optimizes for: from “capacity relief” to “governed lifecycle” Qalabka ugu horeysay ee HSM waa: “wax yar ka mid ah 40% oo ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah ka mid ah” Qalabka dhismaha HSM waa: "We can prove where data lives, why it is there, what it costs, how fast we can get it back, and how long we must keep it" “Saacad ka mid ah ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah mid ah mid ka mid ah. "We can meet retention / immutability requirements without breaking workflows" "We can predict and cap retrieval spending" (Haddii loo yaqaan "Haddii loo yaqaan 'CAP Retrieval spending"). Sida loo yaqaan "Make the disk look bigger" iyo "Make the disk look bigger". . govern data over time across multiple storage domains Bottom line Qalabka Line Ilm waa “Why”. HSM waa mid ka mid ah “how”. Sida loo isticmaali karaa, HSM waxaa loo isticmaali karaa Sida loo yaabaa in la soo bandhigay iyo Waayo, waxaa laga yaqaan 'File Stubs'. policy-as-code + observability + event-driven workflows lifecycle engines object semantics Sida loo yaqaan "HSM" waa mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ka mid ah mid ah mid ka mid ah mid ka mid ah mid ka mid ah.