Actually Measuring RPO and RTO Targets in Disaster Recovery
A green nightly backup job does not mean your RPO and RTO targets are actually met. Only a real, repeated restore drill produces the true number. Here is how to build one, and where it quietly lies to you.
What RPO and RTO actually are, and why they stay on paper
Every disaster recovery plan centers on two numbers. RPO (Recovery Point Objective) defines how much data loss you can tolerate, and RTO (Recovery Time Objective) defines how long you have to bring a system back up. Setting these numbers is easy; writing "RPO 15 minutes, RTO 4 hours" in a meeting takes an hour. Knowing whether those numbers actually hold is the hard part. Most teams never measure it. Because the backup job turns green every night, they assume the target is being met. That assumption is where the most expensive surprise in a real outage comes from.
Taking a backup is not the same as meeting your RPO
A backup tool completing successfully every night proves none of three separate claims: that the data captured is consistent, that it can actually be restored, and that the restore finishes within the target time. Take a database dump captured while the filesystem is mid write: the file size looks correct, but the content can be corrupt. The backup tool reports zero errors, and the first query after restore fails. The only way to catch this is to occasionally run a real restore. A log line that says "success" is not sufficient evidence.
The second problem shows up in retention and pruning logic. Most backup tools delete old snapshots according to a policy. That deletion step can silently fail because of a stale lock file or an interrupted prior run, while the tool still reports "backup complete", because what it measured was the backup step, not the pruning step. The result: the repository quietly grows, nobody notices, until the disk fills up or a restore is actually needed one day. This is why backup monitoring should not only ask "did the backup job succeed", but also "is repository size on the expected curve" and "what is the age of the oldest valid snapshot".
The variables people skip when measuring RTO
Measuring RTO as "how long does the restore command take" is misleading. Real RTO is the sum of getting access and authorization (who has which key, which console, and will that be remembered during a crisis), transferring the data (bounded by network bandwidth, scales linearly with data size), restoring it, starting services in the correct order, and waiting for dependencies such as DNS, certificates, or external services to become ready.
The most common mistake here is running the restore test against the small dataset from initial setup and recording that time as the RTO. If the data grows tenfold over six months, restore time grows proportionally, but because nobody repeats the drill, the number on paper never changes. This measurement is not a one-time certificate; it is a number that needs to be refreshed alongside data growth.
The second skipped variable is the human factor. Which document to consult during a crisis, which system that document lives on, and whether that system is even reachable during the outage, are usually never tested. If the runbook itself lives somewhere that becomes unreachable in the disaster scenario, such as a wiki hosted on the system that just went down, it does not matter how fast the restore steps themselves run.
Three testing approaches and where each one fits
Tabletop exercise: the team gets together, talks through a "server X is down" scenario, and walks through who does what. It is cheap and surfaces communication gaps, for instance nobody knowing where the backup keys are kept, but it does not measure real time. It is a fine starting point for small teams and should never be used on its own as proof of RTO.
Automated restore drill: at regular intervals, weekly or monthly, the latest backup is actually restored into an isolated environment, put through a health check, and the elapsed time is recorded. This produces a real RPO and RTO number because there is little room for human intervention or assumption. Cost is moderate: it requires an isolated environment and an automation script, but once built, upkeep is low. For most teams this is the right balance. It matters that the hardware and network profile of the restore environment is not wildly different from production; a test over a fast internal network in the same data center hides the transfer time a real disaster, restoring from a different region, would actually take.
Live failover test (chaos engineering, game day): actually shifting some or all of production traffic to the backup system and creating a real outage to test against. This gives the most realistic number because it includes factors no drill reproduces, such as network behavior, DNS TTL, and cache warm-up time. It is also the highest risk and highest cost method, and should not be attempted without mature monitoring and rollback infrastructure already in place.
Practical recommendation: start with an automated restore drill for small and medium systems. It gives you a real number without production risk. As criticality increases, for payment systems or single-point databases, increase frequency and eventually move toward live failover testing.
Steps you can apply
Do not set one RPO/RTO target for the whole organization. Define tiers based on data criticality: user data and financial records might warrant an RPO of 15 minutes, while logs and cache data might tolerate 24 hours. Set a separate test cadence per tier; weekly for high criticality, monthly or quarterly can be enough for low criticality.
Collect restore duration as a metric, not just backup job duration. Record the time from the start of the restore to the moment the service passes its health check, and track the trend over time. As data grows this number will grow too; seeing that ahead of time lets you adjust capacity or backup strategy, for example incremental backups or parallel restores, accordingly.
Verify data integrity after restore. Check not just that the command exited with zero errors, but that the restored data has the expected record count, passes a checksum, or clears an application level smoke test. "The restore command returned 0" and "the application is actually running on correct data" are two very different claims.
Test key management separately for encrypted backups. A backup can succeed while the decryption key is lost during rotation, meaning the real RPO is infinite, discovered only during an actual disaster. Regularly test whether the key still actually opens the backup, and make sure the key itself is backed up independently.
Keep the runbook reachable under the outage scenario, and actually follow that document during the drill rather than relying on the memory of whoever wrote it. A drill run from memory hides exactly the places where the document is incomplete or out of date.
When this level of investment is not worth it
Not every system deserves a weekly restore drill. For low criticality systems that are easy to reproduce, such as a static cache or a log archive, a simple and infrequent check is enough. Keep test frequency and depth proportional to that system's actual outage cost; otherwise the team spends most of its time testing low risk systems while the drill for the truly critical one gets neglected. RPO and RTO targets are not a checkbox, they are a contract for how many minutes of data loss you have actually accounted for in a real outage. Test the contract before you sign it.
[OK] 30 records · 9 featured · 1 retainer · 20 standard
/02 services
services.tree
> note
· Prices are in USD. Volume discounts of 7% for 6-12 day projects and 14% for 13+ day projects apply. Programs of 100+ person-days are priced individually. Prices are negotiable based on scope, urgency and long-term collaboration.
> ls ~/products/ --open-source
[OK] 2 entries · 1 live · 1 pre-release
/03 products
products.list
liveopen source · mit/prod/01
filex
the self-hosted file manager that embeds anywhere
single go binary · vue/react/web-component embed · 5 storage drivers · realtime collab · rbac · native multi-tenancy · mcp server for ai agents
We build infrastructure, automate everything, and keep systems running.
BRF Tech is a Bursa-based DevSecOps and software consulting firm. We operate across 30 service areas, from Kubernetes cluster management to serverless platform setup, CI/CD pipeline design to AI agent development.
What we do is simple: we set up your systems, automate them, and make sure they won't wake you up at 3 AM. We codify your infrastructure with Terraform, move your deployments to GitOps with ArgoCD, and monitor everything with Prometheus. If something breaks — we intervene before it does.
We're against vendor lock-in. We work with open-source tools, self-hosted solutions, and industry-standard technologies. We build your own serverless platform on Knative, isolate with Kata Containers, manage your secrets with Vault. Every project is delivered with clear scope, clear timeline, clear pricing.
DevSecOps & CI/CD
Kubernetes & Serverless
Infrastructure as Code
AI & Agent (MCP/ACP)
Security & Zero Trust
Full-Stack Development
Self-Hosted Solutions
> grep -i question ~/faq.md
[OK] 3 entries · click to expand
[?]What services are included in BRF Tech's DevOps solutions?▾
We offer CI/CD pipeline setup, Kubernetes cluster management, container migration, infrastructure automation with Terraform, monitoring & alerting, in-house technology installations and DevOps consulting services.
[?]What are your software development services?▾
We offer MVP development, existing software performance optimization, backend API development (Node.js, Go, Python) and full-stack application development. Every project is delivered with minimal technical debt.
[?]Which DevOps tools do you work with?▾
From Kubernetes and Docker to Talos Linux, from Terraform and OpenTofu to Ansible, and across Jenkins, GitLab CI/CD, GitHub Actions, ArgoCD, Flux, Helm and Rancher, we work with industry-standard tooling. For observability and error tracking we use Prometheus, Grafana, Loki, Tempo, OpenTelemetry and GlitchTip; for networking, Cilium and Envoy; for test automation, Playwright, Cypress, k6, Locust, Testcontainers and Trivy. We determine the most suitable toolset together, based on your project’s needs.
Automated build, test and deployment pipelines with GitHub Actions, GitLab CI/CD.
Automated build, test and deploy pipeline setup for existing or new repositories. GitHub Actions, GitLab CI/CD or preferred tool is used. Separate workflows are defined for staging + production environments.
Container architecture migration, cluster setup and orchestration.
Production-ready Kubernetes cluster setup on bare-metal or cloud. Includes Helm charts, Ingress, TLS certificate management, namespace isolation and RBAC.
Cozystack is an open-source cloud platform built on Kubernetes and the VMware alternative we recommend most. Virtual machines run on KubeVirt, while managed PostgreSQL, MySQL, Redis and Kafka services and dedicated tenant Kubernetes clusters are provisioned from the same dashboard and API. Includes installation on your own bare-metal servers on Talos Linux, replicated storage with LINSTOR/DRBD, network isolation with Kube-OVN, tenant and quota structure, monitoring, backup and a disaster recovery plan. After deployment we also handle upgrades, operations and support; since the platform is open source, there are no license fees and no vendor lock-in.
Packages
Virtual machine support on an existing Kubernetes cluster with KubeVirt
$2,800
4–6 person-day
Pilot setup (3 nodes, virtual machines + managed database)
$3,500
5–8 person-day
Production setup (HA + replicated storage + monitoring + backup)
$6,500
10–16 person-day
Multi-tenant private cloud (tenants, quotas, managed service catalog)
Planned, low-downtime migration of vSphere/ESXi environments to Cozystack, OpenStack or VHI.
A planned move to a VMware alternative for environments whose costs rose after Broadcom moved VMware licensing to subscription bundles, or whose renewal is coming up. We start with an inventory of your vSphere/ESXi estate (virtual machines, disks, networks, dependencies), then compare today's license cost with the total cost of the target platform. In most environments the target is Cozystack; OpenStack fits large-scale IaaS needs and Virtuozzo Hybrid Infrastructure fits storage-heavy service providers. A pilot runs on non-critical virtual machines, disks are converted with tools such as virt-v2v and Forklift, and the migration proceeds in waves within maintenance windows, with a rollback plan for every step.
Packages
Inventory + cost comparison + migration plan
$2,400
3–5 person-day
Pilot migration (up to 10 virtual machines)
$3,500
5–8 person-day
Phased migration (up to 100 virtual machines)
$9,750
15–22 person-day
Full data center migration (network + storage + backup)
OpenStack deployment, Neutron networking, Ceph/Cinder storage, upgrades and operations.
OpenStack deployment and operations in your own data center. A containerized, highly available control plane with Kolla-Ansible; Nova (compute), Keystone (identity), Glance (images) and Horizon (dashboard). On the network side, Neutron with OVN, VLAN/VXLAN, provider and tenant networks, floating IPs and the Octavia load balancer; on the storage side, Cinder block storage on Ceph RBD and optional S3-compatible object storage. For existing deployments: health checks, planned upgrades between releases, monitoring and alerting setup, and a backup strategy.
Packages
Health check + improvement report (existing deployment)
$2,400
3–5 person-day
Lab / PoC setup (single region, 3 nodes)
$3,500
5–8 person-day
Release upgrade (existing deployment)
$3,900
6–10 person-day
Production setup (HA control plane + Ceph + Neutron/OVN)
Hyperconverged infrastructure: multi-tenant cloud plus block and S3-compatible storage for service providers.
Hyperconverged infrastructure with Virtuozzo Hybrid Infrastructure, where compute, storage and networking run on the same servers. Block, S3-compatible object and NFS storage on software-defined storage, plus backup storage (Backup Gateway) for backup products such as Acronis. For service providers: a multi-tenant cloud with domains and projects, quotas, a self-service panel and an OpenStack-compatible API. Includes hardware sizing, network design, cluster deployment and expansion, version upgrades and operations support.
Packages
Pre-deployment assessment + hardware sizing
$2,400
3–4 person-day
Version upgrade / cluster expansion
$2,800
4–6 person-day
Hyperconverged cluster setup (storage + compute)
$3,900
6–10 person-day
Service provider setup (multi-tenant cloud + S3 + backup storage)
Migration of existing applications to container architecture.
Migration of existing applications to container architecture. Docker image design, Compose configuration and conversion to Kubernetes manifests. Kata Containers / gVisor can be included for advanced isolation.
Health check of your current environment, capacity planning, platform selection and a roadmap.
An independent assessment of your current virtualization environment (VMware vSphere, OpenStack, VHI or other KVM-based platforms). The health check covers cluster configuration, resource overcommit, storage latency, forgotten snapshots, backup and patch status. Capacity planning measures CPU, memory and storage growth to work out the hardware you will need next. Platform selection decides which workload should run where: Cozystack for teams running containers and virtual machines side by side, OpenStack for large-scale IaaS, VHI for storage-heavy service providers; staying on the current platform is also an option for some workloads. The deliverable is a written report with a cost comparison and a prioritized roadmap.
In-house tools like GitLab, Nextcloud, VPN, mail server.
Installation of tools like GitLab, Mattermost, Nextcloud, mail server, VPN, internal monitoring on company servers. Deployed on Docker Compose or Kubernetes.
DB + cache + code bottleneck identification and resolution.
Profiling of existing application, identification and resolution of bottlenecks. DB query optimization, caching layer (Redis), service-level improvements.
MCP/ACP agents, RAG pipelines, multi-agent orchestration, model serving.
LLM integration (OpenAI, Claude, Gemini, local models), tool-augmented AI agents with MCP (Model Context Protocol) and ACP (Agent Communication Protocol). RAG pipeline, multi-agent orchestration, model serving (vLLM/Ollama). AI layer for existing business processes.
Event-driven data pipeline with Apache Kafka, RabbitMQ, NATS. ETL/ELT orchestration with Apache Airflow, real-time data streaming, CDC (Change Data Capture). Data lake/warehouse design, schema registry, dead letter queue management.
Packages
Kafka/RabbitMQ setup + basic producer/consumer
$3,500
5–7 person-day
ETL pipeline (Airflow + source → warehouse)
$5,200
8–12 person-day
Full event-driven architecture (CDC + streaming + DLQ)
Hands-on technical training for your teams. Docker & container fundamentals, Kubernetes operations, Terraform IaC, CI/CD best practices, AI/LLM integration workshops. Practical exercises in live lab environments, content customized by skill level.
E2E test automation with Playwright, Cypress, load testing with k6/Gatling. Pre-deploy quality gate integrated into CI/CD pipeline, test coverage reporting, visual regression testing. Reduce test writing time by up to 60% with AI-assisted test generation.
Your Collected Personal Data, Collection Method and Legal Basis
Any information that identifies or makes you identifiable is considered "personal data." When you visit our website or use our services, contact information such as your name, surname, email address, phone number, as well as your IP address and browser cookie data may be collected through automatic or semi-automatic means. This data is processed based on the legal grounds specified in Article 5 of the Personal Data Protection Law No. 6698: "being directly related to the establishment or performance of a contract" and "being mandatory for the legitimate interests of the data controller, provided that it does not harm the fundamental rights and freedoms of the data subject."
Purpose of Processing Your Personal Data
Your collected personal data is processed for the purposes of providing and improving our services, fulfilling customer requests, meeting legal obligations, conducting information security processes and managing communication activities. Your data is processed in a limited and proportionate manner for the stated purposes; when the purpose ceases to exist, data is deleted, destroyed or anonymized.
To Whom and For What Purposes Collected Personal Data May Be Transferred
Your personal data may be transferred to public institutions and organizations as required by legal regulations, to our business partners and technical infrastructure providers for the purpose of delivering services, and to lawyers and consultants in legal disputes. Transfers are carried out in accordance with Articles 8 and 9 of the Law, with necessary technical and administrative measures in place.
Your Rights as a Data Subject
In accordance with Article 11 of Law No. 6698, you have the right to: learn whether your personal data is being processed; request information if it has been processed; learn the purpose of processing and whether it is used in accordance with its purpose; know the third parties to whom it is transferred domestically or abroad; request correction if it has been processed incompletely or incorrectly; request deletion or destruction within the framework of conditions set out in Article 7 of the Law; request that the operations carried out be notified to third parties to whom data has been transferred; object to any adverse result arising from the analysis of data exclusively through automated systems; and claim compensation for damages in case of unlawful processing. You may contact us through the communication channels on our website to exercise these rights.
Terms & Conditions
Terms & Conditions
1. Service Scope and Changes
BRF Tech conducts its software development, DevOps consulting, infrastructure setup and technical support services within the framework of these terms and conditions. The scope of service is determined separately for each project and finalized through mutual agreement. BRF Tech reserves the right to update the scope, pricing and technical details of its services, provided that prior notice is given.
2. Privacy Policy
Personal data collected within the scope of our services is processed in accordance with our Privacy Policy. For detailed information, please review our Privacy Policy page.
3. Service Usage and Responsibilities
Clients agree to use the provided services solely within legal and ethical boundaries. BRF Tech reserves the right to suspend or terminate services in the event of misuse, violation of third-party rights, or use for illegal activities. The client is responsible for the accuracy and currency of the information provided within the project scope.
4. Payment Terms
Payment terms are determined on a project basis and finalized through mutual agreement at the start of the project. Unless otherwise specified, invoices are payable within 15 days of project delivery. A monthly late payment interest of 2% may apply to overdue payments.
5. Cancellation and Refund Policy
Cancellation requests must be submitted in writing at least 7 days before the service start date. For projects already in progress, billing is based on the proportion of completed work. No refunds are issued for software and infrastructure components specifically developed within the project scope.