Premium Content

Access "Disaster recovery planning on a budget"

Published: 29 Oct 2012

RPO/RTO impact of potential DR solutions In this example, introducing replication and increasing communications bandwidth to support higher volumes of data could further reduce recovery point objective (RPO) to 12 hours. By upgrading from a warm site to a hot site, it would be possible to decrease recovery time objective (RTO) from under two days to about six hours. Source: GlassHouse Technologies Recently, I received a call from an IT manager responsible for disaster recovery (DR) for a large organization. He was reasonably certain that the DR test that was scheduled in a few months would fail. He was hoping to identify and resolve some of the problems. More than any other category of IT activity, DR strains the planning and operational capabilities of an IT organization. A DR infrastructure typically is expensive to implement, has low utilization and requires tasks to be accomplished in a time-critical manner. A careful analysis of the trade-offs that you can tolerate--with an understanding of what resources you can commit--should help you get closer to an... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

What's Inside

Features

More Premium Content Accessible For Free