Orka on AWS: Recovery Objectives
The recovery time objectives and the recovery point objectives for your Orka on AWS infrastructure and application.
Quick navigation
Jump to: Reporting issues | Definitions | Recovery objectives
Reporting issues
MacStadium handles all issues with your Orka cluster and respective AWS account and services.
If you experience any issues, submit a ticket through the MacStadium portal.
For more information about the available support tiers, see here.
For more information about how MacStadium support works, see here and here.
Definitions
| Term | Definition |
|---|---|
| Recovery Time Objective (RTO) | Π’he amount of time an application or a component can be down without causing significant damage to the business. |
| Recovery Point Objective (RPO) | The amount of data that can be lost before significant harm to the business occurs. RPO is expressed as a time measurement from the loss event to the most recent preceding backup. |
| Infrastructure | The AWS infrastructure of your Orka on AWS solution (i.e. the components of your Orka VPC and the VPC peering connection). |
| Application | The software layer of your Orka on AWS solution (i.e. the Orka virtualization layer and the interface layer). |
Recovery objectives
Infrastructure
* RPO is based on the default backup policy. If you want more frequent backups, submit a ticket through the MacStadium portal.
** RTO and RPO relate to the process of configuring and sending a new VPC peering request to re-establish the connection.
Application
| Component | RTO | RPO |
|---|---|---|
| API | 10min | 0s |
| Web UI | 10min | 0s |
| Operator | 10min | 0s |
| Nodes | 10min | 0s |
See also
Updated 12 months ago