News from Uplogix, May 2012
Cloud & Local Managment Special Report |
|||||||||||
![]() |
Infographic: Be ready for the Cloudy forecastCloud is going to change customer expectations. New requirements are emerging, service levels are becoming more stringent and some of the time-tested strategies for managing costs and ensuring adequate service levels are being invalidated. Get some of the facts from the infographic based on the new Uplogix white paper. |
|
![]() |
Local Management: Imperative for the CloudHere is a peek at the new white paper from Uplogix: Meeting the Network Requirements of Cloud and Virtual Computing with Local Management. Don't let the catchy title fool you -- this paper could be the plot of a movie. There is the introduction of characters, introduction of the conflict, rising action, heroes, villains... but this story isn't yet complete. The script is still being written as Cloud adoption continues to rise, and as more and more physical systems are virtualized in datacenters around the world. You can almost hear the previews... |
|
![]() |
Limit risks and calculate the savings of Local ManagementWhen the network and dependent systems are down, orders can’t be placed, employees are less productive, and costly resources have to be diverted to fix problems. Traditional centralized network and system management tools—although good at collecting and reporting system data—still do not proactively fix problems once they occur. The result is that people are still required to perform most of the work over console servers on remote networks. Understanding the business case for remote network support is based on a risk/return calculation that takes into account the cost of downtime compared to the mix of resources spent to avoid downtime. The following chart shows that how much you spend on your resource mix doesn’t always equate to the lowest risk. |
|
![]() |
Ensure good configuration health before it's too lateHackers broke into a server for the State of Utah Health Department recently in what has been described as a "configuration error" or an "installed password that wasn't as secure as needed." The breach resulted in over 182,000 Medicaid and Children's Health Insurance Program members having their personal information stolen, with about 25,000 Social Security numbers being compromised. Those affected will be notified of the information theft. Configuration errors are often thought of in terms of downtime, with well known stats from folks like Gartner, calculating 80% of all downtime is caused by human-induced configuration errors and average hourly costs for business of $42,000. Amazon's hourly cost of a website outage was independently calculated at $350,000! But how much more expensive is a security breach than downtime? Potentially much, much more expensive. The Congressional Research Service concluded in 2004, that companies' stock prices dropped between 1%-5% in the days following the announcement of data loss. For the average NYSE corporation, that's shareholder loss of $50M - $200M (remember we're talking 2004 dollars). |
|
Uplogix Events
Uplogix Technical Training | May 15-17 |
||
Cisco Live | June 10-14 |











