Cloud computing presentation explanation.ppt

Cloud computing presentation explanation

1. UNIT-5
DISASTER RECOVERY

2. Chapter2: Security
1. Disaster Recovery.
2. Web Application Design.
3. Machine Image Design.
4. Privacy Design.
5. Database Management.
6. Data Security.
7. Network Security.
8. Host Security.
9. Compromise Response.

3. Unit-5
1. Disaster Recovery
2. Disaster Planning
3. Cloud Disaster Management
Case Studies
Types of Clouds
Cloud Centers in detail
Comparing Approaches
Xen
OpenNEbula
Eucalyptus
Amazon
Nimbus

4. 1. Disaster Recovery

5. Disaster recovery is the practice of making a system capable of
surviving unexpected or extraordinary failures.
A fire in data center that destroy all of the servers in that data
centers and the systems they support.
Every organization should have a documented disaster recovery
process and should test that process at least twice each year.
Virtualization supports automated disaster recovery.
If entire cloud infrastructure falls apart, you should have the
capabilities in place to restore it on internal servers , at
managed hosting services provider, or at another cloud provider
in minutes or hours.

6. 
There are 6 causes of data loss due to disaster
occurrence
Natural Disasters:
Mission critical application failure:
Network failure:
Network intrusion:
Hacking or malicious code:
System failure:

8. Disaster Recovery as a Service

9. Disaster recovery as a service is an upcoming service of cloud computing.
 It is a low cost service when compared to traditional disaster recovery.
It is flexible in replicating physically or virtually.
It provides application consistent recovery for some working applications
like SQL server.
It has pre-built options for virtual recovery environments including security,
network connectivity and server failover when continuously replication
among servers.
When disaster occurs we can take backup and we can run our
applications on service provided by disaster recovery until we get backup
to primary site.
Disaster recovery as a service to replicate critical servers and data centre
infrastructure in cloud.

10. 2. Disaster Planning

Deals with catastrophic failures that are extremely
unlikely to occur during the life time of a system.

Traditional availability planning:
Reasonably expected failures fall under this issue.

Disaster recovery planning:
We have to identify an acceptable recovery state
Develop process and procedures to achiever the recovery
state in the event of disaster.

13. 
Defining a disaster recovery plan involves two key
metrics:
Recovery Point Objective(RPO)
Recovery Time Objective(RTO)

14. Recovery Point Objective(RPO)
The recovery point objective identifies how much data you
are willing to lose in the event of disaster.
This value is typically specified in a number of hours or days
of data.
Example:
If you determine that it is OK to lose 24 hours of data, you must
make sure that the backups you’ll use for your disaster recovery
plan are never more than 24 hours old.

15. Recovery Time Objective(RTO)
Which identifies how much downtime is acceptable in the
event of a disaster.
Example:
If your RTO is 24 hours, you are saying that up to 24 hours may
elapse between the point when your system first goes offline
and the point at which you are fully operational again.

17. 
Disaster recovery plan offers the following benefit :
No downtime and no loss of data occur, no matter what the
disaster.

Nature of disaster :
Generally requires you to accept some level of loss, anything
else come with a significant price tag.

Determine an appropriate RPO and RTO is ultimately a
financial calculation:
At what point does the cost of data loss and downtime?
The right answer is radically different for different businesses.

18. 
Example:
Hurricane Katrina:
Traditional approach:
The cost of surviving with zero down time and zero data loss
could have been having multiple data centers in different
geographic locations.
Those data centers constantly synchronized.

Or
Cloud Service Approach
We need two distinct data centers from different infrastructure
providers with dedicated, high bandwidth connections between
the two.

19. 
The RPO

The RTO

Disasters in the Cloud:
Backups and data retention
Geographic redundancy
Organizational Redundancy