Of course, you can’t have a disaster recovery process in place without proper disaster recovery planning. By outlining the plan beforehand and making sure you have the right tools in place, you can develop a recovery plan that can protect your data, your business, and your customers in the event of a disaster, such as a cloud outage or a cyber attack like ransomware.
Cosa dovremmo includere nel nostro piano di Recovery in caso di calamità?
Backup Cloud
Disaster recovery starts with carefully identifying how you will back up your business’s data, applications, and workloads so they can be recovered and restored when needed.
Cloud backup-as-a-service provides automatic backups, unlimited scalability, routinely updated security, and doesn’t require new software or hardware—making this solution the most effective and streamlined method to create and store backups for recovery.
Not all cloud backup solutions are equal. Make sure that your disaster recovering planning utilizes a cloud backup solution that offers the following:
- Backups stored outside of the user’s account
- Ripristino granulare
- Recupero rapido
il Recovery Time Objective
In addition to the ability to back up and restore application data, disaster recovery planning also involves establishing certain metrics. The first of these is the recovery time objective or RTO. This is defined as the amount of time that an organization has deemed acceptable to recover from a disaster, usually aiming for that recovery to occur before the downtime creates significant consequences.
For example, let’s say an organization has identified an RTO of four hours and later experiences an outage that disables its infrastructure. In this scenario, the organization must have its applications back up and running within four hours, or the downtime will cause a severe break in business continuity.
Recovery Point Objective (RPO)
The second key metric in a disaster recovery plan is the recovery point objective or RPO. This is the maximum acceptable amount of data loss during a disaster event or outage before the amount of data lost exceeds the maximum threshold allotted within a business continuity plan. Put simply, this is the acceptable amount of data that can be lost before internal operations and end users are affected, but expressed as an amount of time.
Ad esempio, supponiamo che un’organizzazione esegua automaticamente il backup dei propri dati tramite il cloud ogni cinque ore e che in seguito subisca un’interruzione del servizio della durata di tre ore. Poiché la durata dell’interruzione non ha superato il punto dell’ultimo backup dei dati, l’organizzazione ha rispettato il proprio RPO, in quanto è in grado di recuperare dati sufficienti per riprendere le operazioni senza interruzioni significative né perdite critiche di dati.
Semplifica la pianificazione del ripristino di emergenza con Clumio
An enterprise’s disaster recovery capabilities are only as good as the tools it uses. Clumio’s industry-leading cloud backup-as-a-service platform provides swift and efficient disaster recovery via innovative rapid restore capabilities that maintain and support business continuity in the face of a disaster event — all while meeting RTOs and RPOs. These features include:
- Backup rapidi dei dati AWS da qualsiasi regione all’interno dell’organizzazione
- Backup “air-gapped” archiviati al di fuori dell’account principale e della regione, che garantiscono una protezione sicura da ransomware e altri attacchi informatici
- Ripristino dei dati granulare e flessibile per un Recovery più rapido
