All Collections
What are the typical RPO and RTO numbers for an Oracle database managed by Tessell?
What are the typical RPO and RTO numbers for an Oracle database managed by Tessell?

Near zero RPO and RTO for your mission-critical databases

Bakul Banthia avatar
Written by Bakul Banthia
Updated over a week ago

The Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for an Azure Tessell for Oracle instance can vary depending on the specific needs and requirements of your application, as well as the size and complexity of your database.
That being said, Tessell for Oracle provides a number of out-of-the-box patented features and options that can help you achieve your desired RPO and RTO targets.





Proportional to transactions since last full backup



<5 mins

Availability Machine: The Availability machine leverages cloud infrastructure technologies such as block storage, snapshots, and blob storage to make its content available across availability zones and regions.
In addition to automated full backups at regular intervals, the archive logs are captured every 5 minutes. This helps make this data available for recovery (zero data loss) at the replica when needed.
Azure Tessell for Oracle creates backups of your database at regular intervals, which can be used to recover your data in the event of a failure. This can be set up by choosing the desired RPO SLA at the time of provisioning

Point-in-time recovery: Azure Tessell for Oracle also supports point-in-time recovery (PITR), which allows you to restore your database to a specific point in time within the retention period as per your choice

Did this answer your question?