Have a Plan of ATTACK. Not a panic attack. 10 September 2003 IBM Internal Use Only Jarrett Potts, Tivoli Sales Enablement

Transcription

1 IBM Software Group Have a Plan of ATTACK Not a panic attack 10 September 2003 IBM Internal Use Only Jarrett Potts, Tivoli Sales Enablement Abstract This session will show the difference between Business continuance and Disaster recovery and how both can be achieved by using the different levels of protection. The first half of this session will deal with disaster recover and business continuance from a hardware and software vendor agnostic way. The second half will show how IBM/Tivoli can address the levels of protection. To wrap up we will cover some resources you have available to you with the IBM Tivoli Hardware and software. 1

2 Agenda Definitions Disaster recovery Business continuance Levels of recovery Levels of data Planning Discover you data Rank your data SLA based Recover tiers Putting it all together Definitions What is disaster recovery? Disaster recovery is the process of recovering an environment after a major failure or disaster to the point at which business can be conducted What is Business continuance? Business continuance is the act of recovering your environment while still being open for business. Little to zero downtime to affect the business transactions. 2

3 Business Recovery Options Tiers 5 and 6 More costly Tiers 3 and 4 Faster Recovery Tiers 1 and 2 6 SHARE 78 Recovery Tiers Tier 0 - Nothing Tier 0 - No offsite data Standard data backup process, NOT DRM Time to recover is unpredictable - may be never 3

4 Tier 1- Vaulting only Tier 1 - Pickup truck access method (PTAM) Daily MUST have a written plan to be DRM, otherwise this is just an archive Typically 1 week or more to recover Tier 2 Vaulting to Hotsite Tier 2 -PTAM + Hot site Daily at Recovery Time Available using TSM/DRM today Typically more than 1 day to recover 4

5 Tier 3 Electronic Vaulting Tier 3 - Electronic vaulting Daily Daily at Recovery Time Fully integrated/automated with TSM/DRM Typically 1 day to recover Tier 4 - Electronic Vaulting to Hotsite Tier 4 - Active secondary site High Bandwidth connections Daily at Recovery Time Available using TSM/DRM and high availability products Typically up to 1 day to recover 5

6 Tier 5 - Hardware + TSM Tier 5 - Two site two phase commit High Bandwidth connections Two phase commit is standard in TSM data movement transactions Typically less than 12 hours to recover Tier 6 Hardware + TSM Tier 6 - Zero data loss Advanced C o up led System s High Bandwidth connections Data Sharing Available using TSM/DRM and high availability products Typically a few minutes to recover 6

7 Successful Disaster Recovery A Documented Process for Recovery Updated and exercised regularly A system environment in which to recover Hotsite; dedicated equipment, combination Including a network environment A protected repository for information System, database, control, synchronization Accurate, available, trusted data updates Database software facilities play a key role Skilled, experienced people to perform recovery Recovery plan The Recovery plan must have the following Mission Statements Disaster Definition Team Responsibilities Contact Information Critical Documentation Unique Procedures Media Plan Recovery Site Inventory Backup/Recovery Process Implementation Plan Test Plan Maintenance Plan Relocation/Migration Plan Dynamic recovery plan Underlined items part of TSM/DRM 7

8 Planning The key to any successful recovery is planning you must: Be prepared by know exactly what is on each computer and who owns the data. Be aware of what type of data you are restoring. Be secure that your data can be retrieved from backup media Be educated on what exactly you must do to restore the data Be able to verify the restore Before your backup Know your data 8

9 Remaining 10% capacity Non Business Files Duplicate data Trash data, such as log files, dump files, temporary files Stale Data Valid Data Get more of this. Delete this. Delete this. Clean this. Often Archive this. Often Protect this. Why protect, store, and pay for data that isn t needed, used, or business-critical? Classify your data Important for backup and restore Level 1 Must have Valid Data Level 2 Need to have Level 3 Should have Level 4 Don t need 9

10 How much data protection is enough for each of your computers? Mission Critical Applications Dedicated Remote Hot Site Tier 7 - Near zero or zero Data Loss: Highly automated takeover on a complex wide or business-wide basis, using remote disk mirroring & data sharing Tier 6 - Near zero or zero Data Loss remote disk mirroring helping with data integrity and data consistency Tier 5 - software two site, two phase commit (transaction integrity); or repetitive PiT copies with small data loss Typically < 4 hrs to recover 4-8 hours to recover < 12 hours to recover Cost Mostly Critical Applications Non-Critical Applications Active Secondary Site Point-in-Time Backup Tier 4 - Batch/Online database shadowing and journaling, repetitive PiT copies, fuzzy copy disk mirroring, TSM-DRM Tier 3 - Electronic Vaulting, TSM 15 Min. 1-4 Hr Hr Hr Hr.. 24 Hr.. Days Tier 2 - PTAM, Hot Site, TSM Tier 1 - PTAM* Up to 1 day to recover 1 day to recover > 1 day to recover 1 week or more to recover IBM Software Group How IBM can get you there! 10 September 2003 IBM Internal Use Only Jarrett Potts, Tivoli Sales Enablement 10

11 Tivoli Storage Manager Ensures application availability by protecting data Simplifies storage administration Improves ROI through efficient use of storage media Provides backup and restore; archive and retrieval; space management; disaster recovery; autonomic storage management Tivoli Storage Resource Manager Monitor storage resources to ensure application availability through policy-based automation Optimize storage capacity utilization Create and manage with storage policies 11

12 Tivoli SAN Manager Visualize SAN resources just as you visualize network resources Automatically detect SAN composition Detect errors and isolate faults within the SAN IBM Tivoli Storage Solutions in Action Server & Storage recovery Stage 1: Planning SAN Mgr: Identify bottleneck and single point of failure TSM: Backup applications & critical data SRM: Analyze storage, identify critical / non-critical data Stage 2: Steady State Stage 3: Recovery SAN Mgr: Monitor SAN, avoid / fix problems TSM: Move stale data, backup systems SRM: Track how the changes are effecting the environment TSM: Backup, archive and restore / recovery SAN Mgr: Identify and troubleshoot new environment (RCA) SRM: Monitor storage, correct problems, forecast needs 12

13 IBM Software Group Thank you Be aware of what type of data you are restoring 10 September 2003 IBM Internal Use Only Jarrett Potts, Tivoli Sales Enablement 13