No products in the cart.
Natural disaster or accidental incidents may cause damage to physical computing resources
anytime. Contrary to traditional computing approach, disaster or damages of computing
devices at clients’ location can no more cause much harm in cloud computing model. Moreover,
the planning and protection system of cloud data centers can provide safety in case of disaster
as discrete silos are avoided in cloud model and different data centers of a vendor spread over
different geographic locations remain well-connected through network.
Disaster recovery planning involves decisions on two key factors: recovery point objective
(RPO) and recovery time objective (RTO). The recovery point objective determines or refers to
the maximum volume of data which can be compromised in case of disaster. Here, the volume
FIG 19.8: SLA lifecycle
SLA
Lifecycle
Defining
Contract
SLA publishing
by provider
and
Discovery by
consumer
SLA de-commissioning
during termination of
contract
Operationalization:
Monitoring,
accounting and
enforcing SLA
terms and conditions
Negotiation
regarding terms and
conditions between
provider and consumer
5
1
2
4
3341
Cloud Management and a Programming Model Case Study
is denoted in terms of storage duration like number of hours or days. For instance, if it is
decided that data which is already eight hours old cannot be compromised, then there should
be a plan to create backup at not more than eight hours’ interval.
The recovery time objective determines the acceptable system downtime in case of disaster.
If this downtime is determined as six hours, then system must have to become operational
within six hours after breaking down for any reason.
Recovery point objective and recovery time objective are two key factors in disaster recovery
planning in computing
Natural disaster or accidental incidents may cause damage to physical computing resources
anytime. Contrary to traditional computing approach, disaster or damages of computing
devices at clients’ location can no more cause much harm in cloud computing model. Moreover,
the planning and protection system of cloud data centers can provide safety in case of disaster
as discrete silos are avoided in cloud model and different data centers of a vendor spread over
different geographic locations remain well-connected through network.
Disaster recovery planning involves decisions on two key factors: recovery point objective
(RPO) and recovery time objective (RTO). The recovery point objective determines or refers to
the maximum volume of data which can be compromised in case of disaster. Here, the volume
FIG 19.8: SLA lifecycle
SLA
Lifecycle
Defining
SLA
Contract
SLA publishing
by provider
and
Discovery by
consumer
SLA de-commissioning
during termination of
contract
Operationalization:
Monitoring,
accounting and
enforcing SLA
terms and conditions
Negotiation
regarding terms and
conditions between
provider and consumer
5
1
2
4
3341
Cloud Management and a Programming Model Case Study
is denoted in terms of storage duration like number of hours or days. For instance, if it is
decided that data which is already eight hours old cannot be compromised, then there should
be a plan to create backup at not more than eight hours’ interval.
The recovery time objective determines the acceptable system downtime in case of disaster.
If this downtime is determined as six hours, then system must have to become operational
within six hours after breaking down for any reason.
Recovery point objective and recovery time objective are two key factors in disaster recovery
planning in computing