Last reviewed: April 9, 2025
📘 In this article:
RPO Compliance Analysis
RPO (Recovery Point Objective) defines how much data loss is acceptable in the event of a failure.
ArchTechLytics compares your declared RPO against your actual backup and replication configurations — bridging the gap between design intent and implementation reality.
⏱️ How It Works
You define an RPO (e.g., 4 hours) in your system settings.
ArchTechLytics then analyzes:
- Backup frequency
- Backup retention duration
- Geo- or zone-redundancy
- Presence of site recovery or replication
Based on this, it evaluates if your configuration truly supports the RPO you’ve declared.
Real-world example:
If the system’s RPO is 4 hours, but the VM backup only runs every 6 hours, the TechLytic will fail — triggering both a scoring penalty and a recommended action.
🔍 Example TechLytic
The following is one of several RPO-related TechLytics used to enforce compliance:
{
"id": "recoverability-backupfrequencyinrpo",
"name": "IsBackupFrequencyWithinRPO",
"architecturalPillar": "Reliability",
"recommendation": "Ensure backup frequency aligns with the Recovery Point Objective (RPO)"
}