Top Banner
© 2013 Velocity Technology Solutions, Inc. EXPERIENCE. INNOVATION. Disaster Recovery: Modernized Best Practices for JD Edwards & Beyond Presented by Andy Chase & Paul Shearer December 4th, 2013
29

Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

Aug 20, 2015

Download

Education

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

© 2013 Velocity Technology Solutions, Inc.

EXPERIENCE. INNOVATION.

Disaster Recovery: Modernized Best Practices for JD Edwards & Beyond

Presented by Andy Chase & Paul Shearer

December 4th, 2013

Page 2: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

What constitutes a disaster?

2

hurricanetornado

tsunami

earthquake

severe weather

power outage

IT failure

epidemic/pandemic

telecommunications failure

fire

flood

cyber attack

utility outage

health & safety incident

environmental accidenthaz mat explosion

supply chain disruption

terrorist event

sabotage

Page 3: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

Rec

ove

ry P

oin

t O

bje

ctiv

e (R

PO

)

Recovery Time Objective (RTO)

Most Disaster Recovery Discussions Begin Here

Tape Backup

Minutes

Days

Seconds

3

Tape Backup

How much data can you afford to lose?

How much downtime can you afford to have?

Weeks

Page 4: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

Rec

ove

ry P

oin

t O

bje

ctiv

e (R

PO

)

Recovery Time Objective (RTO)

Data Vaulting

Minutes

Seconds

4

How much data can you afford to lose?

Most Disaster Recovery Discussions Begin Here

Days

Weeks

ElectronicBackup

RPO: 24 hoursRTO: 24 hours

TransactionVaulting

RPO: 60 minutesRTO: <= 12 hours

High Availability

RPO: last successful transactionRTO: <= 2 hours

Tape Backup

RPO: 24 hoursRTO: 48 hours

NO DR

RPO: ?RTO: ?

How much downtime can you afford to have?

Page 5: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

Rec

ove

ry P

oin

t O

bje

ctiv

e (R

PO

)

Recovery Time Objective (RTO)

Data Vaulting

Minutes

Seconds

5

How much data can you afford to lose?

Most Disaster Recovery Discussions Begin Here

Days

Weeks

ElectronicBackup

RPO: 24 hoursRTO: 24 hours

Transaction Vaulting

RPO: 60 minutesRTO: <= 12 hours

High Availability

RPO: last successful transactionRTO: <= 2 hours

Tape Backup

RPO: 24 hoursRTO: 48 hours

NO DR

RPO: ?RTO: ?

This is inherently broken!

How much downtime can you afford to have?

Page 6: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 6

Disaster Recovery “Benchmark” Data

How many companies that invested in disaster recovery are completely confident that they could recover all their applications & data in the event of a disaster?

• 24% SCUG 9/11• 27.5% HUG 9/12• 26% KC RUG 10/18• 10.5% NY/NJ RUG 10/18• 27% MARUG 10/21• 10.5% RMUG 10/25• 20.5% OCEAN 11/19• 6.7% InFocus 12/4

Page 7: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 7

What do these numbers reveal about DR?

and Proven Recoverability.

There is a GAP between Disaster Recovery

Page 8: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 8

Why the gap?

• “DR Team” already has full-time job- Production support always trumps DR- There will always be production issues to resolve

• Lack of executive sponsorship• Lack of testing

- Testing is not practical- Business can’t or won’t engage

• Testing not complete• Too much time since last test

- Plan not up to date- Too many changes to Production

• Not a business priority- Not perceived as important

• Lack of skills, understanding, funding, etc.• Uncertainty of staff availability in actual regional disaster event

Page 9: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

Rec

ove

ry P

oin

t O

bje

ctiv

e (R

PO

)

Recovery Time Objective (RTO)

Data Vaulting

Minutes

Seconds

9

How much data can you afford to lose?

Why are most DR discussion inherently broken?

Days

Weeks

ElectronicBackup

RPO: 24 hoursRTO: 24 hours

Transaction Vaulting

RPO: 60 minutesRTO: <= 12 hours

High Availability

RPO: last successful transactionRTO: <= 2 hours

Tape Backup

RPO: 24 hoursRTO: 48 hours

NO DR

RPO: ?RTO: ?

How much downtime can you afford to have?

They Assume Recoverability!

Page 10: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 10

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

- Disaster Recovery Recoverability Plan

- Disaster Recovery Recoverability Spending

- Disaster Recovery Recoverability Solution

- Disaster Recovery Recoverability Projects

Page 11: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 11

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

Page 12: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 12

The Velocity definition of Recoverability

The Power to Recover Your Business Applications & Data

Page 13: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 13

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

3. Does Recoverability Matter?

Page 14: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 14

Does Recoverability Matter?

• Most would say yes, but results reveal otherwise…

(GAP between Disaster Recovery & Recoverability is not new)

• Did you know?- SOX, HIPAA, PCI, FERPA do not require Recoverability

(at least Not Yet)- The Disaster Recovery Check Box vs. Proven Recoverability- How many CXOs are aware that their companies compliance with SOX,

HIPAA, etc does not actually mean they are Recoverable?

Page 15: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 15

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

3. Does Recoverability Matter?

4. What would it take to Prove Recoverability?

Page 16: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 16

What would it take to be completely confident that you

could recover all your applications & data in the event of a disaster?

Page 17: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 17

What would it take to Prove Recoverability?

1) Plan it – Define all components required (create a matrix)2) Build it – Implement all the pieces to the puzzle3) Test it – Keep testing all pieces until you get it right4) Prove it – Testing that includes business users & processes5) Maintain it – Keep yourself Recoverable at ALL times6) Guard it – Eliminate every potential single point of failure

The goal is for everyone in your business to be completely confident you are Recoverable!

Page 18: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 18

Page 19: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 19

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

3. Does Recoverability Matter?

4. What would it take to Prove Recoverability?

5. Eliminate single points of failure

Page 20: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 20

Single Points of Failure in Disaster Recovery

• Not enough DR capacity to run Production

• Recovery facility in same FEMA region

• Recovery team in same region as Production

• Production team responsible for recovery

• Recovery depends on “one” person

• DR “team” lacks application expertiseJD Edwards/Technical Application ExpertiseE1, Dev, Web, JAS, 3rd party tools, etc

• Out of date recovery plan, untested plan

• Incomplete testing, unsuccessful or infrequent testing

• DR is an IT exercise rather than Business Process Validation

Page 21: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

Rec

ove

ry P

oin

t O

bje

ctiv

e (R

PO

)

Recovery Time Objective (RTO)

Now we are ready to approach RPOs & RTOs

No DR

ElectronicBackup

RPO: 24 hoursRTO: 24 hours

Data Vaulting

RPO: 60 minutesRTO: <= 12 hours

High Availability

RPO: last successful transactionRTO: <= 2 hours

Minutes

Seconds

21

Days

Weeks

Tape Backup

RPO: 24 hoursRTO: 48 hours

NO DR

RPO: ?RTO: ?

How much data can you afford to lose?

How much downtime can you afford to have?

Page 22: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 22

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

3. Does Recoverability Matter?

4. What would it take to Prove Recoverability?

5. Eliminate single points of failure

6. Make the business case

Page 23: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 23

Make the business case

• “The Problem”• Common Drivers

- Compliance- Executive sponsor- Customers- An event

• Tips- Tie DR to business initiatives- Speak the truth- Show cost savings- Can you chargeback the business?

Page 24: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 24

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

3. Does Recoverability Matter?

4. What would it take to Prove Recoverability?

5. Eliminate single points of failure

6. Make the business case

Page 25: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 25

How can we permanently change the way our organization approaches disaster recovery?

1. Scratch out Disaster Recovery, write Recoverability

2. Define Recoverability

3. Does Recoverability Matter?

4. What would it take to Prove Recoverability?

5. Eliminate single points of failure

6. Make the business case

Think, Invest & Make Decisions toward Recoverability (not toward disaster recovery, where there is no assurance)

Page 26: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 26

Key Takeaways from Today

Page 27: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential 27

How do we embed Recoverability into our organization’s culture?

Key Takeaways from Today

Page 28: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

EXPERIENCE. INNOVATION. Velocity Proprietary and Confidential

Velocity Technology SolutionsQuestions?

28

Get your life back.

Control your Business.

No boundaries.

Go when you’re ready.

One size does not fit all.

Page 29: Disaster recovery: modernized best practices for Oracle's JD Edwards and beyond

© 2013 Velocity Technology Solutions, Inc.

EXPERIENCE. INNOVATION.

Disaster Recovery: Think, Invest & Make Decisions toward RecoverabilityFor more information:

[email protected], [email protected], 803-386-9680