A highly resilient business function example includes a
hundred people who work in six buildings. A disaster occurring in one of the buildings would displace a portion of the
team. Their colleagues in the other buildings would continue
to perform their duties, while the affected group implemented
its recovery plan. From the user’s perspective, the function
was never out of action. It is possible that a meeting or a
phone call or two might have been interrupted when the event
occurred, but the bulk of the function remains in operation.
Maximum allowable downtime for a function with this type
of physical disposition could be a few minutes, or possibly
zero.
The RTO for any of the six groups in this function necessarily
would be longer. Depending on the complexity of the recovery
strategy, RTO could be one business day or more.
Technology HRC scenarios will span a broad spectrum of
possibilities, based on their geo-dispersion, and the type of
recovery environment. In all cases, MAD could be very low.
The recovery time objective will depend on the situation. Two
different scenarios will be considered.
The simplest (and least resilient) technology HRC
example is a hot-hot environment, where one instance is
deployed at the production site, and the second site is the
recovery environment. An automated recovery tool could
shift production traffic to the recovery environment nearly
instantaneously. Both MAD and RTO could be measured in
seconds.
On the higher segment of the resilience spectrum, a technology HRC could be deployed in a dozen or more production locations (“CRL-X”). In this case, a very low MAD value
probably drove the need for high resilience in the first place. If
a disaster disabled one of the production sites, load balancing
technology could redirect traffic among the surviving instances
until the disabled instance is recovered. The RTO would depend
Egenera Cloud Suite® Build Automated Scalable Secure Personalized Cost Effective Recovery as a Service offerings
Find out more at:
www.egenera.com
