1. Presented by Abdiel Louis and Tim Krupinski
LUMINR
Business Continuity and
Disaster Readiness
2. Abdiel Louis
Co-Founder at Luminr and a Senior IT
Architect in the payment industries,
where he leads and designs Private
Cloud and Identity Management
solutions between cross functional
platforms safeguarding global clients.
He has over ten years of experience
integrating and delivering technology
solutions.
Solution Architect with SageLogix
and Co-Founder at Luminr,
specializing in platform migrations
and operational efficiency
improvement. He has worked on
platforms in the Financial,
Healthcare, Enterprise Support and
Government industries since 2005.
About.(Luminr)
Tim Krupinski
3. Business Drivers
• How: Storage
• What: Disaster Recovery
• Why: Data Protection
• When: Disaster Recovery
• Challenges and Special Considerations
• Business Continuity and Disaster Readiness Steps
4. What is Disaster Recovery?
Disaster recovery (DR) : set of policies and procedures to
enable the recovery or continuation of critical business and it
supporting technological infrastructure following a disaster.
• Some Popular Culprits
• Natural Disasters
• Fire or Earthquake
• Terrorist Attacks
• Not-So-Popular Culprits
• Junior Admins
• “Accidental” loss of data
5. A Look at the Data
In a 2012 study, Enterprises reported that
• Nearly 50% of system downtime was caused by Human Error or
Unexpected Updates & Patching
• Only 5% of downtime caused by an actual disaster
2011 Acronis Study of 6,000 IT Organizations
• 86% of companies experienced downtime in the previous 12 months
• 60% caused by human error
• Average downtime was over 2 days
• Average cost of downtime was $366,000 per year
6. Why is Data Protection Important?
Data Accessibility
• Anywhere
Encryption
• In-transit
• At rest
Encryption Mechanism
• AES 256
Security boundaries
• Logical
• Physical
7. How to Manage and Allocate Storage?
Sizing Critial Data
• 1:4 (1GB of data requires 4GB capacity)
Identifying the Cost and Probability of Downtime
• Fitting into your existing infrastructure
• Third party
Cloud Storage
• Azure
• Amazon
• Iron Mountain, and more…
8. When is Disaster Recover Appropriate?
• Business Directive dependent
• Backup ALONE is NOT Disaster Recovery
• Network
• Access
• Bandwidth
• Data Categories/Sets
• Be Strategic; Not Reactionary
• Rentention
• Finanacial institutions - 7 years
9. Challenges and Special Considerations
• Rules, regulations, and restrictions
• Data Security/Location Requirements
• Off Site Requirements
• Recovery Time Objectives (RTO)
• Infrastructure Compatibility
11. Business Continuity and Disaster Readiness
1. Identify and list critical business activities that satisfy
your business operations
2. Identify the critical business information needed for
these activities to complete successfully
3. Create a checklist of your core system processes
• Functional area
• Sequential approach to come back online
• Disaster recovery test
4. Following your checklist, can you recover post
disaster/impact, smoothly without affect your
bottom-line?
