Skip to main content

Recovery Objective

Backups

Our platform's backups are always generated in full. Database has daily, weekly, quarterly and annual full backup schedules. The daily backups last one week, the weekly ones twelve weeks, the quarterly ones three years, and the annual ones fifteen years.

The details are shown in the following table:

TypeDateHourStorage
1AnnualJanuary 1st6:30 am15 years
2MonthlyEvery 1st Monday of the month6:00 am3 years
3WeeklyEvery Sunday5:30 am84 days
4DailyEveryday5:00 am7 days

Recovery objectives

ObjectiveDefinitionTimeDescription
1. Recovery Time Objective (RTO)Defines the maximum tolerable time limit within which the service must be restored to minimum acceptable conditions. If a disaster occurs and the service must be available immediately, the RTO is zero. However, if one hour of total service interruption is tolerated, the RTO is one hour.15 minutesThe platform is classified as critical so the backups are maintained on a permanent basis. The total restoration of a backup is done in 15 minutes, so this is the time it takes for the recovery.
2. Recovery Point Objective (RPO)Defines the maximum tolerable data loss that can be accepted in a disaster situation. For example, if a disaster occurs and the backup of the information is weekly, it means that after recovering the service the data from one week before the incident will be available, the RPO is one week. If the backup is on-line and there is no acceptable data loss, the RPO is zero.0 minutesConsidering that there are backups generated per second, the recovery target has 0.
3. Maximum Tolerable Period of Disruption (MTPD)Defines the maximum time in which the service must operate normally before generating losses that cannot be assumed1 monthThe relationship between monthly operating costs and revenues is almost the same, so if the service is stopped completely for more than 1 month, the losses generated can be unsustainable.

Impact over time

A service interruption can occur at any time; however, if it occurs at a certain point in time, the severity of the interruption may be greater. For this purpose, the impact of an interruption on the function at different moments in time will be analyzed.

Monthly analysis

In the monthly analysis, the first and last month of the year the ARM service usage decreases due to platform freezing and customer vacations.

MonthImpact
JanuaryMedium
FebruaryHigh
MarchHigh
AprilHigh
MayHigh
JuneHigh
JulyHigh
AugustHigh
SeptemberHigh
OctoberHigh
NovemberHigh
DecemberMedium

Weekly analysis

In weekly analysis the first and last week of the month in most of the cases there is the closing or the beginning of projects so the demand of the service can increase.

WeekImpact
Week 1High
Week 2Medium
Week 3Medium
Week 4High

Daily analysis

During any day of the week there can be a high impact from the use of the service, however most customers do not work on weekends.

DayImpact
MondayHigh
TuesdayHigh
WednesdayHigh
ThursdayHigh
FridayHigh
SaturdayLow
SundayLow

Hour analysis

The hours in which the customer is during working hours are listed as high.

HourImpact
0Low
1Low
2Low
3Low
4Low
5Low
6Low
7High
8High
9High
10High
11High
12Medium
13Medium
14High
15High
16High
17High
18High
19High
20Medium
21Medium
22Low
23Low