The reason for the hype is that every business wants to reduce the impact of downtime when a disaster happens.
In addition to data loss, disasters may also lead to the permanent loss of physical infrastructure including IT infrastructure. At the same time, organizations are looking for a more cost-effective way to implement an easy-to-use disaster recovery service.
The costs of traditional recovery testing and exercising often constitute a significant portion of the annual disaster recovery budget (Gartner estimates this is $100,000 or more per exercise).
Old DR models are manual and are required to keep a physical run book that describes every outage and recovery. Today’s businesses need to determine where DRaaS can fit into the overall recovery portfolio. This means the server on the DR site has exactly the same configuration, BIOS, drivers, etc., as the physical server you are trying to recover at the production site. But as stated above, businesses needed to spend a large amount of capital costs to own the infrastructure that support DR services.


Today’s DR best practices must account for the growing complexity of IT, they must assume control over a diversity of platforms and, most importantly, they must provide guaranteed, fast and verifiable recovery through digital automation of the recovery run book. They should still test and run recovery exercises, properly train employees and work closely with vendors. Distinguishing applications that are mission-critical versus non-critical can help keep costs down and ensure the most valued applications never go down. This results in better predictability and greater likelihood of a fast and successful recovery – always the most metric. If a disaster does take down the infrastructure, fast recovery is critical and can dictate the difference between long-term success or failure. Even though most outages aren’t caused by a disaster, it is still best practice to keep recovery site out of the same region as your primary site. In fact, according to the National Archives & Records Administration in Washington, 93 percent of companies that lost their data center for 10 days or more due to a disaster, filed for bankruptcy within one year of the disaster. And even if you do, configuration drift is natural, as any change in primary site needs to be a mirror image to the other.


Recovery from a back-up tape that can literally take days to recover isn’t cutting it anymore.
Disaster recovery as a service (DRaaS) is particularly interesting as it helps IT address many of its biggest challenges.
Costs can run into the millions – if not tens of millions – and for many companies, those expenses are simply too high.
Customers can access computing only when they need it and pay on a monthly basis for what they use – typically this is just a fraction of the cost of a dedicated DR. With DRaaS, companies can have access to services that aren’t as expensive and still have faster recovery time, usually in a matter of hours or minutes. With DRaaS, the differences between the primary and secondary site can be abstracted (via technologies like converged infrastructure) and so customers can be freed from the synchronization handcuffs.



Home fires cast
Us rivers map quiz
Emergency supply list for home
Disaster recovery definition


Comments

  1. 09.09.2014 at 21:42:26


    Blizzard or if my vehicle broke down ten It proved equally i've thought about.

    Author: narko
  2. 09.09.2014 at 18:53:15


    That Russian scientists had been recruited by North Korea to assist truly imply homeopathic care.

    Author: ANTIKVAR