Disaster recovery projects centered on recovery point and recovery time objectives are inherently broken. For decades companies have been taking that same approach to disaster recovery, asking the same questions, delivering the same message and investing countless dollars while expecting (but rarely achieving) better results. Find out how you can permanently change the way your organization approaches JD Edwards disaster recovery, where every dollar spent and every decision made finally produces an ROI with tangible results.
2. What constitutes a disaster?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
2
3. Most Disaster Recovery Discussions Begin Here
Recovery Point Objective (RPO)
Seconds
How much data can
you afford to lose?
Tape Backup
Tape Backup
How much downtime
can you afford to have?
Days
Weeks
Recovery Time Objective (RTO)
EXPERIENCE. INNOVATION.
Minutes
Velocity Proprietary and Confidential
3
4. Most Disaster Recovery Discussions Begin Here
Recovery Point Objective (RPO)
Seconds
How much data can
you afford to lose? Transaction
Data
Vaulting
Vaulting
Electronic
Backup
Tape
Backup
High
Availability
RPO: last successful
transaction
RTO: <= 2 hours
RPO: 60 minutes
RTO: <= 12 hours
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
Recovery Time Objective (RTO)
EXPERIENCE. INNOVATION.
Minutes
Velocity Proprietary and Confidential
4
5. Most Disaster Recovery Discussions Begin Here
Recovery Point Objective (RPO)
Seconds
How much data can
you afford to lose? Transaction
Data
Vaulting
Vaulting
Electronic
Backup
Tape
Backup
High
Availability
RPO: last successful
transaction
RTO: <= 2 hours
RPO: 60 minutes
RTO: <= 12 hours
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
Recovery Time Objective (RTO)
EXPERIENCE. INNOVATION.
Minutes
Velocity Proprietary and Confidential
5
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%
• 27.5%
• 26%
• 10.5%
• 27%
• 10.5%
• 20.5%
• 6.7%
SCUG
HUG
KC RUG
NY/NJ RUG
MARUG
RMUG
OCEAN
InFocus
EXPERIENCE. INNOVATION.
9/11
9/12
10/18
10/18
10/21
10/25
11/19
12/4
Velocity Proprietary and Confidential
6
7. What do these numbers reveal about DR?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
7
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
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
8
9. Why are most DR discussion inherently broken?
Recovery Point Objective (RPO)
Seconds
How much data can
you afford to lose? Transaction
Data
Vaulting
Vaulting
Electronic
Backup
Tape
Backup
High
Availability
RPO: last successful
transaction
RTO: <= 2 hours
RPO: 60 minutes
RTO: <= 12 hours
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
Recovery Time Objective (RTO)
EXPERIENCE. INNOVATION.
Minutes
Velocity Proprietary and Confidential
9
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
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
10
11. How can we permanently change the way our
organization approaches disaster recovery?
1.
Scratch out Disaster Recovery, write Recoverability
2.
Define Recoverability
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
11
12. The Velocity definition of Recoverability
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
12
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?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
13
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?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
14
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?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
15
17. What would it take to Prove Recoverability?
1)
2)
3)
4)
5)
6)
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 ALL times
Guard it – Eliminate every potential single point of failure
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
17
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
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
19
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 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
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
20
21. Now we are ready to approach RPOs & RTOs
Recovery Point Objective (RPO)
Seconds
How much data can
you afford to lose?
Electronic
Backup
Tape
Backup
No DR
High
Availability
RPO: last successful
transaction
RTO: <= 2 hours
Data
Vaulting
RPO: 60 minutes
RTO: <= 12 hours
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
Recovery Time Objective (RTO)
EXPERIENCE. INNOVATION.
Minutes
Velocity Proprietary and Confidential
21
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
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
22
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?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
23
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
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
24
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
(not toward disaster recovery, where there is no assurance)
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
25
26. Key Takeaways from Today
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
26
27. Key Takeaways from Today
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
27
28. Get your life back.
One size does not fit all.
Control your Business.
No boundaries.
Go when you’re ready.
Velocity Technology Solutions
Questions?
EXPERIENCE. INNOVATION.
Velocity Proprietary and Confidential
28