The most recent Amazon Web Services outage left customers (and rival cloud providers) blaming Amazon. Instead, CIO.com columnist Bernard Golden says, everyone needs to accept that cloud computing is not immune to failure. Fortunately, a key advantage of the cloud – cheap, easy redundancy – will help mitigate the risk of an outage.
It used to be that many managed service providers—especially those targeting SMBs—were reluctant to present clients with IT service-level agreements (SLAs).
The smartest way to think about disaster is in terms of when, not if. The object of the game is to mitigate risk as much as is feasible, hope for the best, and prepare for the worst.
Establishing baselines is essential when it comes to assessing risk, managing disaster recovery, stopping loss, and so forth, no matter how big the database or how critical the application.
When formulating a disaster recovery plan, no matter that you are starting from scratch or taking over from another DBA, it is critical to fully understand the business plan and the application’s need for availability and service level. You thus need to establish the tolerance level for your enterprise or service to be without access to data and databases for a given time. In other words, how long do you have after a database goes offline, before the business begins to suffer serious harm? Many database or online transaction processing (OLTP) system clients do not understand their needs, so establishing a baseline is one of the most important exercises in a data center.
As budgets tighten, companies are under increased pressure to not only make smart investments but also put safeguards in place to make sure those investments pay off. Managed network services is one area where many companies are investing.