This presentation will cover the latest best practices for Business Continuity and Disaster Recovery planning.
This webcast will address:
Technologies Overview - from tape to mirroring
How to identify the solution that's right for your business
To view this presentation with audio, visit: http://go.mainline.com/pages/start/knowledge-center-bcdr-webcast-july-2009/index.html?Campaign_Id=7639&Activity_Id=6136
For other topics, visit: www.mainline.com/kc
Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Business Resiliency Strategies - From Basic to Bullet-Proof
1. Business Resiliency Strategies: Overview of Technology Solutions Chris Dedham Business Continuity Specialist Mainline Information Systems
2. The Storage Ecosystem Capacity BC/DR ILM Utilization Performance Operational Recovery Disaster Recovery Security Data Classification Tiers of Storage Data Mobility Archiving Storage Management Tools Virtualization Data De-Duplication
3. The Old Iceberg Analogy 90% of unplanned outages stem from operational issues like human error, viruses and software corruption! 8% of unplanned outages are from hardware failures 2% of unplanned outages are from Disasters
4. Defining the Scope of BC/DR is Key Frequency of Occurrences Per Year Consequences (Single Occurrence Loss) in Dollars per Occurrence 1,000 100 10 1 1/10 1/100 1/1,000 1/10,000 1/100,000 Virus Worms Disk Failure Component Failure Power Failure frequent infrequent lower higher Natural Disaster Application Outage Data Corruption Network Problem Building Fire Terrorism/Civil Unrest availability-related recovery-related Define the desired scope of the BC program
5. Recovery Time is a Step-by-Step Journey Total Elapsed Time (Recovery Time Objective) 15 Min. 1-4 Hr.. 4 -8 Hr.. 8-12 Hr.. 12-16 Hr.. 24 Hr.. 72 hours Value, Investment DR Tier 4 - Point in Time copies forwarded to remote site DR Tier 3 - Electronic Vaulting DR Tier 2 - Hot Site, Restore from Tape DR Tier 7 – Server and storage mirroring, automated end to end recovery DR Tier 6 – Real time replication DR Tier 5 –Transaction integrity, database mirroring DR Tier 1 – Cold Site, restore from Tape Recovery from a disk image Recovery from tape copy Recovery Times are rough estimations only Subject to validation Definition of successful recovery: All applications within a given BC Tier of recovery are up and running
6. Align Storage Technology with the Recoverability Requirements NOTE:. Data protection techniques will vary based on data types. Duration will depend on the amount of data. Sync for zero data loss Tapes to Courier Tapes to Courier VTL Vaulting Log shipping Async Async DR RPO Tapes to Courier for Hot / Cold site Tape VTL Vaulting Snap shots with log apply Storage based Mirror / CDP Host Based Mirror / CDP DR RTO Weekly tape rotation VTL or Tape Log Backups or Snaps Log Backups or Snaps Log backups or Snaps CDP Operational RPO Off line tape VTL or Tape Tape LAN Free / VTL Disk to Disk / CDP CDP Operational RTO Notes Days 24 hours 12-16 hours 8-12 hours 1-4 hours < 15 min Recovery Requirements
7. The Storage Solutions Stack Array / Controller / Storage Based Replication Virtualization / Appliance Based Replication Host / Server Based Replication Application / Log Based Replication Global Mirror, Snap Shots Metro Mirror, SRDF, Snap Mirror SVC, FalconStor, Acopia, Exanet EchoStream, InMage DoubleTake, iCluster, TSM FastBack Data Guard, Exchange SCR DB2, Lotus Notes , MSSQL, etc . = = = = Methodology Technology Backup System (Foundation) TSM, Veritas, Legato VTL, De-Dupe = The application will often drive the type of technology Fabric Based Replication InMage, RecoverPoint =
8. Thank you Knowledge is POWER at: Mainline’s Knowledge Center www.mainline.com/kc 866.490.MAIN (6246)
Editor's Notes
Understanding Recovery Tiers requires an understanding of the Storage Ecosystem. There are many interdependencies within the storage environment. For example, an email archiving strategy to help storage email for compliance purposes will reduce the size of the email database which will shorten the backup window and recovery times.
The vulnerability of a data center is from operational issues like human error , viruses and software corruption. The service level agreements (SLA’s) for operational recovery are tighter and for disaster recovery because the organization and parts of IT are still operational.
Every organization has their own vulnerability issues. Operational issues are fairly universal to most IT organization. Disaster recovery issues vary based on geography and facilities. With today’s technology, it is possible to address operational recovery and disaster recovery with one solution.
It is important to recognize that most organizations will require a blend of technologies since not all data is created equally. Since BC/DR is a costly endeavor, it is often financially prohibitive to apply the same technology for critical applications to non-critical applications.
Once the SLA’s have been defined for operational and disaster recovery, then the appropriate technologies can be aligned with the corresponding recovery time and recovery point objectives
The next step in identifying the correct technologies is to determine what is the optimal approach for protecting the underlying data. Often times a BC/DR strategy is driven by the over all data center strategy is it relates to server and storage.