It’s 3 a.m. and your e-commerce site is down. You don’t know about it until you awake at 6 a.m.—OK, 7 a.m.
It turns out to be an issue in your cloud service, and you spend a few hours to fix the remote servers.
As with power-cycling the Wi-Fi router at home, things return to normal afterward.
All in all, you were down for six hours. No biggie—except that you lost a half million dollars in revenue, and the cost to your reputation is estimated at $5 million.[ The cloud storage security gap—and how to close it. | The InfoWorld Deep Dive: How to make document sharing really work in Office 365. ]
When people talk about such situations, what I hear is that they lack management.
Systems fail, both cloud-based and on-premise—that’s a given. What also should be a given, but often is not, is having the ability to correct issues or prevent them entirely.
For cloud systems, that takes a good understanding of cloud-management best practices and tools.To read this article in full or to leave a comment, please click here