disaster recovery modernized best practices for jd edwards beyond n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Disaster Recovery — Modernized Best Practices for JD Edwards & Beyond PowerPoint Presentation
Download Presentation
Disaster Recovery — Modernized Best Practices for JD Edwards & Beyond

Loading in 2 Seconds...

play fullscreen
1 / 42

Disaster Recovery — Modernized Best Practices for JD Edwards & Beyond - PowerPoint PPT Presentation


  • 73 Views
  • Uploaded on

Disaster Recovery — Modernized Best Practices for JD Edwards & Beyond. Presented by Andy Chase & Paul Shearer December 4, 2013. Introduction to Paul Shearer. Solution Architect 15 years JD Edwards experience Managed E1 Practice for Fortune 50 company

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Disaster Recovery — Modernized Best Practices for JD Edwards & Beyond' - vienna


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
disaster recovery modernized best practices for jd edwards beyond

Disaster Recovery—Modernized Best Practices for JD Edwards & Beyond

Presented by Andy Chase & Paul ShearerDecember 4, 2013

introduction to paul shearer
Introduction to Paul Shearer
  • Solution Architect
  • 15 years JD Edwards experience
  • Managed E1 Practice for Fortune 50 company
  • Designed & Implemented HA solutions for multiple clients
  • Designed and implementation of DR solutions for multiple clients
  • Successfully completed multiple E1 upgrade projects
  • Recovered 12 customers in DR exercises
  • Published two technical whitepapers with Microsoft on ERP virtualization and Platform conversions
introduction to andy chase
Introduction to Andy Chase
  • Disaster Recovery AE & SME
  • Began disaster recovery career at the age of 13 and has worked with over 100 companies since 2001 to improve their recovery capabilities
what constitutes a disaster
What constitutes a disaster?

flood

supply chain disruption

epidemic/pandemic

fire

terroristevent

cyberattack

hurricane

tornado

utilityoutage

sabotage

ITfailure

tsunami

severeweather

health & safety incident

haz mat explosion

poweroutage

environmentalaccident

telecommunicationsfailure

earthquake

what constitutes a disaster1
What constitutes a disaster?

flood

supply chain disruption

epidemic/pandemic

fire

terroristevent

cyberattack

hurricane

tornado

utilityoutage

sabotage

ITfailure

tsunami

severeweather

health & safety incident

haz mat explosion

poweroutage

environmentalaccident

telecommunicationsfailure

earthquake

most disaster recovery discussions begin here
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

Tape Backup

Recovery Point Objective (RPO)

Tape Backup

How much downtime can you afford to have?

Days

Recovery Time Objective (RTO)

Weeks

Minutes

most disaster recovery discussions begin here1
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

Data Vaulting

Recovery Point Objective (RPO)

How much downtime can you afford to have?

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

most disaster recovery discussions begin here2
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

Data Vaulting

Recovery Point Objective (RPO)

Tape

Backup

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

most disaster recovery discussions begin here3
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

Data Vaulting

ElectronicBackup

Recovery Point Objective (RPO)

Tape

Backup

RPO: 24 hours

RTO: 24 hours

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

most disaster recovery discussions begin here4
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

Data Vaulting

Transaction Vaulting

RPO: 60 minutes

RTO: <= 12 hours

ElectronicBackup

Recovery Point Objective (RPO)

Tape

Backup

RPO: 24 hours

RTO: 24 hours

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

most disaster recovery discussions begin here5
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

High Availability

RPO: last successful transaction

RTO: <= 2 hours

Data Vaulting

TransactionVaulting

RPO: 60 minutes

RTO: <= 12 hours

ElectronicBackup

Recovery Point Objective (RPO)

Tape

Backup

RPO: 24 hours

RTO: 24 hours

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

most disaster recovery discussions begin here6
Most Disaster Recovery Discussions Begin Here

Seconds

How much data can you afford to lose?

High Availability

RPO: last successful transaction

RTO: <= 2 hours

Data Vaulting

Transaction Vaulting

This is inherently broken!

RPO: 60 minutes

RTO: <= 12 hours

ElectronicBackup

Recovery Point Objective (RPO)

Tape

Backup

RPO: 24 hours

RTO: 24 hours

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

disaster recovery benchmark data
Disaster Recovery “Benchmark” Data
  • 10* Volunteers & 2 Questions
  • Out of one thousand attendees at Collaborate, if the Keynote speaker asked…
      • How many organizations have already invested in disaster recovery software, infrastructure or services?
      • What percentage of you are completely confident that your team could recover those applications & data in the event of a disaster?
slide14

You are not alone…

8% of federal IT executives are completely confident that their agency could recover 100 percent of its data in the event of a disaster
if i were a cio
“If I were a CIO…”
  • “I would tear up my DR plan & cease spending on DR completely.”
  • Why invest toward something that only works 10-27% of the time?
        • Better odds in Vegas!
what do these numbers reveal about dr
What do these numbers reveal about DR?

and Proven Recoverability.

There is a GAP between Disaster Recovery

why the gap
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
why are most dr discussion inherently broken
Why are most DR discussion inherently broken?

Seconds

How much data can you afford to lose?

High Availability

RPO: last successful transaction

RTO: <= 2 hours

Data Vaulting

Transaction Vaulting

They Assume Recoverability!

RPO: 60 minutes

RTO: <= 12 hours

ElectronicBackup

Recovery Point Objective (RPO)

Tape

Backup

RPO: 24 hours

RTO: 24 hours

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

how can we permanently change the way our organization approaches disaster recovery
How can we permanently change the way our organization approaches disaster recovery?
  • Scratch out Disaster Recovery, write Recoverability
    • Disaster RecoveryRecoverability Plan
    • Disaster RecoveryRecoverability Spending
    • Disaster RecoveryRecoverability Solution
    • Disaster RecoveryRecoverabilityProjects
how can we permanently change the way our organization approaches disaster recovery1
How can we permanently change the way our organization approaches disaster recovery?
  • Scratch out Disaster Recovery, write Recoverability
  • Define Recoverability
the velocity definition of recoverability
The Velocity definition of Recoverability

The Power to Recover Your Business Applications & Data

how can we permanently change the way our organization approaches disaster recovery2
How can we permanently change the way our organization approaches disaster recovery?
  • Scratch out Disaster Recovery, write Recoverability
  • Define Recoverability
  • Does Recoverability Matter?
does recoverability matter
Does Recoverability Matter?
  • Jewelry maker hasn’t tested DR in almost 5 years
    • 3rd party DR contract $50k/year
    • $250k spent without a Recoverability ROI
  • University cancels annual DR Test due to budget cuts
    • Test estimated to cost $10k T&E
    • 3rd party DR contract over $130,000/year
  • Many companies place old infrastructure in DR facility
    • “The business will understand if we have a disaster”
      • Will they? For some, maybe yes.
      • Boston CIO blog after terrorist attack
        • Communications Provider learns from Boston CIO
does recoverability matter1
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, HIPPA, etc does not actually mean they are Recoverable?
when does recoverability matter
When does Recoverability matter?
  • Dallas construction materials company
  • No DR, tape backups only, JDE & WMS highly integrated
  • 3 locations:
    • Dallas HQs, Call Center, Distribution & Data Center
    • California Distribution Center
    • Maryland Distribution Center
  • CFO requests 3 site real-time replication

What changed?

  • CEO finally cares about Recoverabilityafter capturing cell phone camera footage of tornado forming across parking lot!
when does recoverability matter1
When does Recoverability matter?
  • Northeast retail chain
  • Internal DR @ secondary site, using Mimix HA
  • Company funded & implemented DR several years ago
  • Everything is current, tested & documented
  • CIO now wants to outsource DR to the Cloud

What changed?

  • DR facility too close, told by insurance provider they will lose coverage if they don’t move DR site outside region
how can we permanently change the way our organization approaches disaster recovery3
How can we permanently change the way our organization approaches disaster recovery?
  • Scratch out Disaster Recovery, write Recoverability
  • Define Recoverability
  • Does Recoverability Matter?
  • What would it take to Prove Recoverability?
slide31
What would it take to be completely confident that you could recover all your applications & data in the event of a disaster?
what would it take to prove recoverability
What would it take to Prove Recoverability?
  • Plan it – Define all components required (create a matrix)
  • Build it – Implement all the pieces to the puzzle
  • Test it – Keep testing all pieces until you get it right
  • Prove it – Testing that includes business users & processes
  • Maintain it – Keep yourself Recoverable at ALLtimes
  • Guard it – Eliminate every potential single point of failure
  • The goal is for everyone in your business to be completely confident you are Recoverable!
how can we permanently change the way our organization approaches disaster recovery4
How can we permanently change the way our organization approaches disaster recovery?
  • Scratch out Disaster Recovery, write Recoverability
  • Define Recoverability
  • Does Recoverability Matter?
  • What would it take to Prove Recoverability?
  • Eliminate single points of failure
single points of failure in disaster recovery
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 expertise
    • JD Edwards/Technical Application Expertise
    • E1, 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
dr is not that hard
DR is not that hard…
  • Billy Beane: We want you at first base.
  • Scott Hatteberg: But, I've always played catcher.
  • Billy Beane: It's not that hard, Scott. tell him, Wash.
  • Ron Washington: It's Incredibly hard.
disaster recovery vs proven recoverability
Disaster Recovery vs. Proven Recoverability
  • Think, Invest & Make Decisions toward Recoverability
  • (not toward disaster recovery, where there is no assurance)
how can we permanently change the way our organization approaches disaster recovery5
How can we permanently change the way our organization approaches disaster recovery?
  • Scratch out Disaster Recovery, write Recoverability
  • Define Recoverability
  • Does Recoverability Matter?
  • What would it take to Prove Recoverability?
  • Eliminate single points of failure
  • Think, Invest & Make Decisions toward Recoverability
  • (not toward disaster recovery, where there is no assurance)
common disaster recovery configurations
Common Disaster Recovery Configurations

Seconds

How much data can you afford to lose?

High Availability

RPO: last successful transaction

RTO: <= 2 hours

Data Vaulting

RPO: 60 minutes

RTO: <= 12 hours

ElectronicBackup

Recovery Point Objective (RPO)

Tape

Backup

RPO: 24 hours

RTO: 24 hours

No DR

How much downtime can you afford to have?

RPO: 24 hours

RTO: 48 hours

NO DR

RPO: ?

RTO: ?

Days

Weeks

Minutes

Recovery Time Objective (RTO)

key takeaways from today1
Key Takeaways from Today

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

velocity technology solutions

Get your life back.

One size does not fit all.

No boundaries.

Questions?

Control your Business.

Go when you’re ready.

Velocity Technology Solutions
slide42

April 7-11, 2014

The Venetian and Sands Expo Center

Las Vegas, Nevada

QuestDirect.org/COLLABORATE

Attend COLLABORATE 14 to hear high-level,

strategic education for the JD Edwards audience. Register through Quest to receive exclusive JD Edwards updates, materials and networking events.

Registration OPEN! Early Bird rates end February 12, 2014.