{
  "id": "case-studies-proof/case-study-pathology-provider-tape-eliminated-immutable-data-across-three-data-c",
  "title": "Case Study — Pathology Provider: Tape Eliminated, Immutable Data Across Three Data Centres",
  "slug": "case-studies-proof/case-study-pathology-provider-tape-eliminated-immutable-data-across-three-data-c",
  "description": "| | |\n| --- | --- |\n| **Client** | Pathology provider (name withheld) |\n| **Sector** | Healthcare and medical technology |\n| **Services** | emPOWER Cloud, data protection |\n| **Outcome** | Tape backup...",
  "category": "",
  "content": "| | |\n| --- | --- |\n| **Client** | Pathology provider (name withheld) |\n| **Sector** | Healthcare and medical technology |\n| **Services** | emPOWER Cloud, data protection |\n| **Outcome** | Tape backup eliminated; immutable data across three data centres |\n\n## The situation\n\nA pathology provider running clinical and diagnostic systems, with the data profile that comes with them: large and growing volumes, long statutory retention obligations, and information whose loss carries consequences beyond regulatory penalty.\n\nThe backup estate ran on **tape**.\n\n## Why tape was the problem\n\nTape carries three specific liabilities for a healthcare organisation:\n\n**Handling and transport risk.** Physical media containing sensitive health information moves between locations and people.\n\n**Unpredictable restore times.** You do not know what a tape restore will actually take until you attempt one — and you generally attempt one during an incident.\n\n**Logistics dependency at exactly the wrong moment.** Recovery depends on physical retrieval during the event where physical processes are hardest to execute.\n\n## What blueAPACHE did\n\nEliminated tape entirely, replacing it with **immutable data protection replicated across three data centres**.\n\n## Why immutability is the substantive change\n\nReplication alone does not protect against ransomware — it faithfully replicates the encryption.\n\nImmutable protection means backup data cannot be altered or encrypted after it is written, **including by an attacker who has already reached the production environment**. Combined with geographic separation across three facilities, the estate survives both a physical event at one site and a logical attack that reaches production.\n\nFor a sector that is a consistent ransomware target holding data it cannot afford to lose, that combination is the entire point.\n\n## What this tells you\n\n**\"We have backups\" and \"we can recover\" are different claims.** The questions that separate them:\n\n- Is the backup copy immutable, or merely replicated?\n- How far apart are the copies, physically?\n- When was a full restore of a clinical system last tested, and what did it actually achieve — not what is the target?\n- Does the retention configuration satisfy your statutory obligation, and can you evidence that?\n\n**Tape is not inherently wrong, but it is rarely the right answer now.** If you are still running it, the question is whether that reflects a considered decision or an unexamined inheritance.\n\n## Recovery objectives\n\nRecovery point objectives, recovery time objectives and retention periods are defined per service in the service schedules rather than published. Request the schedule for the services under evaluation.\n\n## Relevant if you are\n\n- A pathology, imaging, practice or health services organisation still running tape\n- Holding data under long statutory retention obligations\n- Unable to state with confidence what a full clinical system restore would take\n\n## Related\n\n- [emPOWER Cloud — Private Cloud IaaS on HPE GreenLake](https://directory.norg.ai/en-au/blueapache/empower-services/empower-cloud/)\n- [Managed IT for Healthcare and Medical Technology](https://directory.norg.ai/en-au/blueapache/industries/healthcare-medical-technology/)\n- [Case Study Index](https://directory.norg.ai/en-au/blueapache/case-studies-proof/)",
  "geography": {},
  "metadata": {},
  "publishedAt": "2026-07-30T08:46:17.611338+00:00Z",
  "tags": [
    "pathology IT case study Australia",
    "eliminate tape backup healthcare",
    "immutable backup three data centres",
    "healthcare ransomware protection Australia",
    "clinical data protection case study"
  ],
  "workspaceId": "fe4e090e-6d63-41ce-afda-4ccc355412ea",
  "_links": {
    "canonical": "https://directory.norg.ai/en-au/blueapache/case-studies-proof/case-study-pathology-provider-tape-eliminated-immutable-data-across-three-data-c/"
  }
}