|
|
 |
| Posted: |
23 Apr 2008 |
| Published: |
01 Apr 2008 |
| Format: |
HTML
|
| Length: |
6
Page(s) |
| Type: |
Journal Article |
| Language: |
English |
|
ABSTRACT:
In the last five years, data recovery technologies have been introduced that let users recover data to almost any desired previous point in time, shorten recovery times to minutes for even very large data sets and minimize the amount of storage capacity required for data protection tasks. But there"s a class of apps for which data recovery by itself isn"t sufficient. They require recovery of data and of the app itself in the most automated way possible. The ultimate objective for any recovery operation is to keep the business running; in the case of an application outage, lessening its impact on revenue or customer service is critical. The key recovery metrics are recovery point objective (RPO) and recovery time objective (RTO). It"s therefore important to understand what the recovery requirements are for each app before an appropriate solution can be chosen.
|
 |
AUTHOR:
Eric Burgener
|
|
|
|
BROWSE RELATED RESOURCES:
Clustering | Data Recovery | Data Replication | Fault Tolerance | High Availability | Microsoft Exchange | RPO | RTO | Storage Appliances | Storage Replication |
|
View All Resources
sponsored by Storage Magazine |
 |
|
|
|
Cramsession Research Library Copyright © 1998-2008 Bitpipe, Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. TechTarget · 117 Kendrick St · Needham, MA · 02494
Use of this web site constitutes acceptance of the Bitpipe Terms and Conditions and Privacy Policy. cramsession@bitpipe.com
|
