3. DISASTER
Any event that has a negative impact on
your business continuity or finances could be termed a disaster.
4. WHYWEARETALKINGABOUT DR?
• Over 70% of businesses involved in a major fire either do not reopen, or subsequently fail
within 3 years of fire. (Source continuitycentral.com)
• 80% of businesses affected by a major
incident either never re-open or close within 18 months (SourceAxa)
• 70 percent of companies go out of business after a major data loss (Source
continuitycentral.com)
• 80% of businesses suffering a computer disaster, who have no disaster recovery plans, go
out of business. (Source “A BridgeToo Far”, IBM BusinessRecovery Service & Cranfield,
1993)
• A recent study from Gartner, Inc., found that 90 percent of companies that experience
data loss go out of business within two years.
• 80 percent of companies without well-conceived data protection and recovery strategies
go out of business within 2 years of a major disaster. (Source: US NationalArchives and
Records Administration)
5. RTO – RECOVERYTIME
OBJECTIVE
This is the duration of time and the service level to which a business
process must be restored after a disaster
6. RTO what it implies?
• Have a system that records 1000 transaction at hour
• Take a snapshot of a system at 03:00 am (every day)
• 10:00 am a disaster event occurs
• You spend 1 hour to sort things out for the backup (off-site, preparation, etc.)
• Recover operation takes 4 hours in order to get back to operate (at minimum
service level)
• 5 hours is the: RECOVERYTIME OBJECTIVE
7. RPO – RECOVERY POINT
OBJECTIVE
This describes the acceptable amount of data loss measured in time.
8. RPO –WHAT IT IMPLIES?
• Have a system that records 1000 transaction at hour
• Take a snaphot of a system at 03:00 am (every day)
• 10:00 am a disaster event occurs
• In this case we lost around 7000 transactions.
• 1000 transactions 03:00 04:00
• 1000 transactions 04:00 05:00
• …
• But: we are accepting 24 hours of data loss 24000 transactions (RPO)
11. Disaster Recovery & Cloud?
• On Demand
• We can allocate and release new resources whenever we need
• Cost Effective
• Pay as you go model.We pay only for resources that we are effectively
using
• Scalable
• We can scale freely and adapt our strategy thanks to autoscaling and
other mechanisms
• Secure
• Control doesn’t mean security
12. FOCUS ON DATABASES
We will focus on MySQL but you can apply to your infrastructure without
any problem.
25. Pilot light
We can let a little resource always active
that can help us to activate a whole
system
26. Replication
Basically pilot-light is based on database
replication strategies
For MySQL async replication is used as
base strategy
http://www.slideshare.net/corleycloud/m
ysql-scale-out-cloudparty-2013-milano-
talent-garden
45. DEPENDS ON
ASSUMPTIONS
We assume that we don’t need to scale out our database but that is
enough to scale it up only!
Resource allocation for new read replicas? How long does it takes?