Recovery Point Objective (RPO) and Recovery Time Objective (RTO) should not be in the rear-view mirror for 2021 as organizations look to adjust their BCDR plans post Covid.
RPO Explained: Recovery Point Objective (RPO) is defined as the total amount of data that can be lost after a recovery from a failure. This essentially limits how far to roll back in time during recovery and defines the maximum allowable amount of lost data measured in time from a failure occurrence to the last valid backup.
Recovery point objective (RPO) is defined as the maximum amount of data – as measured by time – that can be lost after a recovery from a disaster, failure, or comparable event before data loss will exceed what is acceptable to an organization. An RPOs determines the maximum age of the data or files in backup storage needed to be able to meet the objective specified by the RPO, should a network or computer system failure occur.
For most organizations, their RPO & RTO are solid, well defined in their Cloud Native application environments. However, there are some who need to make modifications or broaden the scope of “Cloud.” More cloud applications, tools and business infrastructure moved to a virtual world during the pandemic. Contact Center & Unified Communications moved to the cloud quickly replacing legacy Calle Centers and PBX environments respectively. This was a big win for many IT organizations, however Data, especially in these communications deployments moved off-site to both internal cloud instances and external vendor environments. Areas to consider in this new environment:
- How do we add Vendor Contact Center & Omnichannel communications with our Data stores into our BCDR?
- How long can we continue if our Cloud VOIP environment went off-line?
- What is the RTO objective?
- What is the RPO objective?
- How will traffic & data be routed in the interim?
- What is essential for backup?
Some of these questions may seem trivial, however they are not if you’re in the Insurance, Financial Services or even Healthcare verticals. Call and Customer analytics are critical and if the Virtual Contact Center is in production but it can’t capture or retrieve necessary information easily within your CRM or other SaaS tools, what can you live with? Sure, the environment has failsafes to route calls to external Telephone Number, but there is no customer history, recording of inbound requests and more.
Another one often overlooked in the BDCDR plan is multi-cloud for evaluation. Why? Most likely you have solved if cloud region one fails and cloud region 2 takes over…. pretty easy right? However, have you considered the overall Cloud Connectivity Plan? You will want to consider how remote users or customers connect to your failover location in multi-cloud and would that impact egress charges leaving your backup region temporarily. Pulling data storage in large troves of capacity could burden your next invoice so you’ll want to be sure the architecture supports both cost and speed to recovery. Several options exist however the remote user connections will be the hardest to define and expect potential latency increase.
Consider a WAF to mitigate vendor lock-in or be agnostic to your Cloud environment. Read more here about What is a WAF or What is AWS WAF?
We support, design, and help plan for many disasters more as an insurance policy which must be cashed in at any given moment. Everything has or is moving to the cloud for your business, we always advise to leave no stone unturned.