{"id":4998,"date":"2026-02-11T22:40:03","date_gmt":"2026-02-11T19:40:03","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/odoo-ve-erpnext-icin-vps-hosting-mimarisi-cpu-ram-postgresql-ve-yedekleme\/"},"modified":"2026-02-11T22:40:03","modified_gmt":"2026-02-11T19:40:03","slug":"odoo-ve-erpnext-icin-vps-hosting-mimarisi-cpu-ram-postgresql-ve-yedekleme","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/odoo-ve-erpnext-icin-vps-hosting-mimarisi-cpu-ram-postgresql-ve-yedekleme\/","title":{"rendered":"Odoo ve ERPNext \u0130\u00e7in VPS Hosting Mimarisi: CPU, RAM, PostgreSQL ve Yedekleme"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Odoo_ve_ERPNext_Icin_Dogru_VPS_Mimarisi_Neden_Bu_Kadar_Onemli\"><span class=\"toc_number toc_depth_1\">1<\/span> Odoo ve ERPNext \u0130\u00e7in Do\u011fru VPS Mimarisi Neden Bu Kadar \u00d6nemli?<\/a><\/li><li><a href=\"#Odoo_ve_ERPNext_Is_Yukunu_Anlamak_Asil_Kaynak_Tuketen_Ne\"><span class=\"toc_number toc_depth_1\">2<\/span> Odoo ve ERPNext \u0130\u015f Y\u00fck\u00fcn\u00fc Anlamak: As\u0131l Kaynak T\u00fcketen Ne?<\/a><\/li><li><a href=\"#CPU_ve_RAM_Boyutlandirma_Farkli_Olcekler_Icin_Ornek_Senaryolar\"><span class=\"toc_number toc_depth_1\">3<\/span> CPU ve RAM Boyutland\u0131rma: Farkl\u0131 \u00d6l\u00e7ekler \u0130\u00e7in \u00d6rnek Senaryolar<\/a><ul><li><a href=\"#Kucuk_Ekipler_520_Kullanici_Tek_VPS_Hepsi_Bir_Arada_Mimari\"><span class=\"toc_number toc_depth_2\">3.1<\/span> K\u00fc\u00e7\u00fck Ekipler (5\u201320 Kullan\u0131c\u0131): Tek VPS, Hepsi Bir Arada Mimari<\/a><\/li><li><a href=\"#Orta_Olcekli_Kurulumlar_2080_Kullanici_Uygulama_ve_Veritabanini_Ayirmak\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Orta \u00d6l\u00e7ekli Kurulumlar (20\u201380 Kullan\u0131c\u0131): Uygulama ve Veritaban\u0131n\u0131 Ay\u0131rmak<\/a><\/li><li><a href=\"#Buyuk_Kurulumlar_ve_SaaS_Senaryolari_Yatay_Olcekleme_ve_Coklu_VPS\"><span class=\"toc_number toc_depth_2\">3.3<\/span> B\u00fcy\u00fck Kurulumlar ve SaaS Senaryolar\u0131: Yatay \u00d6l\u00e7ekleme ve \u00c7oklu VPS<\/a><\/li><\/ul><\/li><li><a href=\"#PostgreSQL_Mimarisi_Ayni_VPSte_mi_Ayri_Sunucuda_mi\"><span class=\"toc_number toc_depth_1\">4<\/span> PostgreSQL Mimarisi: Ayn\u0131 VPS\u2019te mi, Ayr\u0131 Sunucuda m\u0131?<\/a><ul><li><a href=\"#PostgreSQLin_Ayni_VPSte_Tutulabilecegi_Senaryolar\"><span class=\"toc_number toc_depth_2\">4.1<\/span> PostgreSQL\u2019in Ayn\u0131 VPS\u2019te Tutulabilece\u011fi Senaryolar<\/a><\/li><li><a href=\"#Ne_Zaman_Ayri_PostgreSQL_VPSDedicated_Sunucu_Mantikli\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Ne Zaman Ayr\u0131 PostgreSQL VPS\/Dedicated Sunucu Mant\u0131kl\u0131?<\/a><\/li><li><a href=\"#Temel_PostgreSQL_Ayarlari_Odoo_ve_ERPNext_Icin_Baslangic_Noktalari\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Temel PostgreSQL Ayarlar\u0131: Odoo ve ERPNext \u0130\u00e7in Ba\u015flang\u0131\u00e7 Noktalar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Baglanti_Havuzu_Replikasyon_ve_Yuksek_Erisilebilirlik\"><span class=\"toc_number toc_depth_1\">5<\/span> Ba\u011flant\u0131 Havuzu, Replikasyon ve Y\u00fcksek Eri\u015filebilirlik<\/a><ul><li><a href=\"#PgBouncer_ile_Baglanti_Havuzu\"><span class=\"toc_number toc_depth_2\">5.1<\/span> PgBouncer ile Ba\u011flant\u0131 Havuzu<\/a><\/li><li><a href=\"#PostgreSQL_Replikasyon_Okuma_Yukunu_Bolmek_ve_Felaket_Kurtarma\"><span class=\"toc_number toc_depth_2\">5.2<\/span> PostgreSQL Replikasyon: Okuma Y\u00fck\u00fcn\u00fc B\u00f6lmek ve Felaket Kurtarma<\/a><\/li><\/ul><\/li><li><a href=\"#Yedekleme_Stratejisi_Odoo_ve_ERPNext_Verinizi_Nasil_Gercekten_Korursunuz\"><span class=\"toc_number toc_depth_1\">6<\/span> Yedekleme Stratejisi: Odoo ve ERPNext Verinizi Nas\u0131l Ger\u00e7ekten Korursunuz?<\/a><ul><li><a href=\"#3-2-1_Kurali_Immutable_Yedekler_ve_Ransomware_Riskine_Karsi_Korunma\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 3-2-1 Kural\u0131, Immutable Yedekler ve Ransomware Riskine Kar\u015f\u0131 Korunma<\/a><\/li><li><a href=\"#PostgreSQL_Icin_Mantiksal_ve_Fiziksel_Yedekler\"><span class=\"toc_number toc_depth_2\">6.2<\/span> PostgreSQL \u0130\u00e7in Mant\u0131ksal ve Fiziksel Yedekler<\/a><\/li><li><a href=\"#Snapshot_Tabanli_Yedekler_ve_Uygulama-Tutarlilik\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Snapshot Tabanl\u0131 Yedekler ve Uygulama-Tutarl\u0131l\u0131k<\/a><\/li><li><a href=\"#Yedeklerin_Saklanmasi_Sifrelenmesi_ve_Test_Edilmesi\"><span class=\"toc_number toc_depth_2\">6.4<\/span> Yedeklerin Saklanmas\u0131, \u015eifrelenmesi ve Test Edilmesi<\/a><\/li><\/ul><\/li><li><a href=\"#Izleme_Kapasite_Planlama_ve_DCHost_Tarafinda_Pratik_Oneriler\"><span class=\"toc_number toc_depth_1\">7<\/span> \u0130zleme, Kapasite Planlama ve DCHost Taraf\u0131nda Pratik \u00d6neriler<\/a><ul><li><a href=\"#Izlenecek_Temel_Metrikler\"><span class=\"toc_number toc_depth_2\">7.1<\/span> \u0130zlenecek Temel Metrikler<\/a><\/li><li><a href=\"#Staging_Ortami_ve_Guvenli_Guncellemeler\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Staging Ortam\u0131 ve G\u00fcvenli G\u00fcncellemeler<\/a><\/li><li><a href=\"#DCHost_Tarafinda_Yaygin_Mimariler\"><span class=\"toc_number toc_depth_2\">7.3<\/span> DCHost Taraf\u0131nda Yayg\u0131n Mimariler<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_ve_Yol_Haritasi_OdooERPNext_Icin_Saglam_Bir_VPS_Mimarisi_Nasil_Kurulur\"><span class=\"toc_number toc_depth_1\">8<\/span> Sonu\u00e7 ve Yol Haritas\u0131: Odoo\/ERPNext \u0130\u00e7in Sa\u011flam Bir VPS Mimarisi Nas\u0131l Kurulur?<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Odoo_ve_ERPNext_Icin_Dogru_VPS_Mimarisi_Neden_Bu_Kadar_Onemli\">Odoo ve ERPNext \u0130\u00e7in Do\u011fru <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> Mimarisi Neden Bu Kadar \u00d6nemli?<\/span><\/h2>\n<p>Odoo veya ERPNext kurulumuna giren her ekip, proje planlama toplant\u0131s\u0131nda benzer sorularla kar\u015f\u0131la\u015f\u0131yor: &#8220;Ka\u00e7 vCPU yeter? RAM ne kadar olmal\u0131? PostgreSQL ayn\u0131 VPS\u2019te mi kals\u0131n, ayr\u0131 sunucuya m\u0131 ta\u015f\u0131ns\u0131n? Yedekleri nereye, ne s\u0131kl\u0131kla alaca\u011f\u0131z?&#8221; Bu sorulara net yan\u0131t vermeden i\u015fe ba\u015flamak, ileride performans sorunlar\u0131, veri kayb\u0131 riski ve gereksiz maliyetler olarak geri d\u00f6n\u00fcyor. DCHost olarak onlarca Odoo ve ERPNext kurulumunda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ortak nokta \u015fu: Ba\u015fta do\u011fru mimariyi kuran ekipler, sonradan \u00e7ok daha az yang\u0131n s\u00f6nd\u00fcr\u00fcyor ve altyap\u0131y\u0131 b\u00fcy\u00fctmek onlar i\u00e7in \u00e7ok daha \u00f6ng\u00f6r\u00fclebilir oluyor.<\/p>\n<p>Bu yaz\u0131da, Odoo ve ERPNext i\u00e7in <strong>VPS hosting mimarisi<\/strong>ni CPU ve RAM boyutland\u0131rmas\u0131ndan PostgreSQL yap\u0131land\u0131rmas\u0131na, yedekleme ve felaket kurtarma stratejisinden y\u00fcksek eri\u015filebilirlik se\u00e7eneklerine kadar ad\u0131m ad\u0131m ele alaca\u011f\u0131z. Daha \u00f6nce yay\u0131mlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/odoo-ve-erpnext-icin-vps-hosting-rehberi-cpu-ram-worker-ve-reverse-proxy-ayarlari\/\">Odoo ve ERPNext i\u00e7in VPS hosting rehberi<\/a>nde worker ve reverse proxy ayarlar\u0131na odaklanm\u0131\u015ft\u0131k; bu yaz\u0131 ise \u00f6zellikle veritaban\u0131 mimarisi, kaynak planlama ve yedekleme taraf\u0131n\u0131 derinle\u015ftiriyor. Amac\u0131m\u0131z, elinizde somut senaryolar ve net rakamlarla, ekibinizle ayn\u0131 masada rahat\u00e7a tart\u0131\u015fabilece\u011finiz bir referans dok\u00fcman b\u0131rakmak.<\/p>\n<h2><span id=\"Odoo_ve_ERPNext_Is_Yukunu_Anlamak_Asil_Kaynak_Tuketen_Ne\">Odoo ve ERPNext \u0130\u015f Y\u00fck\u00fcn\u00fc Anlamak: As\u0131l Kaynak T\u00fcketen Ne?<\/span><\/h2>\n<p>Do\u011fru mimariyi kurman\u0131n ilk ad\u0131m\u0131, uygulaman\u0131n kayna\u011f\u0131 nerede t\u00fcketti\u011fini anlamaktan ge\u00e7er. Odoo ve ERPNext tipik bir 3 katmanl\u0131 mimari gibi \u00e7al\u0131\u015f\u0131r:<\/p>\n<ul>\n<li><strong>Uygulama katman\u0131:<\/strong> Odoo\/ERPNext servisleri, Python worker\u2019lar, background job\u2019lar.<\/li>\n<li><strong>Veritaban\u0131 katman\u0131:<\/strong> PostgreSQL, t\u00fcm i\u015f verilerinin tutuldu\u011fu kritik katman.<\/li>\n<li><strong>\u00c7evresel bile\u015fenler:<\/strong> Nginx\/Reverse proxy, e-posta queue, Redis\/Celery benzeri kuyruk sistemleri (varsa).<\/li>\n<\/ul>\n<p>Bu katmanlar\u0131n her biri farkl\u0131 \u015fekilde CPU, RAM, disk IO ve network t\u00fcketir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Stok, muhasebe, CRM gibi mod\u00fcllere yo\u011fun girilen i\u015fletmelerde <strong>veritaban\u0131<\/strong> (PostgreSQL) disk IO ve RAM\u2019i zorlar.<\/li>\n<li>Yo\u011fun raporlama, pivot tablolar ve toplu ihracat i\u015flemlerinde hem <strong>CPU<\/strong> hem de RAM t\u00fcketimi artar.<\/li>\n<li>\u00c7ok say\u0131da e\u015fzamanl\u0131 kullan\u0131c\u0131ya hizmet veren SaaS kurulumlar\u0131nda <strong>uygulama worker say\u0131s\u0131<\/strong> artt\u0131k\u00e7a CPU bask\u0131s\u0131 belirginle\u015fir.<\/li>\n<\/ul>\n<p>Dolay\u0131s\u0131yla mimariyi konu\u015furken \u201ctek VPS yeter mi?\u201d sorusundan \u00f6nce \u015fu sorulara yan\u0131t vermek gerekir:<\/p>\n<ul>\n<li>Ka\u00e7 aktif kullan\u0131c\u0131 olacak, ayn\u0131 anda sistemde ka\u00e7\u0131 \u00e7al\u0131\u015facak?<\/li>\n<li>Hangi mod\u00fcller yo\u011fun kullan\u0131lacak (muhasebe, \u00fcretim, envanter, e-ticaret vb.)?<\/li>\n<li>G\u00fcn i\u00e7i y\u00fck da\u011f\u0131l\u0131m\u0131 nas\u0131l (sabah\/ak\u015fam yo\u011fun saatler, ay sonu\/\u00e7eyrek sonu pikleri)?<\/li>\n<li>RPO\/RTO hedefleriniz nedir (en fazla ne kadar veri kayb\u0131na ve kesintiye tolerans\u0131n\u0131z var)?<\/li>\n<\/ul>\n<h2><span id=\"CPU_ve_RAM_Boyutlandirma_Farkli_Olcekler_Icin_Ornek_Senaryolar\">CPU ve RAM Boyutland\u0131rma: Farkl\u0131 \u00d6l\u00e7ekler \u0130\u00e7in \u00d6rnek Senaryolar<\/span><\/h2>\n<p>Her i\u015f y\u00fck\u00fc farkl\u0131d\u0131r; ancak sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz kurulumlara g\u00f6re baz\u0131 <strong>ba\u015flang\u0131\u00e7 \u015fablonlar\u0131<\/strong> \u00e7\u0131karmak m\u00fcmk\u00fcn. Buradaki de\u011ferler, DCHost \u00fczerinde \u00e7al\u0131\u015fan ger\u00e7ek Odoo\/ERPNext kurulumlar\u0131ndan elde etti\u011fimiz ortalama ve g\u00fcvenli ba\u015flang\u0131\u00e7 noktalar\u0131d\u0131r. \u0130htiyaca g\u00f6re yukar\u0131\/asa\u011f\u0131 ayarlamak her zaman m\u00fcmk\u00fcnd\u00fcr.<\/p>\n<h3><span id=\"Kucuk_Ekipler_520_Kullanici_Tek_VPS_Hepsi_Bir_Arada_Mimari\">K\u00fc\u00e7\u00fck Ekipler (5\u201320 Kullan\u0131c\u0131): Tek VPS, Hepsi Bir Arada Mimari<\/span><\/h3>\n<p>K\u00fc\u00e7\u00fck ekipler i\u00e7in \u00e7o\u011fu zaman <strong>tek bir g\u00fc\u00e7l\u00fc VPS<\/strong> \u00fczerinde hem uygulama hem PostgreSQL veritaban\u0131 tutmak pratik ve maliyet etkin bir \u00e7\u00f6z\u00fcmd\u00fcr.<\/p>\n<ul>\n<li><strong>\u00d6nerilen ba\u015flang\u0131\u00e7:<\/strong> 2\u20134 vCPU, 8\u201312 GB RAM, NVMe SSD disk.<\/li>\n<li><strong>Kullan\u0131m profili:<\/strong> G\u00fcnl\u00fck operasyon (teklif, fatura, basit stok), hafif raporlama.<\/li>\n<li><strong>Mimari:<\/strong>\n<ul>\n<li>Tek VPS \u00fczerinde Odoo\/ERPNext uygulamas\u0131 + PostgreSQL.<\/li>\n<li>Nginx reverse proxy ve iste\u011fe ba\u011fl\u0131 Redis ayn\u0131 makinede.<\/li>\n<li>Harici bir yedek hedefi (Object Storage veya ayr\u0131 yedek VPS).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Bu senaryoda dikkat edilmesi gereken ana nokta, CPU\u2019nun \u201cburst\u201d anlar\u0131nda (\u00f6rne\u011fin a\u011f\u0131r bir rapor \u00e7al\u0131\u015f\u0131rken) PostgreSQL ve uygulaman\u0131n birbirini bo\u011fmamas\u0131. CPU ve RAM\u2019i \u00e7ok k\u0131s\u0131tl\u0131 tutarsan\u0131z, veritaban\u0131 sorgular\u0131 uzar, uygulama worker\u2019lar\u0131 s\u0131raya girer, kullan\u0131c\u0131 taraf\u0131nda ekran ge\u00e7i\u015fleri yava\u015flar.<\/p>\n<h3><span id=\"Orta_Olcekli_Kurulumlar_2080_Kullanici_Uygulama_ve_Veritabanini_Ayirmak\">Orta \u00d6l\u00e7ekli Kurulumlar (20\u201380 Kullan\u0131c\u0131): Uygulama ve Veritaban\u0131n\u0131 Ay\u0131rmak<\/span><\/h3>\n<p>20\u2019nin \u00fczerinde aktif kullan\u0131c\u0131 ve s\u00fcrekli \u00e7al\u0131\u015fan arka plan i\u015flerinin oldu\u011fu kurulumlarda, <strong>uygulama ile PostgreSQL\u2019i ayr\u0131 VPS\u2019lere b\u00f6lmek<\/strong> ciddi avantaj sa\u011flar.<\/p>\n<ul>\n<li><strong>\u00d6nerilen ba\u015flang\u0131\u00e7:<\/strong>\n<ul>\n<li>Uygulama VPS: 4\u20136 vCPU, 8\u201312 GB RAM.<\/li>\n<li>PostgreSQL VPS: 4 vCPU, 16 GB RAM, y\u00fcksek IOPS\u2019l\u0131 NVMe disk.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Mimari avantajlar\u0131:<\/strong>\n<ul>\n<li>Uygulama taraf\u0131nda worker say\u0131s\u0131n\u0131 CPU\u2019ya g\u00f6re esnek artt\u0131rabilirsiniz.<\/li>\n<li>Veritaban\u0131 i\u00e7in RAM\u2019i ve disk performans\u0131n\u0131 ayr\u0131 optimize edebilirsiniz.<\/li>\n<li>Gelecekte sadece veritaban\u0131n\u0131 daha g\u00fc\u00e7l\u00fc bir VPS\u2019e veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>ya ta\u015f\u0131yarak \u00f6l\u00e7ekleyebilirsiniz.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Bu modelde network gecikmesi kritik hale gelir. DCHost altyap\u0131s\u0131nda ayn\u0131 veri merkezindeki VPS\u2019ler aras\u0131nda gecikme \u00e7ok d\u00fc\u015f\u00fck oldu\u011fundan, uygulama\u2013DB ayr\u0131m\u0131 pratikte belirgin bir performans kayb\u0131 yaratmadan \u00e7al\u0131\u015f\u0131r. \u00d6nemli olan, PostgreSQL\u2019in disk performans\u0131 ve RAM\u2019ini c\u00f6mert tutmakt\u0131r.<\/p>\n<h3><span id=\"Buyuk_Kurulumlar_ve_SaaS_Senaryolari_Yatay_Olcekleme_ve_Coklu_VPS\">B\u00fcy\u00fck Kurulumlar ve SaaS Senaryolar\u0131: Yatay \u00d6l\u00e7ekleme ve \u00c7oklu VPS<\/span><\/h3>\n<p>Onlarca\/ y\u00fczlerce e\u015fzamanl\u0131 kullan\u0131c\u0131, \u00e7ok kirac\u0131l\u0131 (multi-tenant) SaaS projeleri veya a\u011f\u0131r raporlama yapan kurulumlarda daha esnek bir mimari gerekir:<\/p>\n<ul>\n<li><strong>Uygulama katman\u0131:<\/strong> Birden fazla VPS \u00fczerinde Odoo\/ERPNext instance\u2019lar\u0131, araya konan Nginx\/HAProxy ile y\u00fck dengeleme.<\/li>\n<li><strong>Veritaban\u0131 katman\u0131:<\/strong> G\u00fc\u00e7l\u00fc bir PostgreSQL sunucusu (y\u00fcksek RAM + NVMe) ve en az bir read-replica.<\/li>\n<li><strong>Destek servisler:<\/strong> Ayr\u0131 Redis\/kuyruk sunucusu, ayr\u0131 loglama\/izleme sunucusu.<\/li>\n<\/ul>\n<p>B\u00f6yle bir mimari genellikle tek bir VPS\u2019in s\u0131n\u0131rlar\u0131n\u0131 a\u015ft\u0131\u011f\u0131nda, <strong>dedicated sunucu<\/strong> veya <strong>colocation<\/strong> se\u00e7eneklerine ge\u00e7i\u015fle birlikte planlan\u0131r. DCHost taraf\u0131nda, veritaban\u0131n\u0131 g\u00fc\u00e7l\u00fc bir dedicated sunucuya al\u0131p uygulama katman\u0131n\u0131 esnek VPS\u2019lerle \u00e7o\u011faltan hibrit yap\u0131lar s\u0131k kulland\u0131\u011f\u0131m\u0131z bir yakla\u015f\u0131m.<\/p>\n<h2><span id=\"PostgreSQL_Mimarisi_Ayni_VPSte_mi_Ayri_Sunucuda_mi\">PostgreSQL Mimarisi: Ayn\u0131 VPS\u2019te mi, Ayr\u0131 Sunucuda m\u0131?<\/span><\/h2>\n<p>Odoo ve ERPNext\u2019in kalbi PostgreSQL\u2019dir. Yava\u015flayan sorgular, \u015fi\u015fen tablolar veya yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f autovacuum, uygulama ne kadar iyi \u00f6l\u00e7eklenmi\u015f olursa olsun t\u00fcm sistemi yava\u015flatabilir. Bu y\u00fczden \u201cPostgreSQL\u2019i nereye koyaca\u011f\u0131z?\u201d sorusu mimarinin en kritik ad\u0131mlar\u0131ndan biridir.<\/p>\n<h3><span id=\"PostgreSQLin_Ayni_VPSte_Tutulabilecegi_Senaryolar\">PostgreSQL\u2019in Ayn\u0131 VPS\u2019te Tutulabilece\u011fi Senaryolar<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki durumlarda PostgreSQL\u2019i uygulama ile ayn\u0131 VPS \u00fczerinde tutmak <strong>makul ve pratik<\/strong> bir \u00e7\u00f6z\u00fcmd\u00fcr:<\/p>\n<ul>\n<li>K\u00fc\u00e7\u00fck\u2013orta \u00f6l\u00e7ek (20\u2019den az e\u015fzamanl\u0131 kullan\u0131c\u0131).<\/li>\n<li>Yo\u011fun, karma\u015f\u0131k raporlar\u0131n nadir \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131 senaryolar.<\/li>\n<li>Toplam veritaban\u0131 boyutunun nispeten k\u00fc\u00e7\u00fck oldu\u011fu (\u00f6rne\u011fin &lt; 50\u201380 GB) kurulumlar.<\/li>\n<li>A\u011f gecikmesini tamamen ortadan kald\u0131rmak istedi\u011finiz basit mimariler.<\/li>\n<\/ul>\n<p>Bu modelde dikkat edilmesi gerekenler:<\/p>\n<ul>\n<li>PostgreSQL i\u00e7in RAM\u2019den makul bir pay (\u00f6rne\u011fin total RAM\u2019in %30\u201340\u2019\u0131) ayr\u0131lmal\u0131.<\/li>\n<li>Disk mutlaka <strong>NVMe SSD<\/strong> olmal\u0131; HDD veya yava\u015f SATA SSD performans sorunlar\u0131 yarat\u0131r.<\/li>\n<li>Odoo\/ERPNext worker say\u0131s\u0131 art\u0131r\u0131l\u0131rken PostgreSQL\u2019in ayn\u0131 CPU\u2019yu payla\u015ft\u0131\u011f\u0131 unutulmamal\u0131.<\/li>\n<\/ul>\n<h3><span id=\"Ne_Zaman_Ayri_PostgreSQL_VPSDedicated_Sunucu_Mantikli\">Ne Zaman Ayr\u0131 PostgreSQL VPS\/Dedicated Sunucu Mant\u0131kl\u0131?<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki sinyallerden bir veya birka\u00e7\u0131 g\u00f6r\u00fcn\u00fcyorsa veritaban\u0131n\u0131 ayr\u0131 bir VPS veya dedicated sunucuya ta\u015f\u0131ma zaman\u0131 gelmi\u015f demektir:<\/p>\n<ul>\n<li>PostgreSQL CPU kullan\u0131m\u0131 s\u00fcrekli y\u00fcksek (%60\u201380+) ve raporlarda yava\u015flamalar var.<\/li>\n<li>top\/htop \u00e7\u0131kt\u0131s\u0131nda IO wait de\u011ferleri anlaml\u0131 \u015fekilde y\u00fckseliyor.<\/li>\n<li>Veritaban\u0131 boyutu onlarca\/ y\u00fczlerce GB seviyesine \u00e7\u0131km\u0131\u015f durumda.<\/li>\n<li>Gelecekte replikasyon, read-replica veya analitik ama\u00e7l\u0131 ayr\u0131 bir veritaban\u0131 kopyas\u0131 planl\u0131yorsunuz.<\/li>\n<\/ul>\n<p>Bu durumda tipik bir ayr\u0131m \u015f\u00f6yle olur:<\/p>\n<ul>\n<li><strong>PostgreSQL i\u00e7in:<\/strong> Daha az vCPU ama bol RAM (\u00f6rne\u011fin 4 vCPU, 32 GB RAM) ve y\u00fcksek IOPS\u2019l\u0131 disk.<\/li>\n<li><strong>Uygulama i\u00e7in:<\/strong> Daha fazla vCPU (\u00f6rne\u011fin 6\u20138 vCPU, 8\u201316 GB RAM), gerekti\u011finde yatay olarak \u00e7o\u011falt\u0131labilir.<\/li>\n<\/ul>\n<p>Veritaban\u0131n\u0131 ay\u0131rd\u0131\u011f\u0131n\u0131zda, yedekleme, replikasyon ve izleme i\u00e7in de daha temiz bir mimari elde edersiniz. \u00d6rne\u011fin sadece PostgreSQL VPS\u2019ine odaklanan bir <a href=\"https:\/\/www.dchost.com\/blog\/vpste-postgresqli-ucurmak-shared_buffers-work_mem-wal-ve-pgbounceri-ne-zaman-nasil-ayarlariz\/\">PostgreSQL tuning<\/a> seti uygulamak \u00e7ok daha kolay hale gelir.<\/p>\n<h3><span id=\"Temel_PostgreSQL_Ayarlari_Odoo_ve_ERPNext_Icin_Baslangic_Noktalari\">Temel PostgreSQL Ayarlar\u0131: Odoo ve ERPNext \u0130\u00e7in Ba\u015flang\u0131\u00e7 Noktalar\u0131<\/span><\/h3>\n<p>Her kurulum i\u00e7in ideal de\u011ferler farkl\u0131 olsa da, sahada iyi \u00e7al\u0131\u015fan baz\u0131 genel \u00f6nerilerden bahsedebiliriz. Detayl\u0131 teknik anlat\u0131m\u0131 ilgili PostgreSQL makalemizde bulabilirsiniz, burada Odoo\/ERPNext oda\u011f\u0131nda \u00f6zetleyece\u011fim.<\/p>\n<ul>\n<li><strong>shared_buffers:<\/strong> Toplam RAM\u2019in kabaca %20\u201325\u2019i iyi bir ba\u015flang\u0131\u00e7t\u0131r. \u00d6rne\u011fin 16 GB RAM\u2019li bir DB sunucusunda 4 GB shared_buffers makul bir de\u011ferdir.<\/li>\n<li><strong>work_mem:<\/strong> Her sorgu i\u00e7in kullan\u0131labilen bellek. \u00c7ok y\u00fcksek ayarlamak, \u00e7ok say\u0131da e\u015fzamanl\u0131 sorguda RAM\u2019in t\u00fckenmesine neden olabilir. 16\u201364 MB aral\u0131\u011f\u0131 g\u00fcvenli bir ba\u015flang\u0131\u00e7t\u0131r; a\u011f\u0131r raporlar\u0131n \u00e7ok oldu\u011fu kurulumlarda kademeli artt\u0131r\u0131labilir.<\/li>\n<li><strong>effective_cache_size:<\/strong> OS disk cache\u2019ini de hesaba katan bir de\u011fer. Genelde toplam RAM\u2019in %50\u201360\u2019\u0131 civar\u0131nda ayarlamak, sorgu planlay\u0131c\u0131s\u0131na daha do\u011fru sinyaller verir.<\/li>\n<li><strong>wal_level, checkpoint, autovacuum:<\/strong> Odoo\/ERPNext gibi s\u00fcrekli yazma yapan sistemlerde WAL ve autovacuum ayarlar\u0131n\u0131n do\u011fru yap\u0131lmas\u0131 kritik \u00f6nemdedir; aksi halde tablolar \u015fi\u015fer, performans bozulur.<\/li>\n<\/ul>\n<p>Orta\u2013b\u00fcy\u00fck kurulumlarda, ba\u011flant\u0131 havuzu (PgBouncer vb.) ile ba\u011flant\u0131 say\u0131s\u0131n\u0131 kontrol etmek ve her Odoo worker\u2019\u0131n veritaban\u0131na ayr\u0131 ayr\u0131 y\u00fcklenmesini engellemek de olduk\u00e7a etkilidir.<\/p>\n<h2><span id=\"Baglanti_Havuzu_Replikasyon_ve_Yuksek_Erisilebilirlik\">Ba\u011flant\u0131 Havuzu, Replikasyon ve Y\u00fcksek Eri\u015filebilirlik<\/span><\/h2>\n<p>Odoo ve ERPNext i\u00e7in sadece tek bir PostgreSQL sunucusu kullanmak, k\u00fc\u00e7\u00fck kurulumlarda yeterli olabilir; ancak b\u00fcy\u00fcyen i\u015f y\u00fcklerinde <strong>ba\u011flant\u0131 havuzu<\/strong>, <strong>replikasyon<\/strong> ve <strong>y\u00fcksek eri\u015filebilirlik<\/strong> devreye girer.<\/p>\n<h3><span id=\"PgBouncer_ile_Baglanti_Havuzu\">PgBouncer ile Ba\u011flant\u0131 Havuzu<\/span><\/h3>\n<p>Her Odoo\/ERPNext worker\u2019\u0131, PostgreSQL\u2019e bir veya daha fazla ba\u011flant\u0131 a\u00e7ar. Worker say\u0131s\u0131 artt\u0131k\u00e7a, veritaban\u0131 taraf\u0131nda y\u00fczlerce ba\u011flant\u0131 olu\u015fabilir ve bu da bellek t\u00fcketimi ile context switch maliyetini art\u0131r\u0131r. PgBouncer gibi hafif bir ba\u011flant\u0131 havuzu araya konarak:<\/p>\n<ul>\n<li>Veritaban\u0131na giden ger\u00e7ek ba\u011flant\u0131 say\u0131s\u0131n\u0131 s\u0131n\u0131rlayabilirsiniz.<\/li>\n<li>K\u0131sa \u00f6m\u00fcrl\u00fc ba\u011flant\u0131lar\u0131n maliyetini azaltabilirsiniz.<\/li>\n<li>Uygulama katman\u0131n\u0131 yeniden ba\u015flat\u0131rken veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 kesmemi\u015f olursunuz.<\/li>\n<\/ul>\n<p>PgBouncer\u2019\u0131 uygulama VPS\u2019inde veya PostgreSQL VPS\u2019i ile ayn\u0131 sunucuda konumland\u0131rmak m\u00fcmk\u00fcnd\u00fcr; \u00e7o\u011fu senaryoda DB taraf\u0131nda konumland\u0131rmak daha yal\u0131n bir yap\u0131 sa\u011flar.<\/p>\n<h3><span id=\"PostgreSQL_Replikasyon_Okuma_Yukunu_Bolmek_ve_Felaket_Kurtarma\">PostgreSQL Replikasyon: Okuma Y\u00fck\u00fcn\u00fc B\u00f6lmek ve Felaket Kurtarma<\/span><\/h3>\n<p>Odoo\/ERPNext\u2019te \u00e7o\u011fu i\u015f y\u00fck\u00fc yazma a\u011f\u0131rl\u0131kl\u0131d\u0131r; ancak raporlama, BI ara\u00e7lar\u0131 ve d\u0131\u015f entegrasyonlar ciddi okuma y\u00fck\u00fc olu\u015fturabilir. PostgreSQL\u2019in streaming replication \u00f6zelli\u011fiyle bir veya daha fazla <strong>read-replica<\/strong> kurarak:<\/p>\n<ul>\n<li>Raporlama ve analitik sorgular\u0131 replica \u00fczerine y\u00f6nlendirebilirsiniz.<\/li>\n<li>Ana veritaban\u0131 \u00fczerindeki okuma y\u00fck\u00fcn\u00fc azalt\u0131rs\u0131n\u0131z.<\/li>\n<li>Felaket durumunda, replica\u2019y\u0131 k\u0131sa s\u00fcrede yeni master\u2019a terfi ettirebilirsiniz.<\/li>\n<\/ul>\n<p>Burada devreye <strong>RPO\/RTO hedefleri<\/strong> girer. KOB\u0130\u2019ler i\u00e7in ger\u00e7ek\u00e7i RPO\/RTO nas\u0131l belirlenir, hosting taraf\u0131nda ne kadar\u0131n\u0131 kar\u015f\u0131layabilirsiniz gibi sorular\u0131 daha detayl\u0131 olarak <a href=\"https:\/\/www.dchost.com\/blog\/kobiler-icin-rpo-rto-ve-felaket-kurtarma-plani-hosting-tarafinda-gercekci-hedefler\/\">RPO\/RTO ve felaket kurtarma rehberi<\/a>nde anlatt\u0131k. Odoo\/ERPNext i\u00e7in de ayn\u0131 prensipler ge\u00e7erlidir.<\/p>\n<h2><span id=\"Yedekleme_Stratejisi_Odoo_ve_ERPNext_Verinizi_Nasil_Gercekten_Korursunuz\">Yedekleme Stratejisi: Odoo ve ERPNext Verinizi Nas\u0131l Ger\u00e7ekten Korursunuz?<\/span><\/h2>\n<p>Odoo veya ERPNext kurulumunuz ne kadar h\u0131zl\u0131 ve \u00f6l\u00e7eklenebilir olursa olsun, <strong>sa\u011flam bir yedekleme stratejisi<\/strong> yoksa ger\u00e7ek anlamda g\u00fcvende de\u011filsiniz. \u00d6zellikle PostgreSQL gibi transactional bir veritaban\u0131 s\u00f6z konusu oldu\u011funda, \u201chaftada bir tam yedek\u201d mant\u0131\u011f\u0131 art\u0131k kabul edilebilir de\u011fil.<\/p>\n<h3><span id=\"3-2-1_Kurali_Immutable_Yedekler_ve_Ransomware_Riskine_Karsi_Korunma\">3-2-1 Kural\u0131, Immutable Yedekler ve Ransomware Riskine Kar\u015f\u0131 Korunma<\/span><\/h3>\n<p>Modern yedekleme stratejilerinin temelinde <strong>3-2-1 kural\u0131<\/strong> vard\u0131r:<\/p>\n<ul>\n<li>Verinizin en az <strong>3 kopyas\u0131<\/strong> olmal\u0131 (1 \u00fcretim, 2 yedek).<\/li>\n<li>Bu kopyalar en az <strong>2 farkl\u0131 ortamda<\/strong> tutulmal\u0131 (\u00f6rne\u011fin VPS diski + harici Object Storage).<\/li>\n<li>En az <strong>1 kopya<\/strong> farkl\u0131 bir lokasyonda veya air-gap\u2019e yak\u0131n bir ortamda saklanmal\u0131.<\/li>\n<\/ul>\n<p>Ransomware ve benzeri sald\u0131r\u0131lara kar\u015f\u0131, salt 3-2-1 yetmez; yedeklerin <strong>immutable<\/strong> (de\u011fi\u015ftirilemez) \u015fekilde saklanmas\u0131, yazma korumal\u0131 period\u2019lar ve d\u00fczenli geri d\u00f6n\u00fc\u015f testleri de gerekir. Bu konuyu hem cPanel\/VPS hem de genel altyap\u0131 perspektifinden <a href=\"https:\/\/www.dchost.com\/blog\/ransomwarea-dayanikli-hosting-yedekleme-stratejisi-3-2-1-kurali-immutable-backup-ve-air-gap\/\">ransomware\u2019a dayan\u0131kl\u0131 yedekleme stratejisi<\/a> makalemizde detayland\u0131rd\u0131k; Odoo\/ERPNext i\u00e7in de birebir ge\u00e7erlidir.<\/p>\n<h3><span id=\"PostgreSQL_Icin_Mantiksal_ve_Fiziksel_Yedekler\">PostgreSQL \u0130\u00e7in Mant\u0131ksal ve Fiziksel Yedekler<\/span><\/h3>\n<p>PostgreSQL\u2019i yedeklerken iki temel yakla\u015f\u0131m vard\u0131r:<\/p>\n<ul>\n<li><strong>Mant\u0131ksal yedekler (pg_dump\/pg_dumpall):<\/strong>\n<ul>\n<li>Tablo ve \u015fema bazl\u0131; daha esnek, ancak b\u00fcy\u00fck veritabanlar\u0131nda yava\u015f olabilir.<\/li>\n<li>\u015eema de\u011fi\u015fikliklerinde (upgrade, migration) granular geri d\u00f6n\u00fc\u015f imk\u00e2n\u0131 sa\u011flar.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Fiziksel yedekler (pg_basebackup, pgBackRest vb.):<\/strong>\n<ul>\n<li>Veritaban\u0131 klas\u00f6r\u00fcn\u00fcn bire bir kopyas\u0131n\u0131 al\u0131r.<\/li>\n<li>B\u00fcy\u00fck veritabanlar\u0131nda daha h\u0131zl\u0131 ve verimli \u00e7al\u0131\u015f\u0131r.<\/li>\n<li>Point-in-Time Recovery (PITR) ile belli bir ana geri d\u00f6n\u00fc\u015f imk\u00e2n\u0131 sunar.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Odoo\/ERPNext kurulumlar\u0131nda, genellikle \u015fu kombinasyon iyi \u00e7al\u0131\u015f\u0131r:<\/p>\n<ul>\n<li>G\u00fcnl\u00fck 1 tam <strong>fiziksel yedek<\/strong> (\u00f6rne\u011fin pgBackRest ile).<\/li>\n<li>10\u201315 dakikada bir WAL ar\u015fivleme ve PITR imk\u00e2n\u0131.<\/li>\n<li>Haftal\u0131k veya kritik s\u00fcr\u00fcm ge\u00e7i\u015flerinden \u00f6nce mant\u0131ksal (pg_dump) yedekler.<\/li>\n<\/ul>\n<p>PgBackRest ve WAL ar\u015fivlemeyi VPS ortam\u0131nda nas\u0131l kurabilece\u011finizi ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/vps-uzerinde-postgresql-yedekleme-ve-pitr-pgbackrest-ile-wal-arsivleme-adim-adim\/\">PostgreSQL yedekleme ve PITR rehberi<\/a>, Odoo\/ERPNext kurulumlar\u0131n\u0131za do\u011frudan uygulanabilir.<\/p>\n<h3><span id=\"Snapshot_Tabanli_Yedekler_ve_Uygulama-Tutarlilik\">Snapshot Tabanl\u0131 Yedekler ve Uygulama-Tutarl\u0131l\u0131k<\/span><\/h3>\n<p>Bir\u00e7ok VPS altyap\u0131s\u0131nda, disk seviyesinde <strong>snapshot<\/strong> almak m\u00fcmk\u00fcnd\u00fcr. Snapshot yedekler h\u0131zl\u0131d\u0131r ve t\u00fcm diskin anl\u0131k g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc al\u0131r; ancak veritaban\u0131 a\u00e7\u0131s\u0131ndan bak\u0131ld\u0131\u011f\u0131nda \u201cuygulama-tutarl\u0131\u201d olup olmamas\u0131 \u00f6nemlidir.<\/p>\n<ul>\n<li><strong>Crash-tutarl\u0131 snapshot:<\/strong> Elektrik kesintisi ya\u015fanm\u0131\u015f gibi bir anl\u0131k g\u00f6r\u00fcnt\u00fc; PostgreSQL genellikle toparlar ama her zaman risk bar\u0131nd\u0131r\u0131r.<\/li>\n<li><strong>Uygulama-tutarl\u0131 snapshot:<\/strong> Snapshot \u00f6ncesi veritaban\u0131 k\u0131sa s\u00fcreli\u011fine dondurulur (\u00f6rne\u011fin fsfreeze veya LVM snapshot ile), b\u00f6ylece disk \u00fczerinde tutarl\u0131 bir durum yakalan\u0131r.<\/li>\n<\/ul>\n<p>Odoo\/ERPNext i\u00e7in ideal yakla\u015f\u0131m, <strong>snapshot\u2019\u0131 PostgreSQL seviyesindeki yedeklere ek bir katman<\/strong> olarak kullanmakt\u0131r; tek ba\u015f\u0131na snapshot\u2019a g\u00fcvenmek yerine, d\u00fczenli mant\u0131ksal\/fiziksel yedeklerle birlikte d\u00fc\u015f\u00fcnmek gerekir.<\/p>\n<h3><span id=\"Yedeklerin_Saklanmasi_Sifrelenmesi_ve_Test_Edilmesi\">Yedeklerin Saklanmas\u0131, \u015eifrelenmesi ve Test Edilmesi<\/span><\/h3>\n<p>Yedek almak i\u015fin yar\u0131s\u0131 bile de\u011fil; as\u0131l kritik k\u0131sm\u0131 saklama, \u015fifreleme ve geri d\u00f6n\u00fc\u015f testleridir:<\/p>\n<ul>\n<li><strong>Depolama:<\/strong> Yedekleri \u00fcretim VPS\u2019inden ayr\u0131 bir VPS\u2019e veya Object Storage\u2019a kopyalay\u0131n. Ayn\u0131 diskte tutulan yedek, yedek de\u011fildir.<\/li>\n<li><strong>\u015eifreleme:<\/strong> \u00d6zellikle ki\u015fisel veri i\u00e7eren ERP veritabanlar\u0131n\u0131 yedeklerken, disk veya obje seviyesinde \u015fifreleme kullan\u0131n.<\/li>\n<li><strong>Saklama s\u00fcreleri:<\/strong> KVKK\/GDPR gerekliliklerinize g\u00f6re saklama s\u00fcresini belirleyin; gere\u011finden fazla veri tutmak da risk yaratabilir.<\/li>\n<li><strong>Geri d\u00f6n\u00fc\u015f testi:<\/strong> Belirli aral\u0131klarla test ortam\u0131na geri y\u00fckleme yaparak, yede\u011fin ger\u00e7ekten \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<\/ul>\n<p>DCHost\u2019ta g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en b\u00fcy\u00fck hatalardan biri, y\u0131llarca hi\u00e7 test edilmemi\u015f yedeklere g\u00fcvenmek. Oysa bir kez bile test restore yap\u0131ld\u0131\u011f\u0131nda, eksik configuration, bozuk dump veya yanl\u0131\u015f \u015fifreleme anahtarlar\u0131 hemen ortaya \u00e7\u0131k\u0131yor.<\/p>\n<h2><span id=\"Izleme_Kapasite_Planlama_ve_DCHost_Tarafinda_Pratik_Oneriler\">\u0130zleme, Kapasite Planlama ve DCHost Taraf\u0131nda Pratik \u00d6neriler<\/span><\/h2>\n<p>Odoo ve ERPNext i\u00e7in do\u011fru mimariyi kurduktan sonra i\u015f bitmiyor; sistemin zamanla nas\u0131l davrand\u0131\u011f\u0131n\u0131 g\u00f6zlemek ve gerekti\u011finde k\u00fc\u00e7\u00fck ayarlamalar yapmak gerekiyor.<\/p>\n<h3><span id=\"Izlenecek_Temel_Metrikler\">\u0130zlenecek Temel Metrikler<\/span><\/h3>\n<p>VPS \u00fczerinde d\u00fczenli takip etmeniz gereken ba\u015fl\u0131ca g\u00f6stergeler:<\/p>\n<ul>\n<li><strong>CPU kullan\u0131m\u0131:<\/strong> \u00d6zellikle business saatlerinde s\u00fcrekli %70\u201380 band\u0131ndaysa, vCPU artt\u0131rmay\u0131 veya worker say\u0131s\u0131n\u0131 optimize etmeyi d\u00fc\u015f\u00fcn\u00fcn.<\/li>\n<li><strong>RAM kullan\u0131m\u0131 ve swap:<\/strong> RAM s\u00fcrekli dolu, swap kullan\u0131m\u0131 art\u0131yorsa, PostgreSQL\/uygulama ayarlar\u0131n\u0131 g\u00f6zden ge\u00e7irin veya RAM y\u00fckseltin.<\/li>\n<li><strong>Disk IOPS ve latency:<\/strong> PostgreSQL i\u00e7in kritik. NVMe disklerde dahi anormal gecikmeler g\u00f6r\u00fcyorsan\u0131z sorgu optimizasyonu ve indekslemeye bakmak gerekir.<\/li>\n<li><strong>PostgreSQL \u00f6zel metrikleri:<\/strong> slow query log, autovacuum istatistikleri, bloat oranlar\u0131.<\/li>\n<\/ul>\n<p>PostgreSQL \u00f6zelinde autovacuum ve bloat y\u00f6netimini detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/postgresql-autovacuum-tuning-ve-bloatla-barismak-vpste-pratik-ayarlar-ve-pg_repack-ile-neredeyse-sifir-kesinti\/\">autovacuum tuning rehberi<\/a>, \u00f6zellikle b\u00fcy\u00fcyen Odoo\/ERPNext veritabanlar\u0131nda hayat kurtaran bir kaynak.<\/p>\n<h3><span id=\"Staging_Ortami_ve_Guvenli_Guncellemeler\">Staging Ortam\u0131 ve G\u00fcvenli G\u00fcncellemeler<\/span><\/h3>\n<p>Odoo veya ERPNext s\u00fcr\u00fcm g\u00fcncellemeleri, mod\u00fcl ekleme\/\u00e7\u0131karma i\u015flemleri ve yap\u0131land\u0131rma denemeleri i\u00e7in <strong>staging\/test ortam\u0131<\/strong> kullanmak b\u00fcy\u00fck fark yarat\u0131r. DCHost \u00fczerinde s\u0131k uygulad\u0131\u011f\u0131m\u0131z pratik yakla\u015f\u0131m \u015f\u00f6yle:<\/p>\n<ul>\n<li>Canl\u0131 veritaban\u0131n\u0131n belirli bir anl\u0131k kopyas\u0131n\u0131 staging VPS\u2019ine geri y\u00fckleyin.<\/li>\n<li>Yeni mod\u00fclleri, \u00f6zelle\u015ftirmeleri ve performans ayarlar\u0131n\u0131 burada deneyin.<\/li>\n<li>\u0130\u015fe yarayan de\u011fi\u015fiklikleri, planl\u0131 bir bak\u0131m penceresinde canl\u0131 ortama ta\u015f\u0131y\u0131n.<\/li>\n<\/ul>\n<p>B\u00f6ylece canl\u0131 ortamda s\u00fcrprizlerle kar\u015f\u0131la\u015fmaz, yedek ve geri d\u00f6n\u00fc\u015f plan\u0131n\u0131z\u0131 da pratikte s\u0131nam\u0131\u015f olursunuz.<\/p>\n<h3><span id=\"DCHost_Tarafinda_Yaygin_Mimariler\">DCHost Taraf\u0131nda Yayg\u0131n Mimariler<\/span><\/h3>\n<p>DCHost m\u00fc\u015fterilerinde s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz birka\u00e7 ba\u015far\u0131l\u0131 desen:<\/p>\n<ul>\n<li><strong>Tek VPS + harici yedek:<\/strong> K\u00fc\u00e7\u00fck ekipler i\u00e7in maliyet\u2013performans dengesi y\u00fcksek.<\/li>\n<li><strong>Uygulama VPS + PostgreSQL VPS + Object Storage yede\u011fi:<\/strong> 20\u201380 kullan\u0131c\u0131 band\u0131 i\u00e7in ideal, esnek ve g\u00fcvenli.<\/li>\n<li><strong>Dedicated PostgreSQL + \u00e7oklu uygulama VPS:<\/strong> Orta\u2013b\u00fcy\u00fck kurulumlar ve SaaS yap\u0131lar i\u00e7in hem performansl\u0131 hem gelece\u011fe a\u00e7\u0131k bir mimari.<\/li>\n<\/ul>\n<p>Her \u00fc\u00e7 modelde de ortak noktam\u0131z, yedeklerin mutlaka ayr\u0131 bir altyap\u0131ya (ayr\u0131 VPS veya Object Storage) ta\u015f\u0131nmas\u0131 ve d\u00fczenli geri d\u00f6n\u00fc\u015f testleriyle do\u011frulanmas\u0131. Zaten bu bak\u0131\u015f a\u00e7\u0131s\u0131n\u0131, genel yedekleme stratejilerini anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/3-2-1-yedekleme-stratejisi-neden-ise-yariyor-cpanel-plesk-ve-vpste-otomatik-yedekleri-nasil-kurarsin\/\">3-2-1 yedekleme stratejisi rehberi<\/a>nde de vurguluyoruz.<\/p>\n<h2><span id=\"Sonuc_ve_Yol_Haritasi_OdooERPNext_Icin_Saglam_Bir_VPS_Mimarisi_Nasil_Kurulur\">Sonu\u00e7 ve Yol Haritas\u0131: Odoo\/ERPNext \u0130\u00e7in Sa\u011flam Bir VPS Mimarisi Nas\u0131l Kurulur?<\/span><\/h2>\n<p>Odoo ve ERPNext i\u00e7in do\u011fru VPS mimarisini kurmak, tek seferlik bir karar de\u011fil; i\u015f y\u00fck\u00fcn\u00fczle birlikte evrilen bir s\u00fcre\u00e7. Ancak ba\u015flang\u0131\u00e7ta birka\u00e7 ana prensibe dikkat ederseniz, ileride b\u00fcy\u00fck refakt\u00f6rlere ihtiya\u00e7 duymadan, kontroll\u00fc ve \u00f6ng\u00f6r\u00fclebilir \u015fekilde b\u00fcy\u00fcyebilirsiniz:<\/p>\n<ul>\n<li>K\u00fc\u00e7\u00fck kurulumlarda bile CPU ve RAM\u2019i \u00e7ok k\u0131s\u0131p performanstan feragat etmeyin; 2\u20134 vCPU ve en az 8 GB RAM genellikle iyi bir taban.<\/li>\n<li>PostgreSQL\u2019i hafife almay\u0131n; veritaban\u0131 RAM ve disk IOPS\u2019dan beslenir, NVMe ve do\u011fru ayarlar fark yarat\u0131r.<\/li>\n<li>20+ aktif kullan\u0131c\u0131ya yakla\u015ft\u0131\u011f\u0131n\u0131zda, uygulama ve veritaban\u0131n\u0131 ay\u0131rmay\u0131 ciddi \u015fekilde d\u00fc\u015f\u00fcn\u00fcn.<\/li>\n<li>Yedekleme taraf\u0131nda 3-2-1 kural\u0131n\u0131, immutable yedekleri ve d\u00fczenli geri d\u00f6n\u00fc\u015f testlerini standart hale getirin.<\/li>\n<li>\u0130zleme, loglama ve staging ortam\u0131 ile mimarinizi s\u00fcrekli iyile\u015ftirin.<\/li>\n<\/ul>\n<p>DCHost olarak hem k\u00fc\u00e7\u00fck KOB\u0130 kurulumlar\u0131nda hem de \u00e7ok kirac\u0131l\u0131 SaaS projelerinde Odoo ve ERPNext altyap\u0131lar\u0131n\u0131 y\u0131llard\u0131r y\u00f6netiyoruz. \u0130htiyac\u0131n\u0131z tek VPS\u2019te t\u00fcm sistemi ko\u015fturmak da olsa, PostgreSQL\u2019i dedicated sunucuya ta\u015f\u0131y\u0131p uygulama katman\u0131n\u0131 \u00e7oklu VPS ile \u00f6l\u00e7eklemek de olsa, mimari tasar\u0131m, kapasite planlama ve yedekleme kurgusu konusunda ekibimizle birlikte yan\u0131n\u0131zday\u0131z. Mevcut kurulumunuzu g\u00f6zden ge\u00e7irmek veya yeni bir projeye ba\u015flamadan \u00f6nce mimari taslak \u00e7\u0131karmak isterseniz, DCHost destek ekibine birka\u00e7 sat\u0131rl\u0131k \u00f6zetle ula\u015fman\u0131z yeterli; kalan\u0131n\u0131 beraber \u015fekillendiririz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Odoo ve ERPNext \u0130\u00e7in Do\u011fru VPS Mimarisi Neden Bu Kadar \u00d6nemli?2 Odoo ve ERPNext \u0130\u015f Y\u00fck\u00fcn\u00fc Anlamak: As\u0131l Kaynak T\u00fcketen Ne?3 CPU ve RAM Boyutland\u0131rma: Farkl\u0131 \u00d6l\u00e7ekler \u0130\u00e7in \u00d6rnek Senaryolar3.1 K\u00fc\u00e7\u00fck Ekipler (5\u201320 Kullan\u0131c\u0131): Tek VPS, Hepsi Bir Arada Mimari3.2 Orta \u00d6l\u00e7ekli Kurulumlar (20\u201380 Kullan\u0131c\u0131): Uygulama ve Veritaban\u0131n\u0131 Ay\u0131rmak3.3 B\u00fcy\u00fck Kurulumlar ve SaaS Senaryolar\u0131: [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4999,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4998","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4998","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=4998"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4998\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4999"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4998"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4998"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4998"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}