Our engineers help customers define server, application and data recovery requirements to reduce costs while achieving desired service level objectives.
Imagine if your site was destroyed or your data center was flooded. The first thing one needs to think about when designing a recovery solution is, what applications need to be recovered for the business to operate immediately and which of those applications can be set as second and third priorities. The reality is that disasters are rare but they also can happen at any time so balancing the probability against cost is a very important exercise.
Today the method of data protection employed by an organization is determined by the required SLA: How fast do we need to recover data? Since all data does not carry the same value, and budgets are tight, corporations are beginning to implement tiered recovery methodologies to drive how and where they protect data.
Corporations are beginning to design data protection needs around "recovery." Since data is the backbone of every organization, recovering that data as quickly as necessary is critical to balance production downtime cost and budgets. Since one solution (and cost) will not fit every data set, a data protection design is based on recovery and must be evaluated by application and data against:
- RecoveryPointObjective(RPO)–“How much data am Iwilling to lose?”
- RecoveryTime Objective(RTO)–“How long can I be without my data?”
- Cost–This is particularly relevant in a remote office where there are little or no IT resources
Enterprise Strategy Group (ESG) found that mid-market organizations (companies with 100 to 999 employees) cannot endure disruption for long. Over half of the companies surveyed (52%) cannot tolerate more than one hour for their most mission-critical data (Tier 1); 49% cannot tolerate more than three hours of downtime for Tier 2; and 43% cannot tolerate more than nine hours for all other data (Tier 3). This is why considerable investments are being made to protect all tiers of data appropriately.
A typical tiered recovery scenario includes three tiers:
- Tier 1 – Mission-critical applications – This tier can include email, production databases, sales/order processing, customer management, and financial systems.
- Tier 2 – Data and applications- This tier that require high levels of performance and reliability but may not be as critical to business and can tolerate longer recovery periods – file system data, user data, etc.
- Tier 3 – This tier includes inactive data that is no longer changed or accessed that still needs to be managed and stored but not necessarily kept on high performance, high cost disk arrays. Tier 3 data should be archived to remove this "stale" data out of shapshots, backups and recovery processes to reduce costs while improving recovery times. Archive data that can tolerate longer recovery times.