Last updated: · Prepared by DataKobi Engineering Team
Disaster Recovery as a Service
DRaaS (Disaster Recovery as a Service) means continuously replicating your production systems to a second data center and running them from there within minutes when a disaster strikes. In Turkish regulation it is also referred to as a "Disaster Recovery Center (FKM)" service.
Earthquake, fire, ransomware or a simple human error: for scenarios that threaten business continuity, the only real insurance is a geographically separate DR environment that is tested regularly. DataKobi DRaaS continuously replicates your production environment to a second location in Ankara or Istanbul; the distance between the two facilities is enough that a single regional disaster cannot affect both.
What sets us apart is test discipline: twice a year we run a real failover test in an isolated network that does not affect production, and we document with an executive report that the RTO/RPO targets are met in practice. For regulated organizations (BDDK (Banking Regulation and Supervision Agency), SPK (Capital Markets Board), healthcare), we prepare the audit file ourselves.
Key features
RPO down to 15 minutes
With continuous replication, the data loss window is limited to minutes.
One-click failover
A predefined runbook brings up the entire environment in sequence at the second location.
Real DR tests
2 DR tests a year in an isolated network without affecting production, with an executive report.
Regulatory file
Documentation ready for BDDK, KVKK (Türkiye's personal data protection law) and ISO 22301 audits.
How should I set my RTO and RPO targets?
RTO (Recovery Time Objective) is the time it takes for a system to be back up and running; RPO (Recovery Point Objective) is the acceptable window of data loss. The right method is to tier every application through a business impact analysis (BIA): for money-movement and sales systems, an RTO of 1-4 hours and an RPO of 15 minutes are typical, while reporting and archive systems are protected more economically with an RTO of 24-72 hours. Protecting every system to the tightest target raises the budget 3-4 times; a tiered approach usually provides the same protection at half the cost. During the discovery phase, we do this tiering together with you, based on your application inventory.
How is a DR test actually carried out, and is production affected?
Production is not affected. In a test, the replica copies are brought up in a "bubble network" that is completely isolated from the production network; application owners log into the systems through test IP addresses and verify their business scenarios. The actual measured values (startup sequence, total duration, data freshness) are compared against the targets and attached to the report. Industry research shows that nearly half of DR plans that are never tested fail in the first real disaster; that is why two tests a year are standard in our contract, not an option.
Technical Specifications
- Replication: VMware vSphere Replication / Veeam CDP / Zerto options
- Locations: Ankara ESB-DC1 ↔ Istanbul IST-DC2
- RTO: Scenarios ranging from 4 hours down to minutes
- Network: Automatic DNS/IP redirection after failover
- Testing: 2 planned DR tests per year included
Frequently Asked Questions
Is DR the same as backup?
What do RTO and RPO mean?
Will I pay full price for the DR environment all the time?
A 30-minute discovery call with your architect
We will listen to your needs and outline the right architecture and a clear pricing framework in the same call. The first consultation is free.