{"id":6140,"date":"2026-06-18T12:21:20","date_gmt":"2026-06-18T12:21:20","guid":{"rendered":"https:\/\/cloudsave.app\/knowledge-base\/calculate-rto-and-rpo-databases\/"},"modified":"2026-06-18T12:55:40","modified_gmt":"2026-06-18T12:55:40","slug":"izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba","status":"publish","type":"post","link":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/","title":{"rendered":"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA"},"content":{"rendered":"

Za DevOps in\u017eenjere, administratore baza podataka (DBA) i IT sistemske arhitekte, ciljano vreme oporavka (RTO) i ciljana ta\u010dka oporavka (RPO) su vi\u0161e od obi\u010dnih floskula o kontinuitetu poslovanja\u2014oni su stroga in\u017eenjerska ograni\u010denja. Prilikom upravljanja kriti\u010dnim bazama podataka, neuspeh u preciznom izra\u010dunavanju, projektovanju i validaciji ovih metrika mo\u017ee rezultirati katastrofalnim gubitkom podataka i produ\u017eenim prekidima rada.<\/p>\n

U savremenim poslovnim okru\u017eenjima, izra\u010dunavanje RTO i RPO zahteva duboko razumevanje unutra\u0161njosti baze podataka, I\/O skladi\u0161tenja, mre\u017enog protoka i mehanike transakcionih logova. Ovaj vodi\u010d istra\u017euje tehni\u010dke metodologije za izra\u010dunavanje, testiranje i optimizaciju RTO i RPO za produkcione sisteme baza podataka.<\/p>\n

Dekonstrukcija RPO (Ciljana ta\u010dka oporavka) u sistemima baza podataka<\/h2>\n

RPO defini\u0161e maksimalno prihvatljivu koli\u010dinu gubitka podataka merenu u vremenu. Ako je va\u0161 RPO 15 minuta, katastrofa koja se dogodi u 12:00 zna\u010di da morate biti u mogu\u0107nosti da oporavite sve potvr\u0111ene transakcije do najmanje 11:45.<\/p>\n

Za baze podataka, RPO je diktiran va\u0161om strategijom upravljanja transakcionim logovima (WAL u PostgreSQL-u, Redo logovi u Oracle-u, transakcioni logovi u SQL Server-u).<\/p>\n

Mehanika gubitka podataka i generisanja logova<\/h3>\n

Da biste izra\u010dunali ostvariv RPO, prvo morate razumeti stopu generisanja transakcionih logova va\u0161e baze podataka. Ako \u0161aljete logove u repozitorijum rezervnih kopija svakih 15 minuta, ali va\u0161a mre\u017ea ne mo\u017ee da prenese 15 minuta logova unutar tog prozora, va\u0161 stvarni RPO \u0107e se kontinuirano pogor\u0161avati.<\/p>\n

Mo\u017eete uspostaviti osnovnu vrednost stope generisanja logova koriste\u0107i izvorne SQL komande. Na primer, u PostgreSQL-u (verzija 10+), mo\u017eete izmeriti stopu generisanja Write-Ahead Log-a (WAL) tokom odre\u0111enog intervala:<\/p>\n

-- Pokrenite ovo na T=0\nSELECT pg_current_wal_lsn() AS start_lsn;\n\n-- Sa\u010dekajte ta\u010dno 5 minuta (300 sekundi), zatim pokrenite:\nSELECT pg_current_wal_lsn() AS end_lsn,\n       pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(), 'START_LSN_VALUE')) AS wal_generated_size,\n       pg_wal_lsn_diff(pg_current_wal_lsn(), 'START_LSN_VALUE') \/ 300 AS bytes_per_second;\n<\/code><\/pre>\n
Ako ovaj upit otkrije da generi\u0161ete 50 MB\/s WAL podataka tokom vr\u0161nog optere\u0107enja, RPO od 15 minuta zahteva prenos 45 GB log podataka u va\u0161e skladi\u0161te rezervnih kopija. Va\u0161a mre\u017ea i ciljna skladi\u0161ta moraju podr\u017eavati trajne brzine upisa ve\u0107e od 50 MB\/s da bi odr\u017eali ovaj RPO.<\/p>\n
Uticaj sinhrone naspram asihrone replikacije<\/h3>\n
Mnogi administratori baza podataka se oslanjaju na replikaciju visoke dostupnosti (HA) da bi zadovoljili RPO. Me\u0111utim, replikacija nije rezervna kopija. Obrisana tabela (DROP TABLE users;<\/code>) se trenutno replicira.<\/p>\n
Kada koristite replikaciju za oporavak od katastrofe (DR), re\u017eim replikacije direktno uti\u010de na RPO:
\n*   Sinhrona replikacija:<\/strong> Garantuje RPO od nule (RPO=0). Primarna baza podataka ne\u0107e potvrditi transakciju dok standby baza ne potvrdi prijem. Kompromis je pove\u0107ano ka\u0161njenje pri operacijama upisa na primarnoj bazi.
\n*   Asinhrona replikacija:<\/strong> Uvodi ka\u0161njenje replikacije. Va\u0161 RPO je efektivno jednak va\u0161em trenutnom ka\u0161njenju replikacije.<\/p>\n
Da biste pratili ka\u0161njenje asihrone replikacije u PostgreSQL-u, koristite:<\/p>\n
SELECT application_name,\n       client_addr,\n       state,\n       sync_state,\n       pg_wal_lsn_diff(pg_current_wal_lsn(), replay_lsn) AS replication_lag_bytes\nFROM pg_stat_replication;\n<\/code><\/pre>\n
Dekonstrukcija RTO (Ciljanog vremena oporavka) za baze podataka velikih razmera<\/h2>\n
RTO je maksimalno podno\u0161ljivo trajanje prekida rada. Izra\u010dunavanje RTO baze podataka je notorno slo\u017eeno jer to nije jednostavno vreme potrebno za kopiranje datoteka nazad na server.<\/p>\n
Matemati\u010dki model za izra\u010dunavanje RTO<\/h3>\n
Realisti\u010dno izra\u010dunavanje RTO baze podataka mora uzeti u obzir \u010detiri razli\u010dite faze:<\/p>\n
RTO = T(infra) + T(transfer) + T(restore) + T(recovery)<\/strong><\/p>\n
    \n
  1. T(infra) \u2013 Obezbe\u0111ivanje infrastrukture:<\/strong> Vreme za pokretanje zamenskih ra\u010dunarskih resursa i skladi\u0161ta. (Mo\u017ee biti blizu nule sa unapred obezbe\u0111enim DR lokacijama ili Infrastructure-as-Code cevovodima).<\/li>\n
  2. T(transfer) \u2013 Prenos podataka:<\/strong> Vreme za preme\u0161tanje paketa rezervne kopije iz repozitorijuma na server baze podataka.<\/li>\n
  3. T(restore) \u2013 Fizi\u010dki oporavak:<\/strong> Vreme za upis datoteka podataka na ciljni disk.<\/li>\n
  4. T(recovery) \u2013 Oporavak baze podataka od pada:<\/strong> Vreme potrebno da mehanizam baze podataka ponovo pokrene transakcione logove, primeni potvr\u0111ene transakcije i poni\u0161ti nepotvr\u0111ene.<\/li>\n<\/ol>\n
    Izra\u010dunavanje vremena prenosa i oporavka<\/h3>\n
    Da biste izra\u010dunali T(transfer)<\/code> i T(restore)<\/code>, morate uspostaviti osnovnu vrednost mre\u017enog propusnog opsega i IOPS\/propusne mo\u0107i diska. Ne oslanjajte se na teoretske maksimume; testirajte svoju stvarnu infrastrukturu.<\/p>\n
    Koristite iperf3<\/code> za testiranje mre\u017enog protoka izme\u0111u va\u0161eg repozitorijuma rezervnih kopija i servera baze podataka:<\/p>\n
    # Na repozitorijumu rezervnih kopija (server)\niperf3 -s\n\n# Na serveru baze podataka (klijent)\niperf3 -c <backup_repo_ip> -t 60 -P 4\n<\/code><\/pre>\n
    Koristite fio<\/code> za testiranje performansi sekvencijalnog upisa va\u0161ih skladi\u0161nih volumena baze podataka, simuliraju\u0107i operaciju oporavka baze podataka:<\/p>\n
    fio --name=restore_sim --ioengine=libaio --rw=write --bs=1M --size=10G --numjobs=4 --iodepth=32 --direct=1 --filename=\/var\/lib\/postgresql\/data\/testfile\n<\/code><\/pre>\n
    Ako va\u0161a baza podataka ima 5 TB, a va\u0161i fio<\/code> testovi pokazuju maksimalnu trajnu brzinu upisa od 500 MB\/s, va\u0161 apsolutni minimum T(restore)<\/code> je pribli\u017eno 2,8 sati. Ako va\u0161 poslovni SLA zahteva RTO od 1 sat, tradicionalni striming oporavci ne\u0107e uspeti. Morate preusmeriti svoju arhitekturu na snimke na nivou skladi\u0161ta (snapshots) ili replikaciju na nivou blokova.<\/p>\n
    Skrivena zamka: T(recovery)<\/h3>\n
    Naj\u010de\u0161\u0107e potcenjena varijabla je T(recovery)<\/code>. Ako vratite nedeljnu punu rezervnu kopiju i treba da primenite 6 dana transakcionih logova da biste dostigli svoj RPO, mehanizam baze podataka mora sekvencijalno da ponovi svaku transakciju.<\/p>\n
    Ponovno pokretanje 500 GB transakcionih logova mo\u017ee potrajati satima, ozbiljno ograni\u010deno performansama CPU-a sa jednom niti i IOPS-om skladi\u0161ta. Da biste minimizirali T(recovery)<\/code>, pove\u0107ajte u\u010destalost va\u0161ih punih ili diferencijalnih rezervnih kopija.<\/p>\n
    Premo\u0161\u0107avanje jaza: Prakti\u010dni koraci za validaciju RTO i RPO<\/h2>\n
    Izra\u010dunavanje teoretskog RTO i RPO je samo prvi korak. Okru\u017eenja od kriti\u010dnog zna\u010daja zahtevaju kontinuiranu validaciju.<\/p>\n
    Korak 1: Implementirajte kontinuirano arhiviranje<\/h3>\n
    Da biste postigli RPO kra\u0107i od minuta bez gubitka performansi sinhronizovane replikacije, implementirajte kontinuirano arhiviranje logova. Umesto \u010dekanja da se datoteka loga popuni (\u0161to mo\u017ee potrajati satima tokom perioda slabog saobra\u0107aja), forsirajte prebacivanje logova u redovnim intervalima.<\/p>\n
    U SQL Server-u mo\u017eete automatizovati \u010deste rezervne kopije transakcionih logova:<\/p>\n
    BACKUP LOG [MissionCriticalDB] \nTO DISK = N'\\BackupRepoSQLMissionCriticalDB_Log.trn' \nWITH NOFORMAT, NOINIT, \nNAME = N'MissionCriticalDB-Transaction Log Backup', \nSKIP, NOREWIND, NOUNLOAD, COMPRESSION, STATS = 10;\n<\/code><\/pre>\n
    Najbolja praksa:<\/em> Zaka\u017eite ovaj posao da se pokre\u0107e svakih 1-5 minuta u zavisnosti od va\u0161ih RPO zahteva.<\/p>\n
    Korak 2: Automatizujte testiranje oporavka<\/h3>\n
    Netestirana rezervna kopija je samo teoretski koncept. Da biste garantovali svoj izra\u010dunati RTO, morate izvr\u0161iti automatizovano testiranje oporavka.<\/p>\n
    Enterprise platforme za rezervne kopije kao \u0161to je CloudSave pojednostavljuju ovo pru\u017eanjem automatizovanog, izolovanog testiranja oporavka. CloudSave mo\u017ee automatski pokrenuti sandbox okru\u017eenje, montirati najnoviju rezervnu kopiju, izvr\u0161iti potpuni oporavak baze podataka i pokrenuti prilago\u0111ene skripte za validaciju (npr. DBCC CHECKDB<\/code> za SQL Server) kako bi izmerio ta\u010dan RTO i osigurao integritet podataka. Ovo pretvara RTO iz izra\u010dunate pretpostavke u dokazanu, izve\u0161tajnu metriku.<\/p>\n
    Korak 3: Pratite i upozoravajte na kr\u0161enje SLA<\/h3>\n
    Va\u0161 monitoring sistem (Prometheus, Datadog, Zabbix) treba aktivno da prati metrike koje ugro\u017eavaju va\u0161e RTO\/RPO SLA ugovore. Pravila upozoravanja treba konfigurisati za:
    \n*   Neuspesi poslova rezervnih kopija:<\/strong> Neposredna pretnja po RPO.
    \n*   Ka\u0161njenje slanja logova:<\/strong> Ako prenos logova traje du\u017ee od intervala generisanja.
    \n*   Ograni\u010davanje IOPS skladi\u0161ta:<\/strong> Provajderi u oblaku (kao \u0161to je AWS EBS) ograni\u010davaju IOPS ako se potro\u0161e burst krediti, \u0161to \u0107e tiho uni\u0161titi va\u0161 RTO tokom stvarne hitne situacije.<\/p>\n
    Optimizacija arhitekture rezervnih kopija baza podataka radi ispunjavanja strogih SLA<\/h2>\n
    Kada matemati\u010dki prora\u010duni otkriju da va\u0161a trenutna arhitektura ne mo\u017ee ispuniti poslovne SLA ugovore, morate optimizovati svoju strategiju rezervnih kopija.<\/p>\n
    1. Iskoristite inkrementalne rezervne kopije na nivou blokova<\/h3>\n
    Tradicionalni dumpovi baza podataka (logi\u010dke rezervne kopije kao \u0161to su pg_dump<\/code> ili mysqldump<\/code>) su prespori za kriti\u010dne RTO zahteve. Koristite fizi\u010dke rezervne kopije na nivou blokova. Inkrementalne rezervne kopije na nivou blokova kopiraju samo one blokove diska koji su promenjeni od poslednje rezervne kopije, drasti\u010dno smanjuju\u0107i T(transfer)<\/code> i mre\u017ene tro\u0161kove.<\/p>\n
    2. Koristite snimke skladi\u0161ta (Storage Snapshots)<\/h3>\n
    Za baze podataka od vi\u0161e terabajta koje zahtevaju RTO kra\u0107i od 15 minuta, tradicionalno kopiranje datoteka je fizi\u010dki nemogu\u0107e preko standardnih mre\u017ea. Integracija sa SAN ili izvornim snimcima skladi\u0161ta u oblaku (npr. AWS EBS Snapshots, Pure Storage) omogu\u0107ava gotovo trenutni T(restore)<\/code>. Mehanizam baze podataka tada treba samo da izvr\u0161i oporavak od pada na snimku.<\/p>\n
    3. Implementirajte paralelizaciju<\/h3>\n
    Osigurajte da va\u0161i alati za rezervne kopije i oporavak koriste vi\u0161e niti (multi-threading). Prilikom oporavka PostgreSQL baze podataka koriste\u0107i pgbackrest<\/code> ili SQL Server baze podataka, eksplicitno defini\u0161ite paralelne radne niti da biste zasitili raspolo\u017eivi mre\u017eni i disk propusni opseg.<\/p>\n
    # Primer paralelnog oporavka u pgBackRest\npgbackrest --stanza=prod_db --process-max=8 restore\n<\/code><\/pre>\n
    Zaklju\u010dak<\/h2>\n
    Izra\u010dunavanje RTO i RPO za kriti\u010dne baze podataka je rigorozna ve\u017eba sistemskog in\u017eenjeringa. Zahteva od administratora baza podataka da prevazi\u0111u podrazumevane konfiguracije rezervnih kopija i matemati\u010dki modeliraju svoj I\/O skladi\u0161ta, mre\u017eni kapacitet i mehaniku oporavka baze podataka.<\/p>\n
    Uspostavljanjem osnovnih vrednosti stope generisanja logova, razumevanjem razli\u010ditih faza oporavka baze podataka i implementacijom automatizovanog testiranja kroz robusne platforme kao \u0161to je CloudSave, IT timovi mogu sa sigurno\u0161\u0107u garantovati svoje SLA ugovore o oporavku od katastrofe. Zapamtite: u domenu administracije baza podataka, nada nije strategija, a netestirane rezervne kopije su odgovornost.<\/p>\n
    \n
    Saznajte kako DevOps in\u017eenjeri i administratori baza podataka mogu precizno izra\u010dunati, testirati i optimizovati RTO i RPO za kriti\u010dne baze podataka koriste\u0107i naprednu mehaniku oporavka, CLI alate i automatizovano testiranje.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"
    **<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Calculate RTO & RPO for Mission-Critical Databases","rank_math_description":"**","rank_math_focus_keyword":"calculate RTO and RPO","footnotes":""},"categories":[1673],"tags":[4454,664,3819,3820,4455,4456],"class_list":["post-6140","post","type-post","status-publish","format-standard","hentry","category-disaster-recovery","tag-business-continuity","tag-data-loss-prevention","tag-database-recovery","tag-dba-guide","tag-mission-critical-databases","tag-rto-and-rpo"],"yoast_head":"\nCalculate RTO & RPO for Mission-Critical Databases<\/title>\n<meta name=\"description\" content=\"**\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/\" \/>\n<meta property=\"og:locale\" content=\"sr_RS\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA\" \/>\n<meta property=\"og:description\" content=\"**\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/\" \/>\n<meta property=\"og:site_name\" content=\"CloudSave\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-18T12:21:20+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-18T12:55:40+00:00\" \/>\n<meta name=\"author\" content=\"shervinrv\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041d\u0430\u043f\u0438\u0441\u0430\u043d\u043e \u043e\u0434\" \/>\n\t<meta name=\"twitter:data1\" content=\"shervinrv\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u041f\u0440\u043e\u0446\u0435\u045a\u0435\u043d\u043e \u0432\u0440\u0435\u043c\u0435 \u0447\u0438\u0442\u0430\u045a\u0430\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 \u043c\u0438\u043d\u0443\u0442\u0430\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/\"},\"author\":{\"name\":\"shervinrv\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"headline\":\"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA\",\"datePublished\":\"2026-06-18T12:21:20+00:00\",\"dateModified\":\"2026-06-18T12:55:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/\"},\"wordCount\":1431,\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"keywords\":[\"Business Continuity\",\"data loss prevention\",\"database recovery\",\"DBA guide\",\"Mission-Critical Databases\",\"RTO and RPO\"],\"articleSection\":[\"Disaster Recovery\"],\"inLanguage\":\"sr-RS\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/\",\"name\":\"Calculate RTO & RPO for Mission-Critical Databases\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/#website\"},\"datePublished\":\"2026-06-18T12:21:20+00:00\",\"dateModified\":\"2026-06-18T12:55:40+00:00\",\"description\":\"**\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/#breadcrumb\"},\"inLanguage\":\"sr-RS\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/#website\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/\",\"name\":\"CloudSave\",\"description\":\"CloudSave\",\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"sr-RS\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\",\"name\":\"shervinrv\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"sr-RS\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"contentUrl\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"width\":859,\"height\":150,\"caption\":\"shervinrv\"},\"logo\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\"},\"sameAs\":[\"http:\\\/\\\/cloudsave.app\"],\"url\":\"https:\\\/\\\/cloudsave.app\\\/sr\\\/knowledge-base\\\/author\\\/shervinrv\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Calculate RTO & RPO for Mission-Critical Databases","description":"**","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/","og_locale":"sr_RS","og_type":"article","og_title":"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA","og_description":"**","og_url":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/","og_site_name":"CloudSave","article_published_time":"2026-06-18T12:21:20+00:00","article_modified_time":"2026-06-18T12:55:40+00:00","author":"shervinrv","twitter_card":"summary_large_image","twitter_misc":{"\u041d\u0430\u043f\u0438\u0441\u0430\u043d\u043e \u043e\u0434":"shervinrv","\u041f\u0440\u043e\u0446\u0435\u045a\u0435\u043d\u043e \u0432\u0440\u0435\u043c\u0435 \u0447\u0438\u0442\u0430\u045a\u0430":"8 \u043c\u0438\u043d\u0443\u0442\u0430"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/#article","isPartOf":{"@id":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/"},"author":{"name":"shervinrv","@id":"https:\/\/cloudsave.app\/sr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"headline":"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA","datePublished":"2026-06-18T12:21:20+00:00","dateModified":"2026-06-18T12:55:40+00:00","mainEntityOfPage":{"@id":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/"},"wordCount":1431,"publisher":{"@id":"https:\/\/cloudsave.app\/sr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"keywords":["Business Continuity","data loss prevention","database recovery","DBA guide","Mission-Critical Databases","RTO and RPO"],"articleSection":["Disaster Recovery"],"inLanguage":"sr-RS"},{"@type":"WebPage","@id":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/","url":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/","name":"Calculate RTO & RPO for Mission-Critical Databases","isPartOf":{"@id":"https:\/\/cloudsave.app\/sr\/#website"},"datePublished":"2026-06-18T12:21:20+00:00","dateModified":"2026-06-18T12:55:40+00:00","description":"**","breadcrumb":{"@id":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/#breadcrumb"},"inLanguage":"sr-RS","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cloudsave.app\/sr\/knowledge-base\/izra%c4%8dunavanje-rto-i-rpo-za-baze-podataka-od-kriti%c4%8dne-va%c5%benosti-vodi%c4%8d-za-dba\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudsave.app\/sr\/"},{"@type":"ListItem","position":2,"name":"Izra\u010dunavanje RTO i RPO za baze podataka od kriti\u010dne va\u017enosti: Vodi\u010d za DBA"}]},{"@type":"WebSite","@id":"https:\/\/cloudsave.app\/sr\/#website","url":"https:\/\/cloudsave.app\/sr\/","name":"CloudSave","description":"CloudSave","publisher":{"@id":"https:\/\/cloudsave.app\/sr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudsave.app\/sr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"sr-RS"},{"@type":["Person","Organization"],"@id":"https:\/\/cloudsave.app\/sr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d","name":"shervinrv","image":{"@type":"ImageObject","inLanguage":"sr-RS","@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","url":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","contentUrl":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","width":859,"height":150,"caption":"shervinrv"},"logo":{"@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png"},"sameAs":["http:\/\/cloudsave.app"],"url":"https:\/\/cloudsave.app\/sr\/knowledge-base\/author\/shervinrv\/"}]}},"_links":{"self":[{"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/posts\/6140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/comments?post=6140"}],"version-history":[{"count":1,"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/posts\/6140\/revisions"}],"predecessor-version":[{"id":6205,"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/posts\/6140\/revisions\/6205"}],"wp:attachment":[{"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/media?parent=6140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/categories?post=6140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudsave.app\/sr\/wp-json\/wp\/v2\/tags?post=6140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}