CFITS Disaster Recovery 2009

47
The Central Florida Information Technology Society The mission of CFITS is to educate, share and develop sound practices for managing risk, budget, and data security to achieve business and operational success.

description

A CFITS member event presentation on Disaster RecoverySponsors include: TriBridge, Prosys and InMage

Transcript of CFITS Disaster Recovery 2009

Page 1: CFITS Disaster Recovery 2009

The Central Florida Information Technology Society

The mission of CFITS is to educate, share and develop sound practices for managing risk,

budget, and data security to achieve business and operational success.

Page 2: CFITS Disaster Recovery 2009

Meeting Agenda

Introduction to CFITS CFITS Updates CFITS in 2008 Introduction to Our Sponsors DR, BC & CDP Q & A Door Prizes

Page 3: CFITS Disaster Recovery 2009

CFITS Updates

New Website Design

Job Section on Website

Website Forum

Page 4: CFITS Disaster Recovery 2009

Making CFITS Your Organization

Networking amongst peers

We encourage open dialogue on the message boards

If you find a tip or trick, post it – use the forums to get answers to questions on emerging technologies

If there are other events of interest that CFITS members may interested in, share!

Page 5: CFITS Disaster Recovery 2009

CFITS 2008 Objectives

Populating the Web Forum with useful information

Seeking Future Event Ideas

Seeking Future Sponsors

Interests for 2009 Board Members – Rotation in December

Scholarship for UCF CS, IT, or MIS Student– Will post entry reqs on website in October 2008.

Page 6: CFITS Disaster Recovery 2009

Today’s Sponsors

Tri Bridge – Greg Pierce– www.tribridge.com

Prosys – Joe Prokop– www.prosysis.com

InMage – Phil Swim– www.inmage.net

Page 7: CFITS Disaster Recovery 2009

Presenter: Gregory PierceE-mail: [email protected]

Phone: 813-221-0376

Business Continuity

Page 8: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

About Us

• World Class Microsoft Partner Top 1% of Microsoft Partners World Wide One of 23 Nationally Managed Partners Member of Microsoft’s “Inner Circle” and President’s

Club Microsoft Dynamics US Partner of the Year 2007 Microsoft Dynamics Worldwide Partner of the Year 2008 Microsoft Southeastern United States Partner of the Year

2008• Capabilities

Total Solution Dedicated Support 100% Go Live

Page 9: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

IT Challenges

• Unpredictable, costly downtime Staff and corporate productivity are impacted

• Managing IT Costs Amount and predictability of ongoing cost

• Management Time Time and effort to fix problems

• Strategic Issues “Fire Fighting” instead of Strategic Deployment Pull instead of push

Page 10: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

Data Protection

• Data backup Make sure it’s repeatable and scalable Know the risks

• Data backup off-site Is it really all about hurricanes? What is your restore window? Do you have any mechanisms to get back up quickly?

• Redundancy Geographic Software, Hardware Environmental

• Determine your Optimal Strategy

Page 11: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

Getting Buy-in

• Assess the risk• Find the money

Show you’re willing to move as well• Architect the Solution• Establish a budget• Develop an ROI

Page 12: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

Business Impact Analysis

Downtime Illustration Example: File server failure at a 20-user Law Firm

For eight hours employees do not have access to their client records, forms, document assembly and case management resources

The firm’s partners and associates have a typical average utilization rate of 70% (billable time)

During the course of this failure, they can only work at 30% of the normal level of productivity

Service provider begins remediation two hours after failure

Page 13: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

Business Impact Analysis

Downtime Illustration Example:• Legal partners (4) bill themselves out at $250/hr

Utilization rate = 70% so effective billing rate is $175/hr• Associates (10) bill themselves out at $140/hr

Effective billing rate = $98/hr• Downtime Incident Cost Calculations:

6 hrs of technician time to fix the server: $600 (6%)

4 partners’ lost billing at 30% utilization: $3,920 (39%)

10 associates’ lost billing at 30% utilization: $5,488 (55%)

TOTAL COST OF DOWNTIME INCIDENT: $10,008 (100%)

Page 14: CFITS Disaster Recovery 2009

Standardized Rationalized Dynamic

Prevent Fires

Basic

Managed IT infrastructure with limited automation

Managed and consolidated IT infrastructure with maximum

automation

Fully automated management,

dynamic resource usage, business

linked SLAs

Uncoordinated, manual

infrastructure

Dynamic IT

Cost Center More Efficient Cost Center Business Enabler Strategic Asset

Page 15: CFITS Disaster Recovery 2009

www.tribridge.com | 888-HELP-DYN | [email protected] | 888-HELP-DYN | [email protected]

Non-Redundant Solution

Redundant Solution

Monthly contract $1,700 $1,700

Additional reactive support $1,100 $0

Downtime cost $1,000 $300

Emergency support $300 $0

Overages $250 $0

TOTALS $4,350 $2,000

ROI Basics

Page 16: CFITS Disaster Recovery 2009

Agree on a Framework Find out the budget up front

Don’t Make it about disaster Clear your plate Crawl before you walk Don’t Overpromise

Page 17: CFITS Disaster Recovery 2009

BUSINESS CONTINUITY AND DISASTER RECOVERYOVERVIEW, FOUNDATION, AND THE BENEFITS OF VIRTUALIZATION

Page 18: CFITS Disaster Recovery 2009

BC/DR Overview - Components

– People• Employees• Customers

– Places• Company Facilities• Local Terrain, Road system,

Services– Things

• Hardware & Software (I.T.) Infrastructure (Classic DR)

– Risks• Identifiable risks to our

People, Places and Things that make up the business

– Time & Money• Relationship of money to the

time business functions are lost or interrupted (BIA)

– Relationships• Contracts and Agreements

with Customers, Employees, Partners, Government

Page 19: CFITS Disaster Recovery 2009

BC/DR Overview – The FoundationA Business Impact Analysis (BIA)

– You must know what the impact is, in the case of a disaster or interruption, to each key business function

– Know the total cost of downtime for each business function within your company over time

– Data Classification for Information Lifecycle Management (ILM) can help. An SRM product can help start your ILM work.

– For smaller organizations this doesn’t have to be huge and can have an “order of magnitude” using industry averages – at least to start.

– Use real-life examples from events in the past– A BIA is not just for I.T. anymore– A BIA should be sold as the foundation for the entire company to

responsibly create strategies and context to operate from

Page 20: CFITS Disaster Recovery 2009

Executive Involvement and Sponsorship• Executive Management must convinced by a BUSINESS Case!• Remember - Business Continuity & DR are NOT about technology!

– Technology by itself cannot justify the use of more technology– BC is typically about the PEOPLE and the DATA or Intellectual Property

more than the technology used to store the data/IP by the people who use it

– Any DR, BC, CP etc efforts are funded to AVOID losses to the business• Don’t forget to include Legal & HR – it’s a Team effort!

– These groups can be your advocates when approaching the CEO/President, CFO or COO

– Compliance – need I say anymore?– Legal liability to customers or partners (contracts, agreements…)– HR involvement in human issues related to disasters and employee

responsibilities

Page 21: CFITS Disaster Recovery 2009

The Classis DR Challenge For IT

• I have to DUPLICATE my Server and Storage Infrastructure capabilities at one or more remote sites for DR !!!

(and Hurricane season is already here !!!)

Page 22: CFITS Disaster Recovery 2009

DR Server Infrastructure without Server Virtualization• Server Infrastructure had to be precisely duplicated at a remote

DR site• Very Expensive and time consuming to maintain that Server

Infrastructure and all the right peripherals so that you systems will boot and run when needed

• Very difficult to test because of all the interdependencies between OS, server hardware and peripherals

• Longer Recovery Time Objectives (RTO’s)• Inability to consistently reach the RTO’s

Page 23: CFITS Disaster Recovery 2009

Server Virtualization – Models

Physical System

System Instance

System Instance

System Instance

Physical System

Application System Instance

System Instance

Thin Host Fat Host

Virtualization Intermediary Host OS

Virtualization Intermediary

(VMware, Citrix XenServer, MS Hyper-V, Linux Virtualization (RHEL, SLES), Open-Source Xen, …)

(VMware Workstation, HP VSE, Parallels, …)

Page 24: CFITS Disaster Recovery 2009

DR with Server Virtualization• Dramatically reduction in the HW Infrastructure required at the DR site

– Reduced infrastructure costs, floor space required, power & cooling

• Servers are liberated from dependencies on specific server hardware– This enables dislike hardware to be used at a remote DR site– Eliminates time and expense of maintaining identical hardware and OS

installations at the DR site– Enables the increased use of Hosting company Infrastructure– Greatly simplifies testing and failover

• Simplified Replication of Data to the DR Site– Shared storage and a Clustered File system can locate all files associated with a

given server in one location– Enables OS and hardware independent snapshots to assist in replicated consistent

data sets to the DR site

• Shorter RTO possible – Simple reboot or short failover

Page 25: CFITS Disaster Recovery 2009

DR SAN Storage Infrastructure without Virtualization• Storage Infrastructure had to be closely duplicated at a remote

DR site• Very Expensive and time consuming to maintain that Storage

Infrastructure • Very difficult to test because of all the interdependencies

between OS, server hardware and SAN Storage• Array-based Replication was expensive and specific to each

storage vendor• Longer Recovery Time Objectives (RTO’s)• Some help more recently with NAS & iSCSI for smaller

application servers

Page 26: CFITS Disaster Recovery 2009

DR SAN Storage Infrastructure without Virtualization

SAN

REMOTE DR SITE

Storage Vendor A

Vendor A DR

Vendor B DR

Vendor C DR

Storage Vendor B

Storage Vendor C

Array-based Replication

PRIMARY SITE

Array-based Replication

Array-based Replication

Array-based SANReplication

Example

Page 27: CFITS Disaster Recovery 2009

DR SAN Storage Infrastructure WITH Virtualization

SAN

REMOTE DR SITE

Storage Vendor A

Storage Vendor B

Storage Vendor C

PRIMARY SITE

Replication between SAN Fabric Appliances or Arrays

Array-based SANReplication

Example with FabricLevel Virtualization

SAN

Optional Storage Vendor X

LUNs and Provisioning Done at the Fabric

Layer

Page 28: CFITS Disaster Recovery 2009

DR SAN Storage Infrastructure with Fabric Virtualization• Servers are isolated from multi-vendor Storage specific

interoperability issues• You have a choice of Storage vendor at the DR Site• Replication can be done with ONE set of replication licenses

across all supported vendors!!!• Arrays that don’t support replication can now be replicated via

the same mechanism as the more advanced arrays• One set of advanced features (snapshots, clones etc) can work

across all supported arrays• Shorter Recovery Time Objectives (RTO’s) due to a common

storage interface, provisioning and management

Page 29: CFITS Disaster Recovery 2009

Summary• Have and use a Business Impact Analysis as the foundation for

all your BC/DR efforts• Processes and tools used in ILM can help you begin to create

your first BIA• Involve all appropriate Executive Management – BC/DR is a

Business Challenge – not just an IT challenge• Look for help from groups like Legal and HR• Server and Storage Virtualization technology provide specific

benefits that make it simpler and less costly to implement IT Infrastructure for BC/DR

Page 30: CFITS Disaster Recovery 2009

SECTION TITLE

Questions?

?

Page 31: CFITS Disaster Recovery 2009

SECTION TITLE

Who is ProSys Information Systems?• Founded in 1997

• Revenue of $442 million in 2007

• Projected revenue of $500 million in 2008

• Headquarters in Atlanta, GA

• 16 locations nationwide

• 350+ employees

• 60+ Account Executives

• 175+ Engineers & Technicians

• 3-to-1: service-to-sales ratio

Page 32: CFITS Disaster Recovery 2009

ProSys National Office Footprint

Miami

AustinTallahassee

CharlotteKnoxville

LexingtonLouisville

Birmingham

Jackson

Little Rock

Memphis

Nashville

CincinnatiIndianapolis

Bell HQ - San Jose, CA

Rorke Data Location HQ - Eden Prairie, MN

Total Tec HQ - Edison, NJ

ProSys HQ Atlanta, GA

Office Locations

A Bell Microproducts Company

Targeted Growth Areas

Tampa

Montgomery

St. Louis

Boca Raton

Page 33: CFITS Disaster Recovery 2009

We would love to help you with your technology challenges!

SECTION TITLE

Ron BurnsAccount Executive, [email protected]/Cell: (407) 928-0926

Dawn PattersonAccount Manager, [email protected]: (727) 388-4292Cell: (727) 698-2703

www.prosysis.com

Joseph M. ProkopData Management Practice Manager, [email protected]: (813) 854-3451Cell: (813) 417-7823

Scott TumeltyDistrict Sales Manager, Central [email protected]: (813) 639-4233Cell: (813) 477-9895

Page 34: CFITS Disaster Recovery 2009

The DR Paradigm Has Shifted

DR Doesn’t Require a “Disaster”

Presented By:

Phil Swim, Account Executive - FL

August 28, 2008

Page 35: CFITS Disaster Recovery 2009

35

Agenda

1. Traditional DR

2. Why and How Has DR Changed Today…?

3. DR Complexity

4. Data Protection & Advanced Recovery in Virtual Environments

5. A little about InMage Systems

Page 37: CFITS Disaster Recovery 2009

37

What is Important in Business Continuity and DR?

Data Lost

SecsMinsHours

DaysWeeks WeeksDaysHours

MinsSecs

Recovery Point Objective Recovery Time Objective

Lost Data Time To Resume Business

(Max data loss you can tolerate ) (Max downtime you can tolerate)

RPO RTO

Page 38: CFITS Disaster Recovery 2009

38

Today’s Challenges

IT Departments Need to Reduce Cost & ComplexityMore data needs better protection, all of the time

Leverage existing technology & incorporate new alternatives

Need simple, scalable, solutions that fit within budget constraints

Backup Was Designed for Yesterday’s ProblemToo labor intensive, too slow, usually provides too little, too late

Backup with VTL/De-Dupe is Still BackupRecovery gaps, Backup Windows, DR hassles still exist

Host Based ReplicationWorks for low-end Applications and servers – Limited uses

Array/Mirroring Solutions Are Expensive & Vendor SpecificLimited & complex. But the data was “Out of the Building”

Page 39: CFITS Disaster Recovery 2009

39

Gartner Survey of Top 3 IT Priorities for 2008:

1. Consolidation

2. Privacy

3. Disaster Recovery

“ Our DR Customer Inquiries Were Higher than Ever Compared to Previous Years. In 2007 We Received Over 800 Customer Calls Pertaining to Disaster Recovery, Planning, and Data Recovery.”

John MorencyGartner Group

Page 40: CFITS Disaster Recovery 2009

40

What Has Caused the DR Shift?

1. DR is a Requirement for Mid-Tier & SMEs Increased onslaught of Natural Disasters and 911 Compliance Mandates for Financial/Healthcare

2. IT Has To Align with Increased End-User SLAs RPOs / RTOs

3. Traditional DR Has Merged with Hourly Recovery

4. Complexity & Cost Have to be Reduced

Technology & Economics Are The Enabler

Page 41: CFITS Disaster Recovery 2009

41

Disaster Recovery and Business Continuity Requirements Are Merging

Virus/WORMSCustomer Service Levels (RPO/RTO)

for Business Continuity /

Disaster Recovery are Merging

Business Continuity

DisasterRecovery

Page 42: CFITS Disaster Recovery 2009

42

DR Projects Are Extremely Complex

BIA & Risk Assessment

Physical Logistics

RecoveryStrategy

Recovery Plan& Mechanisms Testing Plan

Maintenance

DR Projects > 6 Distinct Product Categories A DR Project Consists of Over 700 Specific StepsSignificant Amount of Planning, People, & Processes

Page 43: CFITS Disaster Recovery 2009

43

Two DR Markets With Identical ChallengesEnterprise to Mid-Tier

1. Must Automate the Disaster Recovery Process Consolidate 100’s of Moving Parts and Procedures

2. Advanced Recovery Solutions > End-User SLAs Event Based RPOs/RTOs

3. Testing Must Be Automated and Simplified It’s a Quarterly Requirement versus Annual

4. Must Be Affordable

Page 44: CFITS Disaster Recovery 2009

44

Support for Virtualized Environments

Server Virtualization and/or Storage Virtualization in use or on the Road Map of almost every IT organization

Migration towards ‘Virtualized” Data Center

Support for virtualized source, target or bothProtection of physical servers as well as use a virtualized servers

Flexibility to Support ( V to P, V to V, P to V) Architectures.

Flexibility to support all leading virtualization technologies

Leaders Such as VM Ware & Microsoft Virtual Servers.

Page 45: CFITS Disaster Recovery 2009

45

Quick Intro to InMage

Co-Founded 2001 by Kumar Malavalli, Founder and CTO Brocade Communications

Focused on Enterprise Class “Business Continuity”Company Positioned for 3X+ Growth in 2008 8 Straight Quarters of Increasing Revenues and Customers

Santa Clara, CA (headquarters), Toronto, NYC, DC, Boston, Chicago, Detroit, Denver, SLC, LA, Dallas, Atlanta, London

Strong customer base: Hyperion, Polycom, RJ Reynolds, Sempra Energy, CB Richard Ellis, WSGR, Xerox

Analyst support: Gartner, ESG, and Taneja Group

Pioneered a new approach to “Continuous Data Protection” (CDP) Technology with 6 Patents

Page 46: CFITS Disaster Recovery 2009

46

Key Applications for InMage:

1. Disaster Recovery

Local and Remote Simultaneously Minimal Impact on Product Servers/Networks

2. Continuous Local Backup

‘Near Zero’ RPO & RTO Eliminates Backup Window

3. Application Consistent Failover AND Failback

Based on Predetermined or Ad-hoc Business Events Integrated w/Exchange, SQL, SharePoint, Oracle, SAP,

Blackberry4. Data Migration

Hardware Agnostic Fault Tolerant

5. Profiling and WAN/Storage Modeling

Based on change rate, time of day, or other variables

Page 47: CFITS Disaster Recovery 2009

47

Some of our Customers: