The Floppy Problem

Floppy

Remember putting in floppy, after floppy, for literally hours, just to get something installed? Think that was silly, how did you feel after backing up your 20 MB system in 1.44 MB bites (pun intended) for so long, when did you finally give up? When you got your first 100MB drive? You could ruin a weekend trying to restore that. Eventually the pain of it all makes you change your media platform (also a pain and expensive) and wait for the problem to creep back, at twice the scale of challenges, as the previous time. The floppy problem.

How do we adress this problem today, as we are regularly facing terabytes worth of data a day, sometimes just from the system logs? Have we calculated the cost of ‘pushing the floppy’ for our system data, and can you define when that number exceeds what the business is worth?

*We haven’t even got to the business data storage, and you can bet that is bigger, and already well out of your control. When was the last time you confirmed how long a restore would really take? Do you scale your storage with the changes in business? That also means being able to cutback on costs when demand for service is down. Have you considered the benefit to other services, when this fundamental resource to the business of computer becomes a service you pay for use, and nothing more?

Are you really prepared for what Big Data means? It’s not about getting more storage space, it’s also about making the data available, actionable, and ultimately valuable.

Jump To