Cloud Disaster Recovery as the Answer to a Site You Can No Longer Reach

Many disasters share a common effect: they make an organization's primary site unreachable. A fire, a flood, a prolonged power or network outage, or physical damage can render the site where an organization's systems live inaccessible, taking its operations down with it. Cloud disaster recovery answers this by placing the organization's recovery capability somewhere the disaster cannot reach, in the cloud, so the organization can recover even when its own site cannot be reached. Understanding cloud disaster recovery as the answer to a site you can no longer reach is how an organization sees why recovering in the cloud matters, recognizing that a recovery capability located at the same site as the systems it protects fails when that site is unreachable, so placing recovery in the cloud, beyond the reach of a local disaster, is what lets the organization recover when its primary site cannot be reached at all.

The Problem of a Shared Fate

Recovery capability located at the same site as the primary systems shares their fate, so a disaster making the site unreachable takes the recovery capability with it. This shared fate is the weakness cloud disaster recovery addresses. The problem of a shared fate is why local recovery can fail, because recovery capability, backups and recovery systems, located at the same site as the primary systems shares the site's fate, so a disaster that makes the site unreachable, a fire, flood, or outage, takes the recovery capability down along with the primary systems, leaving the organization unable to recover because its means of recovery was at the same unreachable site, which is the weakness that Cloud disaster recovery addresses, so an organization relying on recovery capability at the same site as its systems risks losing both to one disaster, a shared fate that cloud disaster recovery avoids by placing recovery beyond the site that the disaster makes unreachable.

Recovery Beyond the Disaster's Reach

Cloud disaster recovery places the recovery capability in the cloud, beyond the reach of a local disaster, so a disaster making the primary site unreachable does not affect the cloud-based recovery. This separation is what lets the organization recover. Recovery beyond the disaster's reach is the core of cloud disaster recovery's answer, because placing the recovery capability in the cloud locates it beyond the reach of a local disaster, so a fire, flood, or outage that makes the primary site unreachable does not affect the cloud-based recovery capability, which remains available to recover the organization's systems and data, so the separation of the recovery capability from the primary site is what lets the organization recover when the site cannot be reached, which is precisely the situation many disasters create, so cloud disaster recovery's placement of recovery beyond the disaster's reach is what makes recovery possible when the organization's own site is unreachable and local recovery would share the site's fate.

Recovering Operations in the Cloud

Cloud disaster recovery not only keeps data beyond the disaster's reach but can bring operations up in the cloud, so the organization can keep running even while its primary site remains unreachable. Recovering operations in the cloud maintains continuity through the disaster. Recovering operations in the cloud extends the answer to operational continuity, because cloud disaster recovery can bring the organization's systems up in the cloud, not just keep its data safe there, so the organization can resume operating in the cloud even while its primary site remains unreachable, which maintains continuity through a disaster that would otherwise halt operations until the site could be reached again, so cloud disaster recovery answers the unreachable-site problem not just by protecting data beyond the disaster's reach but by letting the organization operate from the cloud, keeping it running through the disaster rather than down until its primary site becomes reachable, which for many organizations is the difference between weathering a disaster and being halted by it.

Ransomware Makes a Site Unreachable Too

Ransomware can make a site's systems effectively unreachable by encrypting them, so cloud disaster recovery with immutable copies answers ransomware as it answers physical disasters. Recovering clean systems in the cloud restores an organization locked out by ransomware. Ransomware making a site unreachable too extends the answer to ransomware, because a ransomware attack can render a site's systems effectively unreachable by encrypting them, locking the organization out of its own systems much as a physical disaster makes a site inaccessible, so cloud disaster recovery answers ransomware as it answers physical disasters, keeping immutable copies, unalterable during retention even by a compromised administrator, in the cloud and recovering clean systems there, which restores an organization locked out by ransomware, so cloud disaster recovery's answer to an unreachable site applies to the ransomware that makes systems unreachable through encryption, letting the organization recover clean systems in the cloud when ransomware has made its own site's systems unusable.

Testing the Unreachable-Site Scenario

An organization should test recovering as if its primary site were unreachable, confirming cloud disaster recovery works when the site cannot be reached rather than assuming it does. Testing this scenario verifies the answer to the problem it addresses. Testing the unreachable-site scenario is how an organization confirms the answer, because cloud disaster recovery is meant to work when the primary site cannot be reached, so testing recovery as if the site were unreachable, recovering entirely from the cloud, confirms the capability works in the scenario it addresses rather than assuming it does, which verifies that the organization can genuinely recover when its site is unreachable, so an organization should test the unreachable-site scenario specifically, confirming its cloud disaster recovery recovers systems and data from the cloud without relying on the primary site, which gives the organization grounded confidence that cloud disaster recovery will answer the unreachable-site problem when a real disaster makes its primary site impossible to reach.

Recovery That Survives the Disaster

Cloud disaster recovery as the answer to a site you can no longer reach means understanding the problem of a shared fate, placing recovery beyond the disaster's reach, recovering operations in the cloud, applying the answer to ransomware, and testing the unreachable-site scenario. Understanding this is how an organization sees why recovering in the cloud matters, recognizing that recovery capability at the same site as the systems it protects fails when the site is unreachable, so placing recovery in the cloud lets the organization recover when its primary site cannot be reached, which is the effect many disasters share, making cloud disaster recovery an answer to the common situation of a site an organization can no longer reach when a disaster strikes it.