[{"id":416,"title":"Microsoft Entra Connect Sync \u0130\u00e7in Kritik Uyar\u0131","content":"<p data-path-to-node=\"2\"><strong data-path-to-node=\"2\" data-index-in-node=\"0\">Microsoft Entra Connect Sync \u0130&ccedil;in Kritik Uyar\u0131: 30 Eyl&uuml;l 2026&rsquo;ya Kadar Y&uuml;kseltme Zorunlu!<\/strong><\/p>\n<p data-path-to-node=\"3\">Sistem y&ouml;neticilerinin ve BT ekiplerinin dikkatine: Microsoft Entra Connect Sync kullan\u0131yorsan\u0131z, takvimlerinize <strong data-path-to-node=\"3\" data-index-in-node=\"113\">30 Eyl&uuml;l 2026<\/strong> tarihini mutlaka kaydetmeniz gerekiyor. Bu tarihten itibaren, <strong data-path-to-node=\"3\" data-index-in-node=\"189\">2.5.79.0<\/strong> s&uuml;r&uuml;m&uuml;nden daha eski bir versiyon &ccedil;al\u0131\u015ft\u0131ran t&uuml;m senkronizasyon hizmetleri <strong data-path-to-node=\"3\" data-index-in-node=\"273\">&ccedil;al\u0131\u015fmay\u0131 tamamen durduracakt\u0131r<\/strong>.<\/p>\n<p data-path-to-node=\"4\">Microsoft, altyap\u0131s\u0131n\u0131 g&uuml;&ccedil;lendirmek ad\u0131na May\u0131s 2025&rsquo;te arka u&ccedil; hizmetlerinde kapsaml\u0131 bir de\u011fi\u015fikli\u011fe gitti ve bu yeni yap\u0131y\u0131 destekleyen 2.5.79.0 s&uuml;r&uuml;m&uuml;n&uuml; yay\u0131nlad\u0131. Olas\u0131 bir hizmet kesintisinin ve kimlik do\u011frulama sorunlar\u0131n\u0131n &ouml;n&uuml;ne ge&ccedil;mek i&ccedil;in ortam\u0131n\u0131z\u0131 bu tarihten &ouml;nce g&uuml;ncellemeniz \u015fart.<\/p>\n<h3 data-path-to-node=\"5\">Neden Y&uuml;kseltmelisiniz?<\/h3>\n<ul data-path-to-node=\"6\">\n<li>\n<p data-path-to-node=\"6,0,0\"><strong data-path-to-node=\"6,0,0\" data-index-in-node=\"0\">Servis Kesintisi Riski:<\/strong> Son tarihe kadar gerekli y&uuml;kseltmeyi yapmazsan\u0131z, senkronizasyon hizmetleriniz g&uuml;ncellenene kadar <strong data-path-to-node=\"6,0,0\" data-index-in-node=\"122\">BA\u015eARISIZ<\/strong> olacak ve \u015firket i&ccedil;i (on-premises) Active Directory ile bulut aras\u0131ndaki veri ak\u0131\u015f\u0131 duracakt\u0131r.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"6,1,0\"><strong data-path-to-node=\"6,1,0\" data-index-in-node=\"0\">G&uuml;venlik ve \u0130deal S&uuml;r&uuml;m:<\/strong> Microsoft, yaln\u0131zca minimum gereksinim olan 2.5.79.0 s&uuml;r&uuml;m&uuml;ne ge&ccedil;mek yerine, en g&uuml;ncel g&uuml;venlik d&uuml;zeltmelerini i&ccedil;eren ve &ouml;nerilen <strong data-path-to-node=\"6,1,0\" data-index-in-node=\"155\">2.6.84.0<\/strong> s&uuml;r&uuml;m&uuml;ne y&uuml;kseltmenizi &ouml;nemle tavsiye eder.<\/p>\n<\/li>\n<\/ul>\n<h3 data-path-to-node=\"7\">Y&uuml;kseltme &Ouml;ncesi Dikkat Edilmesi Gerekenler<\/h3>\n<ol start=\"1\" data-path-to-node=\"8\">\n<li>\n<p data-path-to-node=\"8,0,0\"><strong data-path-to-node=\"8,0,0\" data-index-in-node=\"0\">Kurulum Dosyas\u0131:<\/strong> Microsoft Entra Connect Sync <code data-path-to-node=\"8,0,0\" data-index-in-node=\"46\">.msi<\/code> kurulum dosyas\u0131na yaln\u0131zca <strong data-path-to-node=\"8,0,0\" data-index-in-node=\"78\">Microsoft Entra Y&ouml;netim Merkezi (Entra Admin Center)<\/strong> &uuml;zerinden eri\u015febilirsiniz.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"8,1,0\"><strong data-path-to-node=\"8,1,0\" data-index-in-node=\"0\">Sistem Gereksinimleri:<\/strong> Sunucunuzun en az <strong data-path-to-node=\"8,1,0\" data-index-in-node=\"41\">.NET Framework 4.7.2<\/strong> ve <strong data-path-to-node=\"8,1,0\" data-index-in-node=\"65\">TLS 1.2<\/strong> protokol&uuml;n&uuml; destekledi\u011finden emin olun.<\/p>\n<\/li>\n<\/ol>\n<p data-path-to-node=\"9\">Kesinti ya\u015famamak ad\u0131na planlaman\u0131z\u0131 \u015fimdiden yapman\u0131z\u0131 ve sunucular\u0131n\u0131z\u0131 en g&uuml;ncel s&uuml;r&uuml;me y&uuml;kseltmenizi &ouml;neririz.<\/p>\n<p data-path-to-node=\"9\">Kaynak : <a href=\"https:\/\/learn.microsoft.com\/en-us\/entra\/identity\/hybrid\/connect\/reference-connect-version-history\">https:\/\/learn.microsoft.com\/en-us\/entra\/identity\/hybrid\/connect\/reference-connect-version-history<\/a><\/p>\n<p data-path-to-node=\"9\">&nbsp;<\/p>","excerpt":"Microsoft Entra Connect Sync \u0130\u00e7in Kritik Uyar\u0131: 30 Eyl\u00fcl 2026\u2019ya Kadar Y\u00fckseltme Zorunlu!\n\nSistem y\u00f6neticilerinin ve BT ekiplerinin dikkatine: Microsoft Entra Connect Sync kullan\u0131yorsan\u0131z, takvimlerinize 30 Eyl\u00fcl 2026 tarihini mutlaka kaydetmeniz gerekiyor. Bu tarihten itibaren, 2.5.79.0 s\u00fcr\u00fcm\u00fcnden daha eski bir versiyon \u00e7al\u0131\u015ft\u0131ran t\u00fcm senkronizasyon hizmetleri \u00e7al\u0131\u015fmay\u0131 tamamen durduracakt\u0131r.","created_at":"2026-09-01 17:26:44","updated_at":"2026-09-23 11:52:24","category_id":6,"view_count":47,"reading_time":2,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2026-09-01 14:26:44","featured_image":"\/uploads\/images\/2026\/09\/6a96e08fbea34_1788272783.jpg","slug":"microsoft-entra-connect-sync-icin-kritik-uyari","category_name":"Sistem","category_slug":"sistem","category_color":"#3b82f6"},{"id":414,"title":"Kurtar\u0131lamaz\" Denen RAID'i S\u0131f\u0131rdan Geri Kurmak","content":"<h1>Metadata's\u0131z RAID ve Yedek Kurtarma: Mimari ve Uygulama Notlar\u0131<\/h1>\n<p>Bu yaz\u0131, index\/journal\/dosya sistemi hi&ccedil;birinin kalmad\u0131\u011f\u0131 bir Veeam kurtarma vakas\u0131nda yazd\u0131\u011f\u0131m iki arac\u0131n teknik i&ccedil; yap\u0131s\u0131n\u0131 ele al\u0131yor. Ama&ccedil; hikaye anlatmak de\u011fil; kararlar\u0131n <em>neden<\/em> &ouml;yle al\u0131nd\u0131\u011f\u0131n\u0131 ve uygulaman\u0131n nas\u0131l kuruldu\u011funu g&ouml;stermek.<\/p>\n<h2>Problem Tan\u0131m\u0131<\/h2>\n<p>Girdi durumu:<\/p>\n<ul>\n<li>RAID metadata's\u0131 kay\u0131p, &uuml;st&uuml;ne yanl\u0131\u015f parametrelerle (muhtemelen yanl\u0131\u015f stripe size \/ disk s\u0131ras\u0131 ile) bir \"rebuild\" denemesi yap\u0131lm\u0131\u015f &mdash; yani &uuml;st &uuml;ste iki bozulma katman\u0131 var.<\/li>\n<li>Dizideki bir k\u0131s\u0131m disk Windows'ta h\u0131zl\u0131 formatlanm\u0131\u015f, ard\u0131ndan &uuml;zerine yeni veri yaz\u0131lm\u0131\u015f.<\/li>\n<li>Hedef veri bir Veeam backup repository'si (.vbk\/.vib zinciri), ama repository'nin kendi index\/metadata katman\u0131 da kay\u0131p.<\/li>\n<\/ul>\n<p>\u0130ki ayr\u0131 problem s\u0131n\u0131f\u0131 var burada ve birbirine kenetli: <strong>(1) blind RAID reconstruction<\/strong> &mdash; hi&ccedil;bir &uuml;st seviye metadata olmadan disk dizisinin geometrisini tespit etmek, <strong>(2) metadata's\u0131z i&ccedil;erik carving<\/strong> &mdash; dosya sistemi ya da backup index'i olmadan, ham bloklardan orijinal yedek yap\u0131s\u0131n\u0131 geri kurmak.<\/p>\n<h2>K\u0131s\u0131m 1: RAID Geometri Tespiti<\/h2>\n<h3>Neden mevcut ara&ccedil;lar yetmedi<\/h3>\n<p>PC-3000 ve benzerlerinin RAID reconstruction mod&uuml;lleri temelde \u015funu yapar: disk ba\u015f\u0131na belirli offsetlerde dosya sistemi imzalar\u0131 arar (NTFS <code>$MFT<\/code> kay\u0131tlar\u0131n\u0131n periyodikli\u011fi, FAT tablo tekrarlar\u0131 vb.), farkl\u0131 stripe size \/ disk s\u0131ras\u0131 \/ rotasyon kombinasyonlar\u0131n\u0131 dener, hangi kombinasyonda bu imzalar \"tutarl\u0131\" bir \u015fekilde diziliyor diye bakar. Bu, istatistiksel bir arama uzay\u0131 problemi &mdash; N disk i&ccedil;in disk s\u0131ras\u0131 perm&uuml;tasyonu &times; olas\u0131 stripe size seti &times; rotasyon y&ouml;n&uuml; kombinasyonlar\u0131n\u0131 taray\u0131p bir \"confidence score\" ile en iyi aday\u0131 se&ccedil;iyor.<\/p>\n<p>Bu y&ouml;ntemin temel varsay\u0131m\u0131: <strong>disk &uuml;zerindeki veri deseni bozulmam\u0131\u015f<\/strong>. Benim vakamda bu varsay\u0131m ge&ccedil;ersizdi &mdash; baz\u0131 diskler formatlan\u0131p &uuml;zerine yaz\u0131lm\u0131\u015ft\u0131, yani &uuml;zerlerindeki \"desen\" zaten farkl\u0131 bir dosya sistemi kurulumuna aitti. Algoritma orada tutarl\u0131 bir sonu&ccedil; bulam\u0131yor, &ccedil;&uuml;nk&uuml; arad\u0131\u011f\u0131 imzalar ger&ccedil;ekten yok.<\/p>\n<h3>Yakla\u015f\u0131m: Desen aramak yerine iz okumak<\/h3>\n<p>Kendi arac\u0131mda stratejiyi tersine &ccedil;evirdim: dosya sistemi i&ccedil;eri\u011fine bak\u0131p geometriyi <em>tahmin etmek<\/em> yerine, RAID controller'lar\u0131n disk &uuml;zerinde b\u0131rakt\u0131\u011f\u0131 <strong>kendi metadata art\u0131klar\u0131n\u0131<\/strong> do\u011frudan okumak.<\/p>\n<p>Pratikte bu \u015fu katmanlardan olu\u015fuyor:<\/p>\n<p><strong>a) WWN tabanl\u0131 disk kimliklendirme<\/strong><\/p>\n<p>Her fiziksel diskten WWN (World Wide Name) okunuyor ve bu, dizideki mant\u0131ksal disk pozisyonuyla e\u015fle\u015ftiriliyor. RAID controller'lar\u0131n &ccedil;o\u011fu (LSI\/Avago, Adaptec, Intel RST) config bloklar\u0131nda disk kimliklerini saklar; bu bloklar formatla silinmemi\u015fse (genelde disk sonunda ayr\u0131 bir reserved alanda dururlar) buradan disk s\u0131ras\u0131 do\u011frudan okunabiliyor. Go taraf\u0131nda bu, <code>\/dev\/sdX<\/code> &uuml;zerinde <code>ioctl<\/code> ile SCSI INQUIRY komutu (page 0x83) &ccedil;a\u011f\u0131rarak WWN &ccedil;ekmek \u015feklinde uyguland\u0131 &mdash; &uuml;&ccedil;&uuml;nc&uuml; parti ba\u011f\u0131ml\u0131l\u0131k yok, do\u011frudan syscall seviyesinde.<\/p>\n<p><strong>b) Config art\u0131klar\u0131ndan stripe\/parity geometrisi<\/strong><\/p>\n<p>Disklerin controller-reserved alanlar\u0131nda (genelde disk sonunda, birka&ccedil; MB'l\u0131k bir b&ouml;lge) eski RAID config yap\u0131lar\u0131 kal\u0131nt\u0131 halinde duruyordu. Buradan stripe size ve parity rotasyon y&ouml;n&uuml; do\u011frudan parse edildi &mdash; tahmin de\u011fil, kay\u0131t okuma. Format i\u015flemi genelde bu alanlara dokunmuyor &ccedil;&uuml;nk&uuml; i\u015fletim sistemi bu sekt&ouml;rleri \"kullan\u0131labilir alan\" olarak g&ouml;rm&uuml;yor.<\/p>\n<p><strong>c) COW katman\u0131 &mdash; sanal montaj<\/strong><\/p>\n<p>Bu, mimarinin can al\u0131c\u0131 noktas\u0131. Elimde formatlan\u0131p &uuml;zerine yaz\u0131lm\u0131\u015f diskler oldu\u011fu i&ccedil;in, herhangi bir yanl\u0131\u015f geometri denemesi ger&ccedil;ek diske yaz\u0131l\u0131rsa geri d&ouml;n&uuml;\u015f&uuml; olmayan bir hasar riski var. Bu y&uuml;zden RAID'i hi&ccedil;bir zaman fiziksel diske yazmadan kurdum:<\/p>\n<ul>\n<li>Her fiziksel disk salt-okunur (<code>O_RDONLY<\/code>) a&ccedil;\u0131l\u0131yor.<\/li>\n<li>&Uuml;zerine bir sparse overlay dosyas\u0131 (fiziksel disk ba\u015f\u0131na bir \"diff\" dosyas\u0131) tan\u0131mlan\u0131yor; okunan her sekt&ouml;r &ouml;nce overlay'de var m\u0131 diye kontrol ediliyor, yoksa fiziksel diskten okunup overlay'e gerekti\u011finde yaz\u0131l\u0131yor (yaln\u0131zca RAID kurulum s&uuml;recinin kendi &uuml;retti\u011fi meta-yaz\u0131lar overlay'e gidiyor, kullan\u0131c\u0131 verisine asla dokunulmuyor).<\/li>\n<li>Bu sanal katman, bir NBD (Network Block Device) server olarak expose ediliyor. Go'da bu, NBD protokol&uuml;n&uuml; (basit bir TCP &uuml;zerinden request\/reply &mdash; <code>NBD_CMD_READ<\/code>, <code>NBD_CMD_WRITE<\/code>, <code>NBD_CMD_DISC<\/code>) do\u011frudan implemente ederek yap\u0131ld\u0131; harici bir ba\u011f\u0131ml\u0131l\u0131k gerekmedi.<\/li>\n<li>Linux taraf\u0131nda <code>nbd-client<\/code> ile bu sanal cihaz <code>\/dev\/nbdX<\/code> olarak mount edilip &uuml;zerinde normal bir blok cihaz\u0131 gibi &ccedil;al\u0131\u015f\u0131labiliyor &mdash; <code>mdadm --assemble<\/code>, loop mount, hatta do\u011frudan dosya sistemi recovery ara&ccedil;lar\u0131 bu sanal cihaza kar\u015f\u0131 &ccedil;al\u0131\u015ft\u0131r\u0131labiliyor.<\/li>\n<\/ul>\n<p>Bunun getirdi\u011fi pratik fayda: onlarca farkl\u0131 stripe size \/ disk s\u0131ras\u0131 \/ rotasyon kombinasyonunu, her denemede ger&ccedil;ek diske hi&ccedil; dokunmadan test edebildim. Yanl\u0131\u015f bir kombinasyon sadece \"bo\u015f\" ya da tutars\u0131z bir dosya sistemi g&ouml;r&uuml;nt&uuml;s&uuml; veriyordu, hasar vermiyordu.<\/p>\n<p><strong>d) Formatlanm\u0131\u015f disklerin toparlanmas\u0131<\/strong><\/p>\n<p>Format (&ouml;zellikle h\u0131zl\u0131 format) diski s\u0131f\u0131rlamaz; yaln\u0131zca dosya sistemi metadata yap\u0131lar\u0131n\u0131 (MFT, boot sector, cluster bitmap) yeniden yazar. Kullan\u0131c\u0131 verisinin b&uuml;y&uuml;k k\u0131sm\u0131, yeni format taraf\u0131ndan hen&uuml;z &uuml;zerine yaz\u0131lmam\u0131\u015f cluster'larda h&acirc;l&acirc; duruyordu. Bu diskler RAID'e COW katman\u0131 &uuml;zerinden dahil edildikten sonra, RAID seviyesinde toparlanan stripe'lar zaten eski veriyi i&ccedil;eriyordu &mdash; &ccedil;&uuml;nk&uuml; format sadece dosya sistemi seviyesinde bir i\u015flemdi, RAID'in stripe d&uuml;zenini de\u011fi\u015ftirmemi\u015fti.<\/p>\n<h2>K\u0131s\u0131m 2: Metadata's\u0131z Veeam Blok Carving<\/h2>\n<p>RAID toparland\u0131ktan sonra elimde tutarl\u0131, okunabilir bir ham disk imaj\u0131 vard\u0131 &mdash; ama i&ccedil;inde ne bir dosya sistemi, ne &ccedil;al\u0131\u015fan bir .vbk, ne index, ne journal.<\/p>\n<h3>Veeam blok yap\u0131s\u0131na dair g&ouml;zlemler<\/h3>\n<p>Veeam backup dosyalar\u0131 (.vbk\/.vib) i&ccedil;eride sabit veya de\u011fi\u015fken boyutlu \"extent\" bloklar\u0131ndan olu\u015fur; her blok genelde bir header\/checksum ile ba\u015flar ve s\u0131k\u0131\u015ft\u0131rma (genelde zlib\/lz4 varyantlar\u0131) uygulanm\u0131\u015f olabilir. Format s&uuml;r&uuml;m&uuml;ne g&ouml;re detaylar de\u011fi\u015fir, ama pratikte her blo\u011fun kendi i&ccedil;inde b&uuml;t&uuml;nl&uuml;k kontrol&uuml;ne izin veren bir imza\/checksum alan\u0131 var. Index kaybolsa bile bu, bloklar\u0131 tek tek tan\u0131may\u0131 m&uuml;mk&uuml;n k\u0131l\u0131yor.<\/p>\n<h3>Carving stratejisi<\/h3>\n<p>Ara&ccedil; \u015fu ak\u0131\u015fla &ccedil;al\u0131\u015f\u0131yor:<\/p>\n<ol>\n<li><strong>Ham tarama<\/strong>: Disk imaj\u0131 sabit boyutlu pencerelerle (chunk) taran\u0131yor, her pencerede bilinen blok header imzalar\u0131 aran\u0131yor.<\/li>\n<li><strong>Blok do\u011frulama<\/strong>: Bir imza bulundu\u011funda, blok boyutu header'dan okunup checksum ile i&ccedil;erik do\u011frulan\u0131yor. Checksum tutmuyorsa blok \"bozuk\/k\u0131smi\" olarak i\u015faretleniyor, at\u0131lm\u0131yor &mdash; &ccedil;&uuml;nk&uuml; ileride ba\u015fka bir kaynaktan tamamlanabilir.<\/li>\n<li><strong>Blok haritas\u0131 (block map) olu\u015fturma<\/strong>: Bulunan her blok, orijinal VM disk offset'ine (blok header'\u0131nda genelde bu bilgi de ta\u015f\u0131n\u0131r) g&ouml;re bir haritaya yerle\u015ftiriliyor. Bu harita asl\u0131nda kaybolan index'in yeniden in\u015fas\u0131.<\/li>\n<li><strong>&Ccedil;apraz yedekten tamamlama<\/strong>: Bir offset i&ccedil;in hi&ccedil;bir sa\u011flam blok bulunamad\u0131\u011f\u0131nda, ayn\u0131 VM'in farkl\u0131 bir restore point'ine ait ikinci bir ham taramadan ayn\u0131 offsete kar\u015f\u0131l\u0131k gelen blok aran\u0131yor. Incremental backup yap\u0131s\u0131 gere\u011fi bloklar aras\u0131nda y&uuml;ksek &ouml;rt&uuml;\u015fme var, bu da eksik par&ccedil;alar\u0131n b&uuml;y&uuml;k k\u0131sm\u0131n\u0131n ba\u015fka bir yedekte sa\u011flam halde bulunmas\u0131n\u0131 sa\u011fl\u0131yor.<\/li>\n<li><strong>Yeniden birle\u015ftirme (reassembly)<\/strong>: Blok haritas\u0131 tamamland\u0131\u011f\u0131nda, bloklar do\u011fru offsetlerde birle\u015ftirilip ya do\u011frudan okunabilir bir disk imaj\u0131 olarak ya da yeni bir .vbk kabu\u011fu i&ccedil;ine yaz\u0131larak Veeam'in kendisinin tan\u0131yabilece\u011fi bir formata sokuluyor.<\/li>\n<\/ol>\n<h3>&Ouml;l&ccedil;ek ve g&ouml;zlemlenebilirlik<\/h3>\n<p>Terabaytlarca ham veriyi taramak I\/O-bound bir i\u015f. Go taraf\u0131nda bunu \u015f&ouml;yle yap\u0131land\u0131rd\u0131m:<\/p>\n<ul>\n<li>Disk imaj\u0131 sabit boyutlu segmentlere b&ouml;l&uuml;n&uuml;p her segment ayr\u0131 bir worker goroutine'e veriliyor (<code>sync.WaitGroup<\/code> + s\u0131n\u0131rl\u0131 say\u0131da worker, disk I\/O bant geni\u015fli\u011fini bo\u011fmamak i&ccedil;in <code>semaphore<\/code>\/buffered channel ile s\u0131n\u0131rland\u0131).<\/li>\n<li>Her worker kendi buldu\u011fu bloklar\u0131 bir sonu&ccedil; channel'\u0131na yaz\u0131yor; ayr\u0131 bir \"collector\" goroutine bunlar\u0131 merkezi blok haritas\u0131na (bir <code>sync.Map<\/code> ya da kilitli bir B-tree benzeri yap\u0131) i\u015fliyor.<\/li>\n<li>\u0130lerleme durumu (taranan byte, bulunan blok say\u0131s\u0131, do\u011frulanamayan\/eksik blok say\u0131s\u0131, &ccedil;apraz yedekten tamamlanan blok say\u0131s\u0131) periyodik olarak tek bir terminal\/TUI ekran\u0131na push ediliyor &mdash; b&uuml;y&uuml;k &ouml;l&ccedil;ekli, uzun s&uuml;ren bir i\u015flemde \"ne kadar kald\u0131, nerede hata var\" g&ouml;r&uuml;n&uuml;rl&uuml;\u011f&uuml; kritik.<\/li>\n<\/ul>\n<h2>&nbsp;<\/h2>\n<p>\u0130ki arac\u0131n da ortak noktas\u0131 \u015fu: <strong>metadata'ya g&uuml;venmemek, ham veriden &ccedil;\u0131kan izlere g&uuml;venmek.<\/strong> RAID taraf\u0131nda bu, config art\u0131klar\u0131ndan geometri okumak ve COW ile hasars\u0131z deneme yapmak anlam\u0131na geldi. Backup taraf\u0131nda ise, blok i&ccedil;eri\u011finin kendi imzalar\u0131ndan bir index'i yeniden in\u015fa etmek ve eksik par&ccedil;alar\u0131 &ccedil;apraz yedekten kapatmak anlam\u0131na geldi.<\/p>\n<p>Piyasadaki genel ama&ccedil;l\u0131 ara&ccedil;lar \"temiz veri, sa\u011flam metadata\" varsay\u0131m\u0131yla optimize edilmi\u015f durumda. O varsay\u0131m &ccedil;&ouml;kt&uuml;\u011f&uuml;nde, i\u015f orada bitmiyor &mdash; asl\u0131nda custom tooling'in ger&ccedil;ekten gerekli oldu\u011fu nokta oras\u0131 oluyor.<\/p>","excerpt":"Bu yaz\u0131, index\/journal\/dosya sistemi hi\u00e7birinin kalmad\u0131\u011f\u0131 bir Veeam kurtarma vakas\u0131nda yazd\u0131\u011f\u0131m iki arac\u0131n teknik i\u00e7 yap\u0131s\u0131n\u0131 ele al\u0131yor. Ama\u00e7 hikaye anlatmak de\u011fil; kararlar\u0131n neden \u00f6yle al\u0131nd\u0131\u011f\u0131n\u0131 ve uygulaman\u0131n nas\u0131l kuruldu\u011funu g\u00f6stermek.","created_at":"2026-08-04 17:10:41","updated_at":"2026-09-08 00:43:03","category_id":6,"view_count":247,"reading_time":9,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2026-08-04 14:10:41","featured_image":"\/uploads\/images\/2026\/08\/6a71f2cdb72b6_1785852621.jpg","slug":"kurtarilamaz-denen-raid-i-sifirdan-geri-kurmak","category_name":"Sistem","category_slug":"sistem","category_color":"#3b82f6"},{"id":412,"title":"A\u00e7\u0131k Kaynak Ara\u00e7larla Kurumsal PAM ","content":"<div id=\"model-response-message-contentr_7d2217de3cb53adf\" class=\"markdown markdown-main-panel enable-luminous-fast-follows enable-updated-hr-color md-content stronger\" dir=\"ltr\" aria-busy=\"false\" aria-live=\"polite\">\n<h1 data-path-to-node=\"0\">Apache Guacamole ve Teleport Hibrit Yakla\u015f\u0131m\u0131<\/h1>\n<p data-path-to-node=\"1\">Ayr\u0131cal\u0131kl\u0131 Eri\u015fim Y&ouml;netimi (Privileged Access Management - PAM), modern BT altyap\u0131lar\u0131nda g&uuml;venlik ve uyumlulu\u011fun temel ta\u015flar\u0131ndan biridir. Kurumsal tarafta <strong data-path-to-node=\"1\" data-index-in-node=\"159\">CyberArk<\/strong> gibi end&uuml;stri standard\u0131 &ccedil;&ouml;z&uuml;mler devasa bir g&uuml;venlik ekosistemi sunsa da y&uuml;ksek lisans maliyetleri ve karma\u015f\u0131k altyap\u0131 gereksinimleri, bir&ccedil;ok ekibi a&ccedil;\u0131k kaynak alternatiflere y&ouml;nlendiriyor.<\/p>\n<p data-path-to-node=\"2\">Peki, CyberArk benzeri kapsaml\u0131 bir PAM mimarisini a&ccedil;\u0131k kaynak ara&ccedil;larla birebir sim&uuml;le etmek m&uuml;mk&uuml;n m&uuml;?<\/p>\n<p data-path-to-node=\"3\">Yan\u0131t: <strong data-path-to-node=\"3\" data-index-in-node=\"7\">Evet.<\/strong> Tek bir ara&ccedil; t&uuml;m ihtiya&ccedil;lar\u0131 kar\u015f\u0131lamakta zorlansa da <strong data-path-to-node=\"3\" data-index-in-node=\"67\">Apache Guacamole<\/strong> ve <strong data-path-to-node=\"3\" data-index-in-node=\"87\">Teleport<\/strong>&rsquo;u bir araya getiren hibrit bir mimari kurarak enterprise seviyede bir PAM ortam\u0131 elde edebilirsiniz.<\/p>\n<h2 data-path-to-node=\"5\">Neden Hibrit Yakla\u015f\u0131m?<\/h2>\n<p data-path-to-node=\"6\">A&ccedil;\u0131k kaynak PAM projelerinde genelde iki ana k\u0131s\u0131tlama ile kar\u015f\u0131la\u015f\u0131l\u0131r:<\/p>\n<ol start=\"1\" data-path-to-node=\"7\">\n<li>\n<p data-path-to-node=\"7,0,0\"><strong data-path-to-node=\"7,0,0\" data-index-in-node=\"0\">Teleport Community<\/strong> s&uuml;r&uuml;m&uuml;n&uuml;n geli\u015fmi\u015f grafik aray&uuml;z\/RDP video kayd\u0131 konusundaki k\u0131s\u0131tlar\u0131 ve kurumsal SSO (SAML\/OIDC) s\u0131n\u0131rlar\u0131.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"7,1,0\"><strong data-path-to-node=\"7,1,0\" data-index-in-node=\"0\">Apache Guacamole<\/strong>&rsquo;un taray\u0131c\u0131 tabanl\u0131 RDP\/VNC taraf\u0131ndaki g&uuml;c&uuml;ne kar\u015f\u0131n, komut sat\u0131r\u0131 (CLI) ve terminal s&uuml;re&ccedil;lerinde DevOps ekipleri i&ccedil;in hantal kalmas\u0131.<\/p>\n<\/li>\n<\/ol>\n<p data-path-to-node=\"8\">Bu iki arac\u0131 birlikte kullanmak, birinin eksikli\u011fini di\u011ferinin g&uuml;c&uuml;yle kapatarak kusursuz bir denge yarat\u0131r.<\/p>\n<h2 data-path-to-node=\"10\">Rol Da\u011f\u0131l\u0131m\u0131: CyberArk vs. Guacamole + Teleport<\/h2>\n<p data-path-to-node=\"11\">A\u015fa\u011f\u0131daki tablo, CyberArk bile\u015fenlerinin hibrit a&ccedil;\u0131k kaynak mimarimizdeki kar\u015f\u0131l\u0131klar\u0131n\u0131 ve bu ara&ccedil;lar\u0131n se&ccedil;ilme nedenlerini &ouml;zetlemektedir:<\/p>\n<table data-path-to-node=\"12\">\n<thead>\n<tr>\n<td><strong>CyberArk Bile\u015feni<\/strong><\/td>\n<td><strong>Hangi Ara&ccedil; &Uuml;stlenir?<\/strong><\/td>\n<td><strong>Neden Bu Ara&ccedil;?<\/strong><\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span data-path-to-node=\"12,1,0,0\"><strong data-path-to-node=\"12,1,0,0\" data-index-in-node=\"0\">PVWA + PSM<\/strong> <em data-path-to-node=\"12,1,0,0\" data-index-in-node=\"11\">(Windows \/ RDP &amp; Web)<\/em><\/span><\/td>\n<td><span data-path-to-node=\"12,1,1,0\"><strong data-path-to-node=\"12,1,1,0\" data-index-in-node=\"0\">Apache Guacamole<\/strong><\/span><\/td>\n<td><span data-path-to-node=\"12,1,2,0\">Taray\u0131c\u0131 &uuml;zerinden istemcisiz (clientless) RDP eri\u015fimi ve <strong data-path-to-node=\"12,1,2,0\" data-index-in-node=\"58\">&uuml;cretsiz video oturum kayd\u0131 (Session Recording)<\/strong> i&ccedil;in idealdir.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span data-path-to-node=\"12,2,0,0\"><strong data-path-to-node=\"12,2,0,0\" data-index-in-node=\"0\">PSMP<\/strong> <em data-path-to-node=\"12,2,0,0\" data-index-in-node=\"5\">(Panelsiz \/ Do\u011frudan SSH)<\/em><\/span><\/td>\n<td><span data-path-to-node=\"12,2,1,0\"><strong data-path-to-node=\"12,2,1,0\" data-index-in-node=\"0\">Teleport<\/strong><\/span><\/td>\n<td><span data-path-to-node=\"12,2,2,0\">Terminal &uuml;zerinden do\u011frudan SSH\/SFTP t&uuml;nelleme, k\u0131sa &ouml;m&uuml;rl&uuml; CA sertifika y&ouml;netimi ve metin tabanl\u0131 komut kayd\u0131nda standartt\u0131r.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span data-path-to-node=\"12,3,0,0\"><strong data-path-to-node=\"12,3,0,0\" data-index-in-node=\"0\">CPM + Vault<\/strong> <em data-path-to-node=\"12,3,0,0\" data-index-in-node=\"12\">(Kasa &amp; \u015eifre Rotasyonu)<\/em><\/span><\/td>\n<td><span data-path-to-node=\"12,3,1,0\"><strong data-path-to-node=\"12,3,1,0\" data-index-in-node=\"0\">Teleport + HashiCorp Vault<\/strong><\/span><\/td>\n<td><span data-path-to-node=\"12,3,2,0\">Teleport sabit \u015fifre saklamak yerine sertifika tabanl\u0131 \u015fifresiz eri\u015fim sunar. \u015eifre rotasyonu ve hassas veri depolama i&ccedil;in arka plana <strong data-path-to-node=\"12,3,2,0\" data-index-in-node=\"134\">HashiCorp Vault<\/strong> veya <strong data-path-to-node=\"12,3,2,0\" data-index-in-node=\"155\">Vaultwarden<\/strong> eklenebilir.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 data-path-to-node=\"14\">Mimarinin &Ccedil;al\u0131\u015fma Mant\u0131\u011f\u0131<\/h2>\n<p data-path-to-node=\"15\">Sisteminizin merkezinde, kullan\u0131c\u0131lar\u0131n eri\u015fim tipine g&ouml;re ayr\u0131lan iki ana giri\u015f kap\u0131s\u0131 yer al\u0131r:<\/p>\n<!----><!----><!----><!----><!----><!----><!----><!---->\n<div class=\"code-block ng-tns-c2033489812-34 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation\" data-hveid=\"0\" data-ved=\"0CAAQhtANahgKEwjD0vyD6vmVAxUAAAAAHQAAAAAQtQI\"><!---->\n<div class=\"formatted-code-block-internal-container ng-tns-c2033489812-34\">\n<div class=\"animated-opacity ng-tns-c2033489812-34\">\n<div class=\"code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c2033489812-34 ng-star-inserted\"><span class=\"ng-tns-c2033489812-34\">Plaintext<\/span>\n<div class=\"buttons ng-tns-c2033489812-34 ng-star-inserted\"><!----><!----><button class=\"mdc-icon-button mat-mdc-icon-button mat-mdc-button-base mat-badge mat-unthemed mat-badge-overlap mat-badge-above mat-badge-after mat-badge-small mat-badge-hidden ng-star-inserted\" aria-label=\"Kodu indir\"><!----><!----><!----><!----><\/button><!----><!----><!----><!----><!----><!----><!----><!----><!----><button class=\"mdc-icon-button mat-mdc-icon-button mat-mdc-button-base mat-badge mat-unthemed mat-badge-overlap mat-badge-above mat-badge-after mat-badge-small mat-badge-hidden ng-star-inserted\" aria-label=\"Kodu kopyala\"><!----><!----><!----><!----><\/button><!----><!----><!----><!----><!----><!----><\/div>\n<!----><!----><\/div>\n<!---->\n<pre class=\"ng-tns-c2033489812-34\"><code class=\"code-container formatted ng-tns-c2033489812-34\" role=\"text\" data-test-id=\"code-content\">                               \u250c\u2500\u2500\u2500&gt; [ Guacamole ] \u2500\u2500\u2500&gt; Windows RDP &amp; Web Apps\n[ Kullan\u0131c\u0131lar ] \u2500\u2500(HTTPS\/SSH)\u2500\u2524       (Video Kayd\u0131 \/ Browser-based)\n                               \u2502\n                               \u2514\u2500\u2500\u2500&gt; [ Teleport ]  \u2500\u2500\u2500&gt; Linux SSH, K8s &amp; DBs\n                                       (Sertifikal\u0131 \/ CLI &amp; Terminal)\n<\/code><\/pre>\n<!----><\/div>\n<\/div>\n<\/div>\n<!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!---->\n<h3 data-path-to-node=\"17\">1. Windows ve Grafik Aray&uuml;zler (Guacamole Katman\u0131)<\/h3>\n<ul data-path-to-node=\"18\">\n<li>\n<p data-path-to-node=\"18,0,0\"><strong data-path-to-node=\"18,0,0\" data-index-in-node=\"0\">Kullan\u0131m Amac\u0131:<\/strong> Sistem y&ouml;neticileri ve d\u0131\u015f tedarik&ccedil;ilerin (Vendors) Windows sunuculara RDP ile ba\u011flanmas\u0131.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"18,1,0\"><strong data-path-to-node=\"18,1,0\" data-index-in-node=\"0\">&Ouml;ne &Ccedil;\u0131kan Avantaj\u0131:<\/strong> \u0130stemci taraf\u0131na herhangi bir yaz\u0131l\u0131m veya VPN kurulumu gerektirmez. Arka planda &ccedil;al\u0131\u015fan <code data-path-to-node=\"18,1,0\" data-index-in-node=\"109\">guacd<\/code> servisi, t&uuml;m RDP oturumunu video format\u0131nda kay\u0131t alt\u0131na al\u0131r. Kullan\u0131c\u0131lar hedef sistemlerin \u015fifrelerini hi&ccedil;bir zaman g&ouml;rmez.<\/p>\n<\/li>\n<\/ul>\n<h3 data-path-to-node=\"19\">2. Linux, Kubernetes ve Veritabanlar\u0131 (Teleport Katman\u0131)<\/h3>\n<ul data-path-to-node=\"20\">\n<li>\n<p data-path-to-node=\"20,0,0\"><strong data-path-to-node=\"20,0,0\" data-index-in-node=\"0\">Kullan\u0131m Amac\u0131:<\/strong> DevOps ve altyap\u0131 ekiplerinin do\u011frudan kendi terminallerinden (<code data-path-to-node=\"20,0,0\" data-index-in-node=\"79\">tsh ssh user@server<\/code>) veya Teleport Web UI &uuml;zerinden Linux\/K8s ortamlar\u0131na eri\u015fimi.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"20,1,0\"><strong data-path-to-node=\"20,1,0\" data-index-in-node=\"0\">&Ouml;ne &Ccedil;\u0131kan Avantaj\u0131:<\/strong> Statik SSH anahtarlar\u0131 yerini <strong data-path-to-node=\"20,1,0\" data-index-in-node=\"50\">1-8 saatlik ge&ccedil;ici sertifikalara<\/strong> b\u0131rak\u0131r. Terminal &uuml;zerinde &ccedil;al\u0131\u015ft\u0131r\u0131lan her komut metin format\u0131nda index'lenir, aranabilir ve denetlenebilir hale gelir.<\/p>\n<\/li>\n<\/ul>\n<h2 data-path-to-node=\"22\">Teleport Community S&uuml;r&uuml;m&uuml;nde SSO K\u0131s\u0131tlamas\u0131n\u0131 A\u015fmak<\/h2>\n<p data-path-to-node=\"23\">Teleport&rsquo;un &uuml;cretsiz topluluk s&uuml;r&uuml;m&uuml;nde Azure AD (Entra ID) veya Okta gibi SAML\/OIDC entegrasyonlar\u0131 k\u0131s\u0131tl\u0131d\u0131r (yerel kullan\u0131c\u0131 veya GitHub OAuth desteklenir).<\/p>\n<p data-path-to-node=\"24\">Bu k\u0131s\u0131tlamay\u0131 mimarimizde \u015fu ad\u0131mlarla a\u015fabiliriz:<\/p>\n<ul data-path-to-node=\"25\">\n<li>\n<p data-path-to-node=\"25,0,0\"><strong data-path-to-node=\"25,0,0\" data-index-in-node=\"0\">Kimlik Merkezi (IdP):<\/strong> \u015eirket i&ccedil;i kullan\u0131c\u0131 y&ouml;netimi i&ccedil;in <strong data-path-to-node=\"25,0,0\" data-index-in-node=\"57\">Keycloak<\/strong> (A&ccedil;\u0131k kaynak IdP) veya <strong data-path-to-node=\"25,0,0\" data-index-in-node=\"89\">FreeIPA \/ Active Directory<\/strong> altyap\u0131s\u0131 konumland\u0131r\u0131l\u0131r.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"25,1,0\"><strong data-path-to-node=\"25,1,0\" data-index-in-node=\"0\">Guacamole Taraf\u0131:<\/strong> LDAP, Active Directory veya Keycloak (OpenID) mod&uuml;lleriyle entegre edilerek kurumsal kimliklerle oturum a&ccedil;mas\u0131 sa\u011flan\u0131r.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"25,2,0\"><strong data-path-to-node=\"25,2,0\" data-index-in-node=\"0\">Teleport Taraf\u0131:<\/strong> GitHub OAuth t&uuml;nellemesi veya Keycloak &uuml;zerindeki OAuth k&ouml;pr&uuml;leri kullan\u0131larak kurumsal kullan\u0131c\u0131 do\u011frulamas\u0131na ba\u011flan\u0131r.<\/p>\n<\/li>\n<\/ul>\n<h2 data-path-to-node=\"27\">&nbsp;<\/h2>\n<p data-path-to-node=\"28\">Apache Guacamole ve Teleport kombinasyonu, a&ccedil;\u0131k kaynak d&uuml;nyas\u0131nda CyberArk seviyesinde bir PAM mimarisi kurman\u0131n en efektif yoludur.<\/p>\n<ul data-path-to-node=\"29\">\n<li>\n<p data-path-to-node=\"29,0,0\"><strong data-path-to-node=\"29,0,0\" data-index-in-node=\"0\">Tam Kapsama:<\/strong> Windows\/RDP taraf\u0131nda g&ouml;rsel video kayd\u0131, Linux\/CLI taraf\u0131nda ise sertifika tabanl\u0131 h\u0131zl\u0131 ve g&uuml;venli eri\u015fim elde edilir.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"29,1,0\"><strong data-path-to-node=\"29,1,0\" data-index-in-node=\"0\">S\u0131f\u0131r Lisans Maliyeti:<\/strong> Y&uuml;ksek b&uuml;t&ccedil;eli lisans s&ouml;zle\u015fmelerine ba\u011f\u0131ml\u0131 kalmadan %100 a&ccedil;\u0131k kaynak bile\u015fenlerle enterprise g&uuml;venlik standartlar\u0131 yakalan\u0131r.<\/p>\n<\/li>\n<li>\n<p data-path-to-node=\"29,2,0\"><strong data-path-to-node=\"29,2,0\" data-index-in-node=\"0\">Geli\u015fmi\u015f Denetim (Auditing):<\/strong> T\u0131pk\u0131 CyberArk PSM gibi, grafik ekranda yap\u0131lan hareketlerin video kayd\u0131na ve terminalde y&uuml;r&uuml;t&uuml;len komutlar\u0131n detayl\u0131 metin loglar\u0131na tek bir mimari &uuml;zerinden eri\u015filebilir.<\/p>\n<\/li>\n<\/ul>\n<\/div>","excerpt":"CyberArk benzeri kapsaml\u0131 bir PAM mimarisini a\u00e7\u0131k kaynak ara\u00e7larla birebir sim\u00fcle etmek m\u00fcmk\u00fcn m\u00fc?","created_at":"2026-07-30 11:17:16","updated_at":"2026-09-23 11:20:31","category_id":6,"view_count":262,"reading_time":5,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2026-07-30 08:17:16","featured_image":"\/uploads\/images\/2026\/07\/6a6b087a51a3e_1785399418.png","slug":"acik-kaynak-araclarla-kurumsal-pam","category_name":"Sistem","category_slug":"sistem","category_color":"#3b82f6"}]