A disaster recovery plan helps an organization to deal with possible incidents and quickly recover the functionality. This page describes our recovery strategy.

Concept

A disaster recovery plan is a structured approach that describes how an organization can quickly resume work after an incident. Such a plan helps an organization deal with data loss and recover system functionality, so it can get back to work.

Konverso recovery strategy

• Making environment backups at least once every 24 hours.

• Backup hosts are designed to be in a region different from the VM to be backed up. For instance, backup.konverso.ai is located in France.

• Encrypting backups. Only the team members who are granted access to the environment may have access to the key to decrypt the backup data.

• Storing solution configuration and settings in Bitbucket customer repositories with versioning and access restriction.

• With the DB and the solution code, any environment can be recreated and returned to full functionality in less than 2 hours.

RTO and RPO

Recovery time objective (RTO) is the maximum delay between the service failure and its recovery. RTO defines the acceptable time for service downtime.

• Our RTO is 2 hours.

Recovery point objective (RPO) is the maximum period of time since the last data recovery point. It defines how much data loss could occur in case of an incident.

• Our RPO is 24 hours.

Recovery tests

Recovery tests help to understand the capability of the software to recover from any kinds of failures, including software crashes, hardware crashes, and network failures.

We run random full recovery tests on one customer environment at least once per quarter.