What CIOs can learn in the wake of a major IT outage
The impact of system outages brings to light the stark reality that as cloud continues to evolve, there are serious challenges to its true resiliency to withstand unforced errors.
The impact of system outages brings to light the stark reality that as cloud continues to evolve, there are serious challenges to its true resiliency to withstand unforced errors.
A single hour of IT related downtime costs Australian businesses between $500,000 to more than $10 million.
Studies in innovation suggest that some of the best ideas and solutions to problems are generated by looking at practices outside of one’s own area of work. There’s a tremendous opportunity for CIOs to learn better practices from their counterparts in other areas of the business.
Last week, North Korea's sole Internet link with the rest of the world went down for about three hours.
Telstra has come under fire for maintaining its premium pricing despite a recent string of network outages.
Troubleshooting servers is a fine art, but there are some methods and tips to get things running smoothly, quickly and easily. ITIL methodology delves into how to troubleshoot a server or a related issue more deeply, but the general theme is to narrow down the problem as quickly and efficiently as possible. Take a step back and think about how to logically resolve an issue during an outage. For example, if a user complains that they can’t access something, find out if other users have the same issue, eliminating the possibility that the problem is localized to a single end-user device.