Cloud Solutions
Private, public and hybrid environments connected securely to your office.
Explore service : Cloud SolutionsDisaster Recovery
Keep a second copy of critical systems at another site and plan how services can be restored after a failure.
Enquire about this service
Protect the data. Plan the recovery.
A second copy of data is only part of a recovery arrangement. You also need to know which applications must return first, where they can run and what connections and dependencies are required for staff to use them again.
EDISON covers Veeam backup and replication, SAN replication between sites and email disaster recovery. Planning begins with the business systems to protect and the amount of interruption and data loss your organisation can accept for each one.
- Backup and replication with Veeam
- SAN storage replication between sites
- Email disaster recovery
Backup and replication play different roles.
The recovery method should follow the failure you are preparing for and the systems that need to be restored.
| Part of the plan | What it addresses |
|---|---|
| Backup | Retained copies provide recovery points from which data or systems can be restored. Plan what is included, how frequently copies are made, how long they are kept and where they are stored. The ability to restore should be checked as part of the recovery arrangement. |
| Replication | A replica provides a copy at another location for a recovery or failover scenario. Veeam and SAN replication are within EDISON’s scope. The target system, available capacity, site connection and behaviour after a failure need to be considered alongside the copy itself. |
| Application recovery | Servers, storage and email have dependencies such as identity services, network access and related applications. A recovery sequence should identify these dependencies and the checks required before users resume work. It should also describe how normal operation will be resumed afterwards. |
Set recovery targets for each service.
Recovery point objective (RPO) is the acceptable amount of data loss measured in time. Recovery time objective (RTO) is the target time to restore a service after an interruption. These are planning targets to agree and test, with the infrastructure and recovery steps designed around them.
Different applications can have different targets. List their owners, priorities, current backup arrangements and the proposed recovery location. A recovery exercise should verify application access and data, as well as the process for deciding when recovery starts.
How would your critical systems recover?
Tell us which systems matter most, your current backup arrangement and acceptable interruption.