7 Must-Know Disaster Recovery Strategies

(1)

7 MUST-KNOW DISASTER

RECOVERY STRATEGIES

J A M I E

G R U E N E R

S E N I O R A N A L Y S T , E N T E R P R I S E I N F R A S T R U C T U R E

T H E Y A N K E E G R O U P

S U M B E R D A R I :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A

M I E _ G R U E N E R . P P T

S U M B E R K E P U S T A K A A N :

(2)

WHAT YOU WILL LEARN IN THIS SESSION .

.

1.The Main Goal: Bullet-proofng Disaster Recovery

Strategies

2.Remote Replication vs. Mirroring Strategies

3.Disaster Recovery and Virtualization: A New

Angle

4.Integrating Mirroring and Replication into

Disaster Recovery Strategies

5. Metro SANs: Options for Remote Mirroring And

Replication

6.Your Network Options: Questions to Guide You

7.The Outsourcing Alternatives: Things to Consider

(3)

THE GOAL: BULLET-PROOFING

DISASTER RECOVERY STRATEGIES

You’ve heard the statistics



~ $5 billion in computing infrastructure lost in 9-11

tragedy



Close to 100 businesses declaring disasters in NYC

You’re here for a reason



9-11 was a call to action for all of us



Disaster Recovery and Business Continuity Strategies

must be done – this is only one leg of a multi-leg strategy

You’re entering a new era



It is now about Business Continuance and Risk

Management



Preserving data is an imperative

(4)

DEFINING TERMS: REMOTE MIRRORING

AND DATA REPLICATION

Remote Mirroring generates a mirrored

image of data on two or more disks

Data Replication scans data periodically for

changes and copies new data to the other

disk or fle system on another system

Factors to consider



Value of data (and lost data) being backed up



Costs for network bandwidth and software



Your existing infrastructure



Product features (OS, File System, Disk or

Application)

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M I E _ G R U E N E R . P P T

4

(5)

MEASURING DATA PROTECTION:

POINT-IN-TIME TO SYNCHRONOUS

5 Data

Protection

Network Bandwidth Consumed

Point In Time

Asynchronous

Synchronous

Tip

There will be a need for

multiple tools to protect data

Lost Transactions Line of Tolerance

More

Less

_More

(6)

QUESTIONS TO CONSIDER WHEN LOOKING

AT REMOTE MIRRORING AND REPLICATION



What are you protecting? (applications, transactions, fles, disks)



What level of protection do you need?

(We’ll come back to this!)



What are your network requirements?



What is your expected budget for this project?



Is the ROI greater than acquisition costs?



What will best ft your larger business continuity strategy?

6

(7)

THE LUXURY SEDAN:

DISK-TO-DISK REMOTE COPY

Key advantages



Operates at the disk level



Can be (not always) less complex to set up and

administer than host-based approaches



Can ofer the beneft of capturing all application changes.

. .

Key Disadvantages: Costly



Lacks transaction knowledge or what the data represents



Can be wasteful of network bandwidth if not properly set

up



If operating in synchronous mode, can degrade

application performance

(8)

THE RISING ALTERNATIVE:

BLOCK-AND-FILE REPLICATION

Fundamentals



Makes comparisons and only copies changes (at disk or fle

level)

Key Advantages



Can be less expensive



Can be fexible to replicate all enterprise data regardless of

disk system



Copies only the most important fles/data



Many-to-one replication architectures available



Limits amount of data transferred, reducing network load and

cost

Key Disadvantages



Isn’t 100% availability of data

8

(9)

BLOCK AND FILE REPLICATION DETAILS

YOU NEED TO CONSIDER

Less expensive, host-based (or

array-based) fle and block

replication

Specifc to storage vendor, OS or fle

system

9 File WAN Replication

(10)

DATABASE REPLICATION

Typically done by replicating or mirroring log

fles

A number of variations:



Continuous Mirroring: updates DBMS as changes(adds,

updates, deletes) occur



Change Data Capture: captures DBMS changes and stores

them until a predetermined replication time



Full Copy Refresh: replicates entire DBMS copy to target

systems (done to resynchronize DBMS after outage)

Trigger-based native DBMS is not usually

appropriate for DR because of high system

and network overhead

(11)

SNAPSHOTS: THE HOTSHOTS OF

BACKUP

Establishes a separate identifable storage

entity and run operations against it



Primary purpose: backup, testing, conversion and

batch process

Is dependent on OS, host and array support…

Advantage: it takes up less network

bandwidth than mirroring

Disadvantage: resynchronization of data is an

art



If you do not resynchronize, you must build snapshot

mirror totally from scratch

(12)

NEW KID ON THE BLOCK: VIRTUALIZATION

AND DISASTER RECOVERY

Virtualization software ofers a new alternative



Data replication (over both IP and Fibre Channel)



Snapshot



High Availability Fail-over



A cost-efective approach to disaster recovery

Key Challenges



Recreating the virtualization system can be difcult



Specifying fle level information for replication can be

difcult



Still a relatively new technology, so test well



Research virtualization players thoroughly



Ask hard questions about number of customers doing this



How are issues of network performance and security handled?

12

(13)

(14)

OK, NOW WHAT? IT’S THE NETWORK,

STUPID

Long-distance Remote Mirroring/Replication

requires signifcant network integration



Mission: Connecting two or more islands of storage



Could be SANs, hot sites, remote disk or tape

Myriad of network transport choices boil down

to two fundamentals (from the POP out)



Fibre



IP

Where to Start: Evaluate Network

Requirements



Ask storage vendors for requirements



Map that to service provider bandwidth services

(15)

SPECIFIC NETWORK CHALLENGES FOR

REMOTE MIRRORING AND REPLICATION

Enterprise network performance is many times

slower than storage performance

Things You Could Consider



What tools do the remote mirroring/replication vendor

provide for performance on a Metro SAN?



Network throttling – adjusting data amounts sent over wire



Compression – compressing data to take up less network bandwidth



Time-stamping – marking data at time saved or accessed



Latency isn’t your friend



Measurable time it takes for an I/O transaction to reach destination



Distance is a factor – especially when extending data native limit



_{Storage trafc requires high bandwidth, low latency connections not}

typical of IP

15

(16)

METRO SAN PUZZLE PIECES

16 Headquarter

s

Remote Site

Primary

Disk Storage

_{Disk Storage}

Remote

Tape Library

Mirroring/Replication Software

Edge of Network Equipment (Director, Router or DWDM)

Service Provider Connectivity Services

Key Features

(17)

METRO SAN NETWORK TRANSPORT

OPTIONS

17 Network

Protocol

Performance

Length of Distance

ESCON

Full performance (200-M

bits/sec. unidirectional)

8 km for full performance,

50% performance @ 20 km

FICON

Bi-directional channel

protocol, runs over at

1.063 G bit/sec.

100 km distance limitation

Dark Fibre

Dedicated Fibre (depends

on transport)

10 km without long-wave

transceivers

iSCSI, iFCP, FCIP

Still in proof-of-concept

stage, but promise of 1

TB per hour over IP

Depends on applications,

service, connection points –

FCIP - primary for Metro

SANs

storage islands, OC3 or <

Depends on applications,

service, connection points and

routers used (DWDM)

(18)

IP NETWORK OPTIONS

Private Router Backbones



Leased, dedicated lines



Optimized for performance (racing the sun)

xSP VPNs



Customer purchases edge routers and ISP

provides shared backbone



Leverages Multiprotocol Layer Switching (MPLS)

for better Quality of Service

Internet . . .



Not a disaster recovery tactic I would trust

(19)

TIPS TO CONSIDER WHEN SPEAKING

WITH YOUR SERVICE PROVIDER

Ask your xSP to provide you what their expertise is

in storage services



Consider how you could leverage your existing connectivity

services to establish a cost-efective service contract for your

backup services



Ask for a latency/network performance SLA



Your primary xSP should have partners to assist with storage

services if they don’t

Consider leveraging storage vendor relationships to

fnd service providers that can do integration

Do or have done a network analysis to determine

requirements for your backup services

Determine if outsourcing is an option

S U M B E R K E P U S T A K A A N :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M

(20)

METRO SAN CHALLENGES: THINGS

YOU NEED TO ASK ABOUT IP

Latency and Bandwidth

Security

Complexity

Quality of Service (QoS)

Dropped Packets

Manageability

NOTE: IP storage switch vendors are

trying to solve these things – so gauge

them based on this

S U M B E R K E P U S T A K A A N :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M

(21)

DOES OUTSOURCING MAKE SENSE?

Determine if outsourcing disaster recovery

services for Data Mirroring and Replication

services



Do I have the skills, personnel and infrastructure?

Outsourcing provides a number of advantages



Enables enterprise to focus on core competence



Speeds IT’s ability to maintain and return to business operations



Leverages expertise and more plentiful specialized resources



Ofers mirrored solutions for immediate recovery



Provides problem resolution expertise that speeds delivery of

services related to backup, security and performance monitoring



Delivers professional services to assist in design of a customized

business continuity plan

S U M B E R K E P U S T A K A A N :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M

(22)

ASK FOR HELP FROM A

PROFESSIONAL . . .

This is a complex proposition

Storage vendors will assist with best

backup technologies

Service Providers will ofer options for

services

Integrators with storage and networking

practices are best candidates for

additional implementation



_{they are still rare in the world}

S U M B E R K E P U S T A K A A N :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M

(23)

EVALUATE ROI FOR DISASTER RECOVERY

Come up with a ROI calculation for your

data protection strategy

Guidelines to remember



_{Calculated over three-year term}



The higher the ROI, the more favorable the project



TCO vs. ROI – ROI wins out

Key factors to be included in ROI analysis



Costs: downtime, personnel, assets



Reliability: data replication, mirroring, backups



_{System performance: how is systems and software}

utilized



_{Calculate savings: improved performance, revenue,}

processes

S U M B E R K E P U S T A K A A N :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M

(24)

CONCLUSIONS

Don’t forget the fundamental goal: Disaster

Recovery

Consider your options for mirroring/replication

and make a metric to measure them by



ROI analysis is one way of measuring options

Be cautious of new technologies



New IP storage networking technologies and software

ofer new options – but you need to be savvy in

deployment

There’s not one solution – strategize on ways to

prioritize your data protection

S U M B E R K E P U S T A K A A N :

C D N . T T G T M E D I A . C O M / . . . / S T O R A G E _ M A N A G E M E N T _ J A M