{"id":563,"date":"2026-04-05T18:35:00","date_gmt":"2026-04-05T15:35:00","guid":{"rendered":"https:\/\/m4.ist\/index.php\/2026\/04\/05\/proxmox-ve-yedekleme-plani-proxmox\/"},"modified":"2026-04-05T18:35:00","modified_gmt":"2026-04-05T15:35:00","slug":"proxmox-ve-yedekleme-plani-proxmox","status":"publish","type":"post","link":"https:\/\/m4.ist\/index.php\/2026\/04\/05\/proxmox-ve-yedekleme-plani-proxmox\/","title":{"rendered":"Proxmox VE yedekleme plani: 2026 Pratik Rehber"},"content":{"rendered":"<h1>Proxmox VE Snapshot ile Offsite Yedekleme: Uygulamal\u0131 Rehber<\/h1>\n<div class=\"rankmath-manual-toc\" data-rankmath-toc=\"1\">\n<p><strong>Icindekiler<\/strong><\/p>\n<ul>\n<li><a href=\"#bolum-1\">\u0130\u00e7indekiler<\/a><\/li>\n<li><a href=\"#bolum-2\">Proxmox VE Snapshot Neden \u00d6nemlidir?<\/a><\/li>\n<li><a href=\"#bolum-3\">Gerekli Donan\u0131m ve Yaz\u0131l\u0131m \u015eartlar\u0131<\/a><\/li>\n<li><a href=\"#bolum-4\">Ad\u0131m Ad\u0131m Uygulama Rehberi<\/a><\/li>\n<li><a href=\"#bolum-5\">1. VM ID\u2019lerini \u00d6\u011frenme<\/a><\/li>\n<li><a href=\"#bolum-6\">2. Snapshot Olu\u015fturma<\/a><\/li>\n<li><a href=\"#bolum-7\">3. Offsite Senkronizasyon<\/a><\/li>\n<li><a href=\"#bolum-8\">4. Manuel Ba\u015flatma ve Servis<\/a><\/li>\n<li><a href=\"#bolum-9\">5. \u00d6rnek Snapshot Komutu<\/a><\/li>\n<li><a href=\"#bolum-10\">6. Geri Y\u00fckleme<\/a><\/li>\n<li><a href=\"#bolum-11\">7. Log ve \u0130zleme<\/a><\/li>\n<li><a href=\"#bolum-12\">8. G\u00fcncelleme ve Test<\/a><\/li>\n<li><a href=\"#bolum-13\">Y\u00f6ntem veya Ara\u00e7 Kar\u015f\u0131la\u015ft\u0131rma Tablosu<\/a><\/li>\n<li><a href=\"#bolum-14\">Risk ve Rollback Noktas\u0131 Tablosu<\/a><\/li>\n<li><a href=\"#bolum-15\">Snapshot ve Offsite Yedekleme Kontrol Listesi<\/a><\/li>\n<li><a href=\"#bolum-16\">Sorun Giderme ve Rollback<\/a><\/li>\n<li><a href=\"#bolum-17\">Performans ve G\u00fcvenlik Optimizasyonu<\/a><\/li>\n<li><a href=\"#bolum-18\">Sonu\u00e7 ve H\u0131zl\u0131 Tekrar<\/a><\/li>\n<li><a href=\"#bolum-19\">S\u0131k Sorulan Sorular<\/a><\/li>\n<\/ul>\n<\/div>\n<h2 id=\"bolum-1\">\u0130\u00e7indekiler<\/h2>\n<ul>\n<li><a href=\"#proxmox-ve-snapshot-neden-\u00f6nemlidir\">Proxmox VE Snapshot Neden \u00d6nemlidir?<\/a><\/li>\n<li><a href=\"#gerekli-donan\u0131m-ve-yaz\u0131l\u0131m\u2011\u015fartlar\u0131\">Gerekli Donan\u0131m ve Yaz\u0131l\u0131m \u015eartlar\u0131<\/a><\/li>\n<li><a href=\"#ad\u0131m-ad\u0131m-uygulama-rehberi\">Ad\u0131m Ad\u0131m Uygulama Rehberi<\/a><\/li>\n<li><a href=\"#y\u00f6ntem-veya-ar\u00e7-kar\u015f\u0131la\u015ft\u0131rma-tablosu\">Y\u00f6ntem veya Ara\u00e7 Kar\u015f\u0131la\u015ft\u0131rma Tablosu<\/a><\/li>\n<li><a href=\"#risk-ve-rollback-noktas\u0131-tablosu\">Risk ve Rollback Noktas\u0131 Tablosu<\/a><\/li>\n<li><a href=\"#snapshot-ve-offsite-yedekleme-kontrol-listesi\">Snapshot ve Offsite Yedekleme Kontrol Listesi<\/a><\/li>\n<li><a href=\"#sorun-giderme-ve-rollback\">Sorun Giderme ve Rollback<\/a><\/li>\n<li><a href=\"#performans-ve\u2011g\u00fcvenlik\u2011optimizasyonu\">Performans ve G\u00fcvenlik Optimizasyonu<\/a><\/li>\n<li><a href=\"#sonu\u00e7-ve\u2011h\u0131zl\u0131\u2011tekrar\">Sonu\u00e7 ve H\u0131zl\u0131 Tekrar<\/a><\/li>\n<li><a href=\"#s\u0131k\u2011sorulan\u2011sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<\/ul>\n<h2 id=\"bolum-2\">Proxmox VE Snapshot Neden \u00d6nemlidir?<\/h2>\n<p>Proxmox VE snapshot, sanal makinelerin anl\u0131k g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc al\u0131r, bu da de\u011fi\u015fiklikleri zaman damgas\u0131yla kaydeder. Snapshot, VM i\u00e7indeki t\u00fcm disk bloklar\u0131n\u0131 kilitleyerek, yedekleme s\u00fcresini k\u0131salt\u0131r. Snapshot al\u0131nd\u0131\u011f\u0131nda, VM \u00e7al\u0131\u015fma s\u00fcresini durdurmaz; ayn\u0131 anda veri tutarl\u0131l\u0131\u011f\u0131 sa\u011flan\u0131r. \u00d6rne\u011fin, 20 GB&#8217;l\u0131k bir veri taban\u0131 sunucusunda 5 saniyelik snapshot, sadece 1 GB veri kayb\u0131na yol a\u00e7ar. Offsite yedekleme, bu snapshotlar\u0131 uzak bir sunucuya \u015fifreli olarak g\u00f6nderir, b\u00f6ylece fiziksel hasar veya veri h\u0131rs\u0131zl\u0131\u011f\u0131 riskini azalt\u0131r. Proxmox Backup Server, bu transferi otomatikle\u015ftirir ve s\u0131k\u0131\u015ft\u0131rma, dedup ve \u015fifreleme se\u00e7enekleri sunar. PBS, snapshotlar\u0131 \u201cproxmox backup\u201d format\u0131nda depolar, bu format veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc garantiler.<\/p>\n<p>Yedekleme plan\u0131 olu\u015ftururken, hedef sunucunun a\u011f geni\u015fli\u011fi ve gecikme s\u00fcresi g\u00f6z \u00f6n\u00fcnde bulundurulmal\u0131d\u0131r. \u00d6rne\u011fin, 1 Gbps ba\u011flant\u0131 \u00fczerinden g\u00fcnl\u00fck 50 GB veri senkronizasyonu, 30 dakikada tamamlanabilir. Snapshots ayr\u0131ca, test ortamlar\u0131nda \u201cblue\u2011green deployment\u201d gibi stratejileri kolayla\u015ft\u0131r\u0131r. Offsite yedekleme ile, veri kurtarma s\u00fcresi (RTO) dakikalar i\u00e7inde ger\u00e7ekle\u015febilir. Bu s\u00fcre\u00e7, i\u015f s\u00fcreklili\u011fi planlar\u0131nda kritik bir bile\u015fen olarak kabul edilir. Snapshot ve offsite yedekleme birle\u015fimi, veri kayb\u0131n\u0131 minimuma indirir ve maliyetleri kontrol alt\u0131nda tutar. Sonu\u00e7 olarak, Proxmox VE snapshot ve offsite yedekleme, i\u015fletmelerin g\u00fcvenli\u011fini g\u00fc\u00e7lendirir.<\/p>\n<p>Ek baglam icin <a href=\"\/proxmox-ve-snapshot-ve-offsite-yedekleme-plani-rehberi\">proxmox ve snapshot ve offsite yedekleme plani rehberi<\/a> ve <a href=\"https:\/\/pbs.proxmox.com\/docs\/proxmox-backup.pdf\" target=\"_blank\" rel=\"noopener\">proxmox backup.pdf<\/a> baglantilarina bakabilirsiniz.<\/p>\n<h2 id=\"bolum-3\">Gerekli Donan\u0131m ve Yaz\u0131l\u0131m \u015eartlar\u0131<\/h2>\n<p>Proxmox VE 7.0 veya \u00fcst\u00fc, snapshot \u00f6zelliklerini destekler, eski s\u00fcr\u00fcmlerle uyumlu de\u011fildir. Proxmox Backup Server (PBS) 4.0 veya sonras\u0131 \u00f6nerilir, \u00e7\u00fcnk\u00fc eski s\u00fcr\u00fcmler dedup \u00f6zelli\u011fini s\u0131n\u0131rl\u0131 sunar. PBS i\u00e7in minimum 2 GB RAM ve 50 GB disk alan\u0131 gereklidir; yedekleme hacmi artt\u0131k\u00e7a alan artt\u0131r\u0131lmal\u0131d\u0131r. VM&#8217;lerinizin toplam disk boyutu, PBS depolama alan\u0131n\u0131n %70\u2019i kadar yer tutmal\u0131d\u0131r. A\u011f ge\u00e7idi olarak 100 Mbps kablosuz yerine 1 Gbps Ethernet tercih edilmelidir, bu transfer h\u0131z\u0131n\u0131 3\u20114 kat art\u0131r\u0131r.<\/p>\n<p>\u015eifreleme anahtarlar\u0131, 256\u2011bit AES kullan\u0131larak olu\u015fturulur, bu anahtarlar\u0131 g\u00fcvenli bir ortamda saklamal\u0131s\u0131n\u0131z. Offsite hedefinizin IP adresi, g\u00fcvenlik duvar\u0131nda 443 portuna izin verirken, TLS ba\u011flant\u0131s\u0131 a\u00e7\u0131l\u0131r. Zamanlama i\u00e7in cron job, her g\u00fcn saat 02:00\u2019de pbm backup komutunu \u00e7al\u0131\u015ft\u0131r\u0131r; bu saat, sistem trafi\u011finin d\u00fc\u015f\u00fck oldu\u011fu zamand\u0131r. PBS\u2019yi kurmadan \u00f6nce, hem sunucu hem de hedef cihaz\u0131n NTP senkronizasyonu sa\u011flanmal\u0131d\u0131r.<\/p>\n<p>PBS\u2019nin y\u00f6netim paneli, HTTPS \u00fczerinden 4443 portunda dinler; bu portu firewall\u2019da a\u00e7\u0131n. Backup verilerinizi s\u0131k\u0131\u015ft\u0131rmak i\u00e7in gzip seviyesini 6 olarak ayarlayabilirsiniz, bu dosya boyutunu %20 azalt\u0131r. Dedup i\u015flemi, ayn\u0131 bloklar\u0131n tek bir kopyas\u0131n\u0131 tutarak depolama maliyetini %30 azalt\u0131r. Yedekleme s\u00fcrecinde, \u201cmax_parallel\u201d de\u011ferini 4 olarak ayarlamak, disk IO\u2019yu dengeleyebilir. \u015eifreleme anahtar\u0131 y\u00f6netimi i\u00e7in, HashiCorp Vault veya AWS KMS gibi \u00e7\u00f6z\u00fcmler kullan\u0131labilir. PBS kurulumunda, \u201c\/etc\/pbs\/conf.d\u201d dizinine konfig\u00fcrasyon dosyalar\u0131 eklenir, bu dosyalar JSON format\u0131ndad\u0131r.<\/p>\n<p>Sunucu \u00fczerinde, \u201cpve-manager\u201d ile snapshot olu\u015fturma izinleri, role bazl\u0131 olarak atan\u0131r. Snapshot i\u00e7in kullan\u0131lan ZFS havuzlar\u0131, \u201cdedup=on\u201d ve \u201ccompression=lz4\u201d parametreleriyle optimize edilmelidir. Offsite senkronizasyon, hedef sunucuda da ayn\u0131 s\u00fcr\u00fcm PBS\u2019nin y\u00fckl\u00fc olmas\u0131 gerekir. A\u011f\u0131 izlemek i\u00e7in, ntopng veya Grafana ile bant geni\u015fli\u011fi ve gecikme metrikleri izlenebilir. Son olarak, yedekleme g\u00fcnl\u00fckleri, \/var\/log\/pbs\/ dizinine kaydedilir ve g\u00fcnl\u00fck 7 g\u00fcn tutulur.<\/p>\n<h2 id=\"bolum-4\">Ad\u0131m Ad\u0131m Uygulama Rehberi<\/h2>\n<h3 id=\"bolum-5\">1. VM ID\u2019lerini \u00d6\u011frenme<\/h3>\n<p>PBS kurulumunu tamamlad\u0131ktan sonra, \u00f6ncelikle yedeklenecek VM\u2019lerin ID\u2019lerini \u00f6\u011frenmek gerekir.<br \/>\n\u201cpvesh get \/nodes\/{node}\/qemu\u201d komutu, t\u00fcm VM ID\u2019lerini listeler, \u00f6rne\u011fin 101, 102 ve 103.  <\/p>\n<h3 id=\"bolum-6\">2. Snapshot Olu\u015fturma<\/h3>\n<p>Snapshot almak i\u00e7in, \u201cpbm backup &#8211;node {node} &#8211;job {jobname} {vmid}\u201d komutu kullan\u0131l\u0131r.<br \/>\nJob tan\u0131mlarken, \/etc\/pbs\/jobs\/{jobname}.json dosyas\u0131 olu\u015fturulur; bu dosya, snapshot parametrelerini i\u00e7erir.  <\/p>\n<pre><code class=\"language-json\">{\n  \"schedule\": \"02:00\",\n  \"storage\": \"pbs:\/\/storage1\",\n  \"compression\": \"lz4\",\n  \"encryption\": \"aes256\",\n  \"max_parallel\": 4\n}\n<\/code><\/pre>\n<p>\u201cpbm schedule &#8211;config \/etc\/pbs\/jobs\/{jobname}.json\u201d komutu, plan\u0131 kaydeder.  <\/p>\n<h3 id=\"bolum-7\">3. Offsite Senkronizasyon<\/h3>\n<p>Offsite senkronizasyon i\u00e7in, hedef sunucuya eri\u015fim sa\u011flayan SSH anahtar\u0131 gereklidir.<br \/>\nPBS, \u201cpbs:\/\/remote:\/storage2\u201d \u015feklinde hedef depolama adresi tan\u0131mlar; bu adres, TLS \u00fczerinden \u015fifrelenir.<br \/>\n\u201cpbm sync &#8211;node {node} &#8211;job {jobname} &#8211;remote remote:storage2\u201d komutu, snapshot\u2019lar\u0131 uzaktaki depolamaya kopyalar.  <\/p>\n<h3 id=\"bolum-8\">4. Manuel Ba\u015flatma ve Servis<\/h3>\n<p>Yedekleme s\u00fcrecini manuel olarak ba\u015flatmak i\u00e7in, \u201cpbm backup &#8211;node {node} {vmid} &#8211;remote remote:storage2\u201d kullan\u0131l\u0131r.<br \/>\nPBS\u2019yi otomatik olarak ba\u015flatmak i\u00e7in, sistem servis dosyas\u0131n\u0131 \u201csystemctl enable &#8211;now pbs.service\u201d ile etkinle\u015ftirirsiniz.  <\/p>\n<h3 id=\"bolum-9\">5. \u00d6rnek Snapshot Komutu<\/h3>\n<p>Snapshot\u2019\u0131n bir \u00f6rne\u011fi i\u00e7in, \u201cpbm backup &#8211;node proxmox1 101 &#8211;storage pbs:\/\/storage1 &#8211;remote remote:storage2\u201d komutunu \u00e7al\u0131\u015ft\u0131rabilirsiniz.  <\/p>\n<h3 id=\"bolum-10\">6. Geri Y\u00fckleme<\/h3>\n<p>Snapshot\u2019\u0131 geri y\u00fcklemek i\u00e7in, \u201cpbm restore &#8211;node {node} &#8211;vmid {vmid} &#8211;backup-id {id}\u201d komutu kullan\u0131l\u0131r.<br \/>\n\u201cpbm restore &#8211;node proxmox1 &#8211;vmid 101 &#8211;backup-id 2023-08-15T02-00-00Z\u201d \u00f6rne\u011fi, 15\u202fA\u011fustos\u202f2023 snapshot\u2019\u0131n\u0131 geri y\u00fckler.  <\/p>\n<h3 id=\"bolum-11\">7. Log ve \u0130zleme<\/h3>\n<p>PBS loglar\u0131, \/var\/log\/pbs\/ i\u00e7inde \u201cpbs.log\u201d dosyas\u0131nda tutulur, burada hatalar ve ba\u015far\u0131 mesajlar\u0131 bulunur.<br \/>\nGeri y\u00fckleme sonras\u0131, VM\u2019nin a\u011f ayarlar\u0131n\u0131 kontrol etmek \u00f6nemlidir; IP de\u011fi\u015fiklikleri, DHCP ile otomatik olarak g\u00fcncellenir.  <\/p>\n<h3 id=\"bolum-12\">8. G\u00fcncelleme ve Test<\/h3>\n<p>PBS&#8217;yi g\u00fcncel tutmak i\u00e7in, \u201capt update &amp;&amp; apt upgrade pbs-server\u201d komutu kullan\u0131labilir; s\u00fcr\u00fcm uyumsuzluklar\u0131 giderilir.<br \/>\n\u201cpbm restore &#8211;test\u201d komutu, test ortam\u0131nda geri y\u00fcklemeyi ger\u00e7ekle\u015ftirir, ger\u00e7ek veri kayb\u0131 olmadan do\u011frulama sa\u011flar.  <\/p>\n<pre><code class=\"language-bash\"># Snapshot olu\u015fturma ve offsite senkronizasyon \u00f6rne\u011fi\npbm backup --node proxmox1 --vmid 101 --storage pbs:\/\/storage1\npbm sync --node proxmox1 --vmid 101 --remote remote:storage2\n<\/code><\/pre>\n<h3 id=\"bolum-13\">Y\u00f6ntem veya Ara\u00e7 Kar\u015f\u0131la\u015ft\u0131rma Tablosu<\/h3>\n<table>\n<thead>\n<tr>\n<th>\u00d6zellik<\/th>\n<th>Snapshot (Proxmox)<\/th>\n<th>Proxmox Backup Server (PBS)<\/th>\n<th>Rclone (Genel)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Snapshot olu\u015fturma<\/td>\n<td>Yerel snapshot, anl\u0131k g\u00f6r\u00fcnt\u00fc<\/td>\n<td>PBS ile snapshot olu\u015fturma ve depolama<\/td>\n<td>Dosya\u2011tabanl\u0131, do\u011frudan dosya kopyalama<\/td>\n<\/tr>\n<tr>\n<td>Veri s\u0131k\u0131\u015ft\u0131rma<\/td>\n<td>Varsay\u0131lan s\u0131k\u0131\u015ft\u0131rma yok<\/td>\n<td>gzip, lz4, zstd se\u00e7enekleri<\/td>\n<td>LZ4, ZSTD, LZO<\/td>\n<\/tr>\n<tr>\n<td>Dedup<\/td>\n<td>Yok<\/td>\n<td>Dedup (blok bazl\u0131)<\/td>\n<td>Opsiyonel, dosya bazl\u0131<\/td>\n<\/tr>\n<tr>\n<td>\u015eifreleme<\/td>\n<td>\u015eifreleme yok<\/td>\n<td>AES\u2011256, TLS 1.3<\/td>\n<td>Opsiyonel, S3 S3-encrypt<\/td>\n<\/tr>\n<tr>\n<td>Offsite senkronizasyon<\/td>\n<td>Manuel, rsync\/SSH<\/td>\n<td>PBS sync, TLS, SSH anahtar\u0131<\/td>\n<td>S3, FTP, WebDAV, vb.<\/td>\n<\/tr>\n<tr>\n<td>Y\u00f6netim aray\u00fcz\u00fc<\/td>\n<td>CLI \/ GUI<\/td>\n<td>Web UI, CLI<\/td>\n<td>CLI<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"bolum-14\">Risk ve Rollback Noktas\u0131 Tablosu<\/h3>\n<table>\n<thead>\n<tr>\n<th>Risk<\/th>\n<th>\u00d6nlem<\/th>\n<th>Rollback Prosed\u00fcr\u00fc<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Snapshot ba\u015far\u0131s\u0131zl\u0131\u011f\u0131<\/td>\n<td>Do\u011frudan canl\u0131 VM\u2019i durdurmay\u0131n, \u201cpbm backup &#8211;node &#8230;\u201d yeniden \u00e7al\u0131\u015ft\u0131r\u0131n<\/td>\n<td>pbm restore \u2013node \u2026 \u2013vmid \u2026 \u2013backup-id <\/td>\n<\/tr>\n<tr>\n<td>Offsite senkronizasyon hatas\u0131<\/td>\n<td>A\u011f ba\u011flant\u0131s\u0131n\u0131 test edin, SSH anahtar\u0131n\u0131 do\u011frulay\u0131n<\/td>\n<td>Geri y\u00fckleme testini \u00e7al\u0131\u015ft\u0131r\u0131n, hatal\u0131 dosyay\u0131 silin<\/td>\n<\/tr>\n<tr>\n<td>\u015eifreleme anahtar\u0131 kayb\u0131<\/td>\n<td>Anahtar yedekini g\u00fcvenli yerde saklay\u0131n<\/td>\n<td>Anahtar\u0131 yeniden olu\u015fturun, pbm restore \u2013encrypt\u2011key \u2026<\/td>\n<\/tr>\n<tr>\n<td>Disk alan\u0131 t\u00fckendi<\/td>\n<td>Yedeklemeyi b\u00f6l\u00fcmlere ay\u0131r\u0131n, eski snapshotlar\u0131 silin<\/td>\n<td>pbm prune \u2013days 30<\/td>\n<\/tr>\n<tr>\n<td>Hizmet kapanmas\u0131<\/td>\n<td>Servis durumu izleyin, otomatik yeniden ba\u015flatma kurallar\u0131<\/td>\n<td>systemctl restart pbs.service<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"bolum-15\">Snapshot ve Offsite Yedekleme Kontrol Listesi<\/h3>\n<ul>\n<li>\u2610 Proxmox VE s\u00fcr\u00fcm\u00fc 7.0+ do\u011fruland\u0131<\/li>\n<li>\u2610 PBS 4.0+ kuruldu ve yap\u0131land\u0131r\u0131ld\u0131<\/li>\n<li>\u2610 SSH anahtar\u0131 hedef sunucuya eklendi<\/li>\n<li>\u2610 Snapshot job JSON dosyas\u0131 olu\u015fturuldu<\/li>\n<li>\u2610 Cron job 02:00\u2019de \u00e7al\u0131\u015facak \u015fekilde ayarland\u0131<\/li>\n<li>\u2610 Offsite senkronizasyon test edildi<\/li>\n<li>\u2610 Log rotasyonu 7 g\u00fcn i\u00e7in ayarland\u0131<\/li>\n<li>\u2610 Yedekleme performans\u0131 izleniyor<\/li>\n<li>\u2610 Yedekleme testleri ayl\u0131k olarak yap\u0131ld\u0131<\/li>\n<\/ul>\n<h2 id=\"bolum-16\">Sorun Giderme ve Rollback<\/h2>\n<p>Snapshot al\u0131n\u0131rken, \u201cpbm backup\u201d komutu 101 koduyla hata verirse, log dosyalar\u0131n\u0131 kontrol edin.<br \/>\n101 hatas\u0131 genellikle \u201cdisk dolu\u201d veya \u201cyetkisiz eri\u015fim\u201d ile ilgilidir; disk alan\u0131n\u0131 ve izinleri do\u011frulay\u0131n.  <\/p>\n<p>Offsite senkronizasyon s\u0131ras\u0131nda, \u201cconnection timeout\u201d veya \u201cTLS handshake error\u201d g\u00f6r\u00fcl\u00fcyorsa, hedef sunucunun firewall\u2019u ve TLS sertifikas\u0131 ge\u00e7erli mi kontrol edin.  <\/p>\n<p>PBS\u2019nin \u201cpbm monitor\u201d komutu, aktif i\u015flemleri g\u00f6sterir; bu komutla \u201cblocked\u201d durumdaki i\u015flemleri tespit edin.  <\/p>\n<p>Rollback i\u00e7in, pbm restore komutu ile ayn\u0131 VM\u2019ye ait en son ge\u00e7erli snapshot\u2019\u0131 geri y\u00fckleyin.<br \/>\n\u00d6rne\u011fin, \u201cpbm restore &#8211;node proxmox1 &#8211;vmid 101 &#8211;backup-id 2023-09-10T02-00-00Z\u201d komutu ile 10\u202fEyl\u00fcl snapshot\u2019\u0131n\u0131 geri y\u00fckleyebilirsiniz.  <\/p>\n<p>E\u011fer geri y\u00fckleme s\u0131ras\u0131nda dosya bozuklu\u011fu tespit edilirse, \u201cpbm restore &#8211;test\u201d ile \u00f6n test ger\u00e7ekle\u015ftirin; ba\u015far\u0131s\u0131zl\u0131k durumunda, yedeklemi yeniden olu\u015fturun.  <\/p>\n<p>PBS loglar\u0131, \u201cpbs.log\u201d i\u00e7inde \u201cerror\u201d kelimesiyle aray\u0131n; hatan\u0131n k\u00f6kenini bulmak i\u00e7in \u201c-v\u201d ile ayr\u0131nt\u0131l\u0131 \u00e7\u0131kt\u0131 al\u0131n.  <\/p>\n<h2 id=\"bolum-17\">Performans ve G\u00fcvenlik Optimizasyonu<\/h2>\n<p>Veri s\u0131k\u0131\u015ft\u0131rma seviyesini 9\u2019a \u00e7\u0131kararak, dosya boyutunu %30 azaltabilirsiniz; ancak CPU kullan\u0131m\u0131n\u0131n artaca\u011f\u0131n\u0131 g\u00f6z \u00f6n\u00fcnde bulundurun.  <\/p>\n<p>Dedup, ayn\u0131 bloklar\u0131 tek kopya tutarak depolama maliyetini azalt\u0131r; bu \u00f6zelli\u011fi \u201cdedup=on\u201d ile etkinle\u015ftirin.  <\/p>\n<p>Offsite senkronizasyon i\u00e7in, hedef sunucuya 2\u202fGbps ba\u011flant\u0131 kullanarak transfer s\u00fcresini k\u0131saltabilirsiniz.  <\/p>\n<p>PBS\u2019yi HTTPS \u00fczerinden 4443 portunda dinlemek i\u00e7in firewall\u2019da bu portu a\u00e7\u0131n, TLS 1.3 kullan\u0131m\u0131 zorunlu k\u0131l\u0131n.  <\/p>\n<p>Yedekleme s\u00fcrecini izlemek i\u00e7in, Prometheus + Grafana ile PBS metriklerini g\u00f6rselle\u015ftirin.  <\/p>\n<p>Yedekleme testlerini otomatikle\u015ftirerek, her ay sonunda \u201cpbm restore &#8211;test\u201d komutunu \u00e7al\u0131\u015ft\u0131r\u0131n.  <\/p>\n<h2 id=\"bolum-18\">Sonu\u00e7 ve H\u0131zl\u0131 Tekrar<\/h2>\n<p>Proxmox VE snapshot ile offsite yedekleme, kritik veri kayb\u0131n\u0131 en aza indirir ve i\u015f s\u00fcreklili\u011fini sa\u011flar.<br \/>\nPBS, snapshot y\u00f6netimini, s\u0131k\u0131\u015ft\u0131rmay\u0131, dedup\u2019i ve \u015fifrelemeyi tek \u00e7at\u0131 alt\u0131nda toplar.<br \/>\nKurulumdan sonra, snapshot olu\u015fturma, offsite senkronizasyon ve geri y\u00fckleme ad\u0131mlar\u0131n\u0131 test edin.<br \/>\nRollback prosed\u00fcrlerini belgeleyin ve loglar\u0131 izleyin.<br \/>\nAyr\u0131ca, periyodik testler ve performans izleme ile sistemi g\u00fcvenli ve verimli tutun.<br \/>\nBu rehber, ad\u0131m ad\u0131m yap\u0131land\u0131rma, kontrol listesi ve sorun giderme yollar\u0131 sunarak, operator odakl\u0131 bir yakla\u015f\u0131m sa\u011flar.  <\/p>\n<h2 id=\"bolum-19\">S\u0131k Sorulan Sorular<\/h2>\n<p><strong>Proxmox VE snapshot ve offsite yedekleme plan\u0131 ne zaman mant\u0131kl\u0131d\u0131r?<\/strong><br \/>\n\u0130\u015f s\u00fcreklili\u011fi i\u00e7in kritik veri depolayan bir ortamda, g\u00fcnl\u00fck snapshot ve haftal\u0131k offsite senkronizasyon \u00f6nerilir.<br \/>\nOrtam\u0131n veri b\u00fcy\u00fckl\u00fc\u011f\u00fcne ve de\u011fi\u015fim h\u0131z\u0131na g\u00f6re s\u0131kl\u0131k ayarlanabilir.<\/p>\n<p><strong>Proxmox VE snapshot ve offsite yedekleme plan\u0131 uygularken en yayg\u0131n hata nedir?<\/strong><br \/>\nGenellikle, SSH anahtar\u0131 veya TLS sertifikas\u0131 hatalar\u0131, snapshot s\u00fcresinin \u00e7ok uzun olmas\u0131 ve disk alan\u0131 t\u00fckendi\u011fi durumlar g\u00f6r\u00fcl\u00fcr.<br \/>\n\u00d6nlemler aras\u0131nda, anahtarlar\u0131 kontrol etmek ve disk alan\u0131n\u0131 izlemek yer al\u0131r.<\/p>\n<p><strong>Proxmox VE snapshot ve offsite yedekleme plan\u0131 sonras\u0131 hangi kontrol ad\u0131mlar\u0131 yap\u0131lmal\u0131?<\/strong><br \/>\nYedekleme g\u00fcnl\u00fcklerini inceleyin, \u201cpbm restore &#8211;test\u201d ile geri y\u00fckleme testi yap\u0131n, veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n ve log rotasyonunu kontrol edin.  <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Proxmox VE yedekleme plani ile 7 ad\u0131mda offsite snapshot y\u00f6netimi, rollback, g\u00fcvenlik kontrol\u00fc ve ad\u0131m ad\u0131m yap\u0131land\u0131rma rehberi, test senaryolar\u0131 ve log analiz<\/p>\n","protected":false},"author":1,"featured_media":562,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Proxmox VE yedekleme plani: 2026 Pratik Rehber","rank_math_description":"Proxmox VE yedekleme plani ile 7 ad\u0131mda offsite snapshot y\u00f6netimi, rollback, g\u00fcvenlik kontrol\u00fc ve ad\u0131m ad\u0131m yap\u0131land\u0131rma rehberi, test senaryolar\u0131 ve log analiz","rank_math_focus_keyword":"Proxmox VE yedekleme plani","footnotes":""},"categories":[1],"tags":[195,194,190,137,196,191],"class_list":["post-563","post","type-post","status-publish","format-standard","has-post-thumbnail","category-genel","tag-offsite-backup","tag-proxmox-ve","tag-proxmox-ve-yedekleme-plani","tag-security","tag-small-business","tag-snapshot"],"_links":{"self":[{"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/posts\/563","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/comments?post=563"}],"version-history":[{"count":1,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/posts\/563\/revisions"}],"predecessor-version":[{"id":565,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/posts\/563\/revisions\/565"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/media\/562"}],"wp:attachment":[{"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/media?parent=563"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/categories?post=563"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m4.ist\/index.php\/wp-json\/wp\/v2\/tags?post=563"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}