IOPSTOR

After its 100 TB RAID failed, a hospital chose IOPStor for storage it can rely on

The hospital's 100 TB RAID failed, and the company that supplied it would not repair it. IOPStor replaced it with a 100 TB NAS and a single compute node, protected by snapshots and a disaster-recovery system that keeps a copy offsite in the cloud.

HealthcareNAS

  • 100 TB on the IOPStor NAS, protected by snapshots
  • 0 downtime when the hardware fails, because the DR system takes over
  • 3 copies of the data, the NAS, the DR system and the cloud

Challenge

The hospital kept its data on a 100 TB RAID supplied by another company. When the RAID failed, that company declined to repair it. The data was recovered separately, and the hospital came to IOPStor for a replacement it could rely on. Looking at what had been installed, IOPStor found a system that had not been built to be reliable in the first place. The hospital's internal applications also ran on three separate servers, which meant three more machines that could fail.

Solution

IOPStor installed two systems in its place. A 100 TB IOPStor NAS holds the data. A single IOPStor compute node runs the hospital's internal applications as three virtual machines, replacing the three servers. IOPStor storage takes snapshots, so if something goes wrong the hospital can go back to the data as it was at an earlier point in time. Behind both sits a disaster-recovery system that backs up all of the data. If the hardware fails, the DR system takes over and the administrators are notified. The DR system also copies the data offsite, to the cloud.

Results

Three servers became one compute node, and the hospital's patient data now has four protections around it: snapshots to go back in time, a DR system that takes over when hardware fails so there is no downtime, notifications to the people who look after it, and a copy outside the hospital. For critical patient records, the hospital now has a system it can rely on.

If something fails what catches a failure now

Snapshots

Go back to the data as it was at an earlier point in time.

The DR system takes over

It holds a full backup of the data and takes over, so there is no downtime.

The administrators are notified

The system notifies the hospital's administrators.

Would your storage survive a failure like this one?

Tell us what you run today, and we will show you what would catch a failure and what would not.

Contact us

All Case Studies

01Post ProductionMedia

A post-production company grows from 8 people to 100 on IOPStor storage

Eight people passing files from hand to hand became a hundred across video editing, 3D and After Effects, working from IOPStor storage that gives each department its own pool and its own bandwidth.

02HealthcareNAS

After its 100 TB RAID failed, a hospital chose IOPStor for storage it can rely on

The hospital's 100 TB RAID failed, and the company that supplied it would not repair it. IOPStor replaced it with a 100 TB NAS and a single compute node, protected by snapshots and a disaster-recovery system that keeps a copy offsite in the cloud.

03HCIManufacturing

Six branches and a hundred users on one IOPStor hyper-converged system

A manufacturer whose branches each held their own copy of the data now runs six sites on a single IOPStor hyper-converged system, with every employee working inside it through VMware Horizon.