{"id":35270,"date":"2025-11-27T18:40:57","date_gmt":"2025-11-27T15:40:57","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=35270"},"modified":"2025-11-27T18:40:57","modified_gmt":"2025-11-27T15:40:57","slug":"mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/","title":{"rendered":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi"},"content":{"rendered":"<p><body><\/p>\n<h2>MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi<\/h2>\n<p>MySQL veritabanlar\u0131, modern web uygulamalar\u0131n\u0131n ve kurumsal sistemlerin belkemi\u011fini olu\u015fturur. Zaman zaman, bu kritik veritabanlar\u0131n\u0131 bir sunucudan di\u011ferine ta\u015f\u0131mak gerekebilir. Bu ta\u015f\u0131ma i\u015flemi, \u00e7e\u015fitli nedenlerle ortaya \u00e7\u0131kabilir ve dikkatli bir planlama ile uygulanmas\u0131 gereken hassas bir s\u00fcre\u00e7tir. Bu kapsaml\u0131 rehberde, MySQL veritabanlar\u0131n\u0131 iki sunucu aras\u0131nda g\u00fcvenli, verimli ve minimum kesintiyle nas\u0131l ta\u015f\u0131yaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m inceleyece\u011fiz.<\/p>\n<h3>Neden MySQL Veritaban\u0131 Ta\u015f\u0131n\u0131r?<\/h3>\n<p>Veritaban\u0131 ta\u015f\u0131ma ihtiyac\u0131, genellikle a\u015fa\u011f\u0131daki senaryolardan bir veya daha fazlas\u0131ndan kaynaklan\u0131r:<\/p>\n<p>*   <strong>Sunucu Y\u00fckseltmeleri veya Donan\u0131m De\u011fi\u015fiklikleri:<\/strong> Mevcut sunucunun donan\u0131m\u0131 eskidi\u011finde, performans\u0131 yetersiz kald\u0131\u011f\u0131nda veya yeni nesil donan\u0131mlara ge\u00e7i\u015f yap\u0131lmas\u0131 gerekti\u011finde veritaban\u0131 yeni bir sunucuya ta\u015f\u0131nabilir.<br \/>\n*   <strong>\u0130\u015fletim Sistemi Y\u00fckseltmeleri:<\/strong> Mevcut i\u015fletim sisteminin destek s\u00fcresi doldu\u011funda veya daha g\u00fcncel, g\u00fcvenli bir s\u00fcr\u00fcme ge\u00e7i\u015f yap\u0131lmas\u0131 gerekti\u011finde, veritaban\u0131 yeni bir i\u015fletim sistemi kurulu sunucuya ta\u015f\u0131nabilir.<br \/>\n*   <strong>Bulut Ortam\u0131na Ge\u00e7i\u015f:<\/strong> \u015eirketler, maliyet optimizasyonu, esneklik, \u00f6l\u00e7eklenebilirlik ve y\u00f6netilebilirlik avantajlar\u0131ndan faydalanmak amac\u0131yla yerel (on-premise) sunucular\u0131ndan bulut sa\u011flay\u0131c\u0131lar\u0131n\u0131n (AWS, Azure, Google Cloud vb.) y\u00f6netilen veritaban\u0131 hizmetlerine ge\u00e7i\u015f yapabilirler.<br \/>\n*   <strong>Felaket Kurtarma ve Y\u00fcksek Eri\u015filebilirlik:<\/strong> Felaket kurtarma stratejilerinin bir par\u00e7as\u0131 olarak, veritaban\u0131 yedek bir konuma veya farkl\u0131 bir veri merkezine ta\u015f\u0131nabilir. Y\u00fcksek eri\u015filebilirlik \u00e7\u00f6z\u00fcmlerinin (\u00f6rne\u011fin, replikasyon) kurulmas\u0131 da ta\u015f\u0131ma gerektirebilir.<br \/>\n*   <strong>Y\u00fck Dengeleme ve Performans \u0130yile\u015ftirmeleri:<\/strong> Yo\u011fun trafik alan uygulamalarda, veritaban\u0131 y\u00fck\u00fcn\u00fc dengelemek veya performans\u0131 art\u0131rmak amac\u0131yla veritaban\u0131 farkl\u0131, daha g\u00fc\u00e7l\u00fc bir sunucuya veya bir veritaban\u0131 k\u00fcmesinin par\u00e7as\u0131 olarak ta\u015f\u0131nabilir.<br \/>\n*   <strong>Ortam Ayr\u0131m\u0131:<\/strong> Geli\u015ftirme, test ve \u00fcretim ortamlar\u0131n\u0131 birbirinden ay\u0131rmak veya birle\u015ftirme ihtiyac\u0131 do\u011fdu\u011funda veritaban\u0131 ta\u015f\u0131nabilir.<\/p>\n<p>Bu nedenlerin her biri, ta\u015f\u0131ma s\u00fcrecinin kendine \u00f6zg\u00fc zorluklar\u0131n\u0131 ve gereksinimlerini beraberinde getirebilir. Bu rehber, bu farkl\u0131 senaryolara uygun \u00e7\u00f6z\u00fcmler sunmay\u0131 ama\u00e7lamaktad\u0131r.<\/p>\n<h3>Ta\u015f\u0131ma \u00d6ncesi Haz\u0131rl\u0131klar: Ba\u015far\u0131l\u0131 Bir Ta\u015f\u0131ma \u0130\u00e7in Temel Ad\u0131mlar<\/h3>\n<p>Ba\u015far\u0131l\u0131 bir veritaban\u0131 ta\u015f\u0131mas\u0131, titiz bir \u00f6n haz\u0131rl\u0131k gerektirir. Bu ad\u0131mlar, olas\u0131 sorunlar\u0131 minimize etmenize ve kesintisiz bir ge\u00e7i\u015f sa\u011flaman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h4>Hedef ve Kaynak Ortam Analizi<\/h4>\n<p>*   <strong>MySQL S\u00fcr\u00fcmleri:<\/strong> Kaynak ve hedef sunuculardaki MySQL s\u00fcr\u00fcmlerinin uyumlu oldu\u011fundan emin olun. B\u00fcy\u00fck s\u00fcr\u00fcm farkl\u0131l\u0131klar\u0131 (\u00f6rn. MySQL 5.7&#8217;den 8.0&#8217;a) uyumluluk sorunlar\u0131na yol a\u00e7abilir ve ek ad\u0131mlar gerektirebilir.<br \/>\n*   <strong>\u0130\u015fletim Sistemi:<\/strong> \u0130\u015fletim sistemi t\u00fcr\u00fc (Linux da\u011f\u0131t\u0131m\u0131, Windows Server) ve s\u00fcr\u00fcm\u00fc, fiziksel ta\u015f\u0131ma y\u00f6ntemlerini etkileyebilir.<br \/>\n*   <strong>Donan\u0131m Kaynaklar\u0131:<\/strong> Hedef sunucunun CPU, RAM, disk alan\u0131 ve I\/O performans\u0131 a\u00e7\u0131s\u0131ndan kaynak sunucudan daha iyi veya en az\u0131ndan e\u015fde\u011fer oldu\u011fundan emin olun. Disk tipi (SSD\/NVMe) ve RAID yap\u0131land\u0131rmas\u0131 performans\u0131 do\u011frudan etkiler.<br \/>\n*   <strong>A\u011f Yap\u0131land\u0131rmas\u0131:<\/strong> Kaynak ve hedef sunucular aras\u0131ndaki a\u011f ba\u011flant\u0131s\u0131n\u0131n h\u0131z\u0131n\u0131 ve g\u00fcvenilirli\u011fini kontrol edin. G\u00fcvenlik duvar\u0131 (firewall) kurallar\u0131n\u0131n gerekli portlara (varsay\u0131lan MySQL portu 3306) eri\u015fime izin verdi\u011finden emin olun.<br \/>\n*   <strong>Depolama Motorlar\u0131:<\/strong> Kaynak veritaban\u0131ndaki tablolar\u0131n kulland\u0131\u011f\u0131 depolama motorlar\u0131n\u0131 (InnoDB, MyISAM vb.) kontrol edin. \u00d6zellikle InnoDB, modern MySQL kurulumlar\u0131nda varsay\u0131lan ve \u00f6nerilen motordur.<\/p>\n<h4>Yedekleme Stratejisi<\/h4>\n<p>Ta\u015f\u0131ma i\u015flemine ba\u015flamadan \u00f6nce, kaynak veritaban\u0131n\u0131n tam ve do\u011frulanm\u0131\u015f bir yede\u011fini almak mutlak bir zorunluluktur. Bu yedek, herhangi bir sorun durumunda geri d\u00f6nebilece\u011finiz bir g\u00fcvenlik a\u011f\u0131 sa\u011flar. Yedekleme i\u00e7in <code>mysqldump<\/code> veya fiziksel yedekleme ara\u00e7lar\u0131 kullan\u0131labilir. Yede\u011fin b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc do\u011frulamak i\u00e7in geri y\u00fckleme testi yap\u0131lmas\u0131 \u015fiddetle tavsiye edilir.<\/p>\n<h4>Kesinti S\u00fcresi Planlamas\u0131<\/h4>\n<p>Veritaban\u0131 ta\u015f\u0131mas\u0131 genellikle bir miktar kesinti s\u00fcresi gerektirir. Bu s\u00fcreyi en aza indirmek i\u00e7in bir plan yap\u0131n:<br \/>\n*   Uygulaman\u0131n en az kullan\u0131ld\u0131\u011f\u0131 zaman dilimini (bak\u0131m penceresi) belirleyin.<br \/>\n*   Kullan\u0131c\u0131lara veya payda\u015flara \u00f6nceden bilgi verin.<br \/>\n*   Farkl\u0131 ta\u015f\u0131ma y\u00f6ntemlerinin (\u00f6rne\u011fin, replikasyon tabanl\u0131 ta\u015f\u0131ma) kesinti s\u00fcresi \u00fczerindeki etkilerini de\u011ferlendirin.<\/p>\n<h4>Eri\u015fim \u0130zinleri<\/h4>\n<p>Hem kaynak hem de hedef sunucularda SSH eri\u015fimi ve MySQL root veya yeterli yetkilere sahip bir kullan\u0131c\u0131 hesab\u0131 gerekecektir.<br \/>\n*   SSH eri\u015fimi i\u00e7in kullan\u0131c\u0131 ad\u0131 ve \u015fifre veya SSH anahtarlar\u0131 haz\u0131rlay\u0131n.<br \/>\n<em>   MySQL i\u00e7in <code>GRANT ALL PRIVILEGES ON <\/em>.* TO 'kullanici'@'%' IDENTIFIED BY 'sifre';<\/code> gibi komutlarla gerekli izinleri sa\u011flay\u0131n.<\/p>\n<h4>Gerekli Ara\u00e7lar<\/h4>\n<p>Ta\u015f\u0131ma i\u015flemi i\u00e7in ihtiyac\u0131n\u0131z olacak temel ara\u00e7lar \u015funlard\u0131r:<br \/>\n*   <code>mysqldump<\/code>: Mant\u0131ksal yedekleme ve geri y\u00fckleme i\u00e7in.<br \/>\n*   <code>mysql<\/code> istemcisi: SQL dosyalar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmak ve veritaban\u0131yla etkile\u015fim kurmak i\u00e7in.<br \/>\n*   <code>scp<\/code> veya <code>rsync<\/code>: Dosyalar\u0131 sunucular aras\u0131nda g\u00fcvenli bir \u015fekilde aktarmak i\u00e7in. <code>rsync<\/code>, b\u00fcy\u00fck dosyalar i\u00e7in daha verimli olabilir ve kesintiye u\u011frayan aktar\u0131mlar\u0131 kald\u0131\u011f\u0131 yerden devam ettirme \u00f6zelli\u011fine sahiptir.<br \/>\n*   <code>gzip<\/code> \/ <code>bzip2<\/code>: Yedek dosyalar\u0131n\u0131 s\u0131k\u0131\u015ft\u0131rmak i\u00e7in.<br \/>\n*   <code>ssh<\/code>: Sunuculara uzaktan eri\u015fim i\u00e7in.<\/p>\n<h4>Veritaban\u0131 Boyutu ve S\u00fcre Tahmini<\/h4>\n<p>Veritaban\u0131n\u0131n boyutu, ta\u015f\u0131ma s\u00fcresini ve se\u00e7ilecek y\u00f6ntemi b\u00fcy\u00fck \u00f6l\u00e7\u00fcde etkiler. \u00c7ok b\u00fcy\u00fck veritabanlar\u0131 i\u00e7in <code>mysqldump<\/code> yava\u015f kalabilir ve fiziksel ta\u015f\u0131ma veya replikasyon daha uygun olabilir. Tahmini ta\u015f\u0131ma s\u00fcresini belirlemek i\u00e7in k\u00fc\u00e7\u00fck bir test veritaban\u0131 \u00fczerinde deneme yap\u0131n.<\/p>\n<h4>Test Ortam\u0131<\/h4>\n<p>M\u00fcmk\u00fcnse, ta\u015f\u0131ma i\u015flemini bir test ortam\u0131nda (\u00fcretim d\u0131\u015f\u0131) ba\u015ftan sona sim\u00fcle edin. Bu, olas\u0131 sorunlar\u0131 \u00f6nceden tespit etmenize ve ger\u00e7ek ta\u015f\u0131ma s\u0131ras\u0131nda daha p\u00fcr\u00fczs\u00fcz bir deneyim ya\u015faman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<h3>Ta\u015f\u0131ma Y\u00f6ntemleri: Farkl\u0131 Senaryolar \u0130\u00e7in \u00c7\u00f6z\u00fcmler<\/h3>\n<p>MySQL veritaban\u0131 ta\u015f\u0131mas\u0131 i\u00e7in \u00e7e\u015fitli y\u00f6ntemler mevcuttur. Her bir y\u00f6ntemin avantajlar\u0131 ve dezavantajlar\u0131 vard\u0131r ve do\u011fru se\u00e7imi yapmak, projenizin gereksinimlerine ve k\u0131s\u0131tlamalar\u0131na ba\u011fl\u0131d\u0131r.<\/p>\n<h4>Y\u00f6ntem 1: <code>mysqldump<\/code> ile Mant\u0131ksal Yedekleme ve Geri Y\u00fckleme (En Yayg\u0131n)<\/h4>\n<p>Bu y\u00f6ntem, k\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli veritabanlar\u0131 i\u00e7in en basit ve en yayg\u0131n kullan\u0131lan y\u00f6ntemdir. Veritaban\u0131n\u0131n SQL komutlar\u0131 olarak d\u0131\u015fa aktar\u0131lmas\u0131n\u0131 ve ard\u0131ndan hedef sunucuda geri y\u00fcklenmesini i\u00e7erir.<\/p>\n<h5>Kaynak Sunucuda Yedekleme<\/h5>\n<p>Kaynak sunucuda SSH \u00fczerinden oturum a\u00e7\u0131n ve a\u015fa\u011f\u0131daki komutu kullanarak veritaban\u0131n\u0131z\u0131 yedekleyin. T\u00fcm veritabanlar\u0131n\u0131 yedeklemek istiyorsan\u0131z <code>--all-databases<\/code> bayra\u011f\u0131n\u0131 kullanabilirsiniz. Belirli bir veritaban\u0131n\u0131 yedeklemek i\u00e7in veritaban\u0131 ad\u0131n\u0131 belirtin.<\/p>\n<pre><code class=\"language-bash\"># T\u00fcm veritabanlar\u0131n\u0131 yedeklemek i\u00e7in:\nmysqldump -u root -p --all-databases --single-transaction --master-data=2 --routines --triggers --events | gzip > all_databases_yedek.sql.gz\n\n<h2>Belirli bir veritaban\u0131n\u0131 yedeklemek i\u00e7in (\u00f6rne\u011fin, 'myapp_db'):<\/h2>\nmysqldump -u root -p myapp_db --single-transaction --master-data=2 --routines --triggers --events | gzip > myapp_db_yedek.sql.gz<\/code><\/pre>\n<p><strong>Parametrelerin A\u00e7\u0131klamas\u0131:<\/strong><br \/>\n*   <code>-u root -p<\/code>: MySQL root kullan\u0131c\u0131s\u0131 ile ba\u011flan\u0131n ve \u015fifre isteyin. G\u00fcvenlik nedeniyle <code>-pSifre<\/code> \u015feklinde \u015fifreyi komut i\u00e7inde a\u00e7\u0131k\u00e7a belirtmek \u00f6nerilmez.<br \/>\n*   <code>--all-databases<\/code>: T\u00fcm veritabanlar\u0131n\u0131 yedekler.<br \/>\n*   <code>myapp_db<\/code>: Yedeklenecek belirli veritaban\u0131n\u0131n ad\u0131.<br \/>\n*   <code>--single-transaction<\/code>: InnoDB tablolar\u0131 i\u00e7in tutarl\u0131 bir yedekleme sa\u011flar. Yedekleme s\u0131ras\u0131nda veritaban\u0131n\u0131n kilitlenmesini \u00f6nler.<br \/>\n*   <code>--master-data=2<\/code>: Yedek dosyas\u0131n\u0131n ba\u015f\u0131na, replikasyon i\u00e7in gerekli olan binary log konumunu (binlog file ve position) ekler. Bu, \u00f6zellikle replikasyon kurmay\u0131 planl\u0131yorsan\u0131z \u00f6nemlidir. <code>2<\/code> de\u011feri, bu bilgiyi SQL yorumu olarak ekler.<br \/>\n*   <code>--routines<\/code>: Sakl\u0131 yordamlar\u0131 (stored procedures) ve fonksiyonlar\u0131 yedekler.<br \/>\n*   <code>--triggers<\/code>: Tetikleyicileri (triggers) yedekler.<br \/>\n*   <code>--events<\/code>: Olaylar\u0131 (events) yedekler.<br \/>\n*   <code>| gzip > yedek_dosyasi.sql.gz<\/code>: \u00c7\u0131kt\u0131y\u0131 <code>gzip<\/code> ile s\u0131k\u0131\u015ft\u0131r\u0131r ve <code>yedek_dosyasi.sql.gz<\/code> adl\u0131 dosyaya yazar. Bu, disk alan\u0131ndan tasarruf sa\u011flar ve aktar\u0131m s\u00fcresini k\u0131salt\u0131r.<\/p>\n<h5>Yede\u011fi Hedef Sunucuya Aktarma<\/h5>\n<p>Yedek dosyas\u0131n\u0131 kaynak sunucudan hedef sunucuya aktar\u0131n. <code>scp<\/code> veya <code>rsync<\/code> kullanabilirsiniz.<\/p>\n<pre><code class=\"language-bash\"># scp ile aktarma:\nscp \/path\/to\/all_databases_yedek.sql.gz user@hedef_sunucu_ip:\/path\/to\/hedef\/dizin\/\n\n<h2>rsync ile aktarma (b\u00fcy\u00fck dosyalar i\u00e7in ve devam edebilirlik i\u00e7in \u00f6nerilir):<\/h2>\nrsync -avzP \/path\/to\/all_databases_yedek.sql.gz user@hedef_sunucu_ip:\/path\/to\/hedef\/dizin\/<\/code><\/pre>\n<h5>Hedef Sunucuda Geri Y\u00fckleme<\/h5>\n<p>Hedef sunucuda SSH \u00fczerinden oturum a\u00e7\u0131n, yedek dosyas\u0131n\u0131 aktard\u0131\u011f\u0131n\u0131z dizine gidin ve a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 izleyin:<\/p>\n<p>1.  <strong>MySQL servisini ba\u015flat\u0131n:<\/strong> E\u011fer durdurulduysa, <code>sudo systemctl start mysql<\/code> veya <code>sudo service mysql start<\/code>.<br \/>\n2.  <strong>Gerekirse bo\u015f veritabanlar\u0131n\u0131 olu\u015fturun:<\/strong> E\u011fer <code>--all-databases<\/code> ile yedek almad\u0131ysan\u0131z ve belirli bir veritaban\u0131n\u0131 ta\u015f\u0131yorsan\u0131z, hedef sunucuda bu veritaban\u0131n\u0131n bo\u015f halini olu\u015fturman\u0131z gerekebilir.<\/p>\n<pre><code class=\"language-sql\">mysql -u root -p -e \"CREATE DATABASE myapp_db CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;\"<\/code><\/pre>\n<p>    <code>--all-databases<\/code> ile yedek ald\u0131ysan\u0131z, <code>CREATE DATABASE<\/code> komutlar\u0131 yedek dosyas\u0131nda zaten olacakt\u0131r.<br \/>\n3.  <strong>Yede\u011fi geri y\u00fckleyin:<\/strong><\/p>\n<pre><code class=\"language-bash\"># T\u00fcm veritabanlar\u0131n\u0131 geri y\u00fcklemek i\u00e7in:\n    gunzip < all_databases_yedek.sql.gz | mysql -u root -p\n\n    # Belirli bir veritaban\u0131n\u0131 geri y\u00fcklemek i\u00e7in:\n    gunzip < myapp_db_yedek.sql.gz | mysql -u root -p myapp_db<\/code><\/pre>\n<p>    B\u00fcy\u00fck veritabanlar\u0131 i\u00e7in geri y\u00fckleme i\u015flemi uzun s\u00fcrebilir. Bu s\u00fcre\u00e7te MySQL sunucusunun <code>innodb_buffer_pool_size<\/code> gibi parametrelerini ge\u00e7ici olarak art\u0131rmak performans\u0131 iyile\u015ftirebilir. Ayr\u0131ca, geri y\u00fckleme s\u0131ras\u0131nda <code>log_bin_trust_function_creators<\/code> ve <code>foreign_key_checks=0<\/code>, <code>unique_checks=0<\/code> gibi ayarlar\u0131n ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131lmas\u0131 i\u015flemi h\u0131zland\u0131rabilir, ancak dikkatli kullan\u0131lmal\u0131d\u0131r.<\/p>\n<h5>Avantajlar ve Dezavantajlar<\/h5>\n<p>*   <strong>Avantajlar:<\/strong> Basit, anla\u015f\u0131l\u0131r, farkl\u0131 MySQL s\u00fcr\u00fcmleri ve i\u015fletim sistemleri aras\u0131nda esnek ge\u00e7i\u015f sa\u011flar, veritaban\u0131 \u015femas\u0131n\u0131 ve veriyi SQL komutlar\u0131 olarak ta\u015f\u0131r.<br \/>\n*   <strong>Dezavantajlar:<\/strong> \u00c7ok b\u00fcy\u00fck veritabanlar\u0131 i\u00e7in (birka\u00e7 GB'tan fazlas\u0131) yava\u015f olabilir, yedekleme ve geri y\u00fckleme s\u0131ras\u0131nda veritaban\u0131 kilitlenebilir (her ne kadar <code>--single-transaction<\/code> bunu InnoDB i\u00e7in hafifletse de), daha uzun kesinti s\u00fcresi gerektirebilir.<\/p>\n<h4>Y\u00f6ntem 2: Fiziksel Dosyalar\u0131n Kopyalanmas\u0131 (InnoDB i\u00e7in)<\/h4>\n<p>Bu y\u00f6ntem, \u00f6zellikle b\u00fcy\u00fck InnoDB veritabanlar\u0131 i\u00e7in <code>mysqldump<\/code>'tan \u00e7ok daha h\u0131zl\u0131 olabilir. Ancak, daha k\u0131s\u0131tlay\u0131c\u0131 gereksinimleri vard\u0131r: kaynak ve hedef sunucularda ayn\u0131 MySQL s\u00fcr\u00fcm\u00fc ve genellikle ayn\u0131 i\u015fletim sistemi mimarisi olmal\u0131d\u0131r.<\/p>\n<h5>Ne Zaman Kullan\u0131l\u0131r?<\/h5>\n<p>*   \u00c7ok b\u00fcy\u00fck veritabanlar\u0131 s\u00f6z konusu oldu\u011funda.<br \/>\n*   Minimum kesinti s\u00fcresi hedeflendi\u011finde (veri aktar\u0131m h\u0131z\u0131 nedeniyle).<br \/>\n*   Kaynak ve hedef MySQL s\u00fcr\u00fcmleri ve i\u015fletim sistemleri tamamen uyumlu oldu\u011funda.<\/p>\n<h5>Ad\u0131mlar<\/h5>\n<p>1.  <strong>MySQL Servislerini Durdurma:<\/strong> Hem kaynak hem de hedef sunucularda MySQL servisini durdurun. Bu, veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc sa\u011flamak i\u00e7in kritik \u00f6neme sahiptir.<\/p>\n<pre><code class=\"language-bash\">sudo systemctl stop mysql # veya sudo service mysql stop<\/code><\/pre>\n<p>2.  <strong><code>datadir<\/code> Konumunu Belirleme:<\/strong> MySQL yap\u0131land\u0131rma dosyas\u0131nda (<code>\/etc\/mysql\/my.cnf<\/code> veya <code>\/etc\/my.cnf<\/code>) <code>datadir<\/code> parametresini bularak veritaban\u0131 dosyalar\u0131n\u0131n depoland\u0131\u011f\u0131 dizini \u00f6\u011frenin.<\/p>\n<pre><code class=\"language-bash\">grep \"datadir\" \/etc\/mysql\/my.cnf\n    # \u00c7\u0131kt\u0131 \u00f6rnek: datadir = \/var\/lib\/mysql<\/code><\/pre>\n<p>3.  <strong>Veritaban\u0131 Dosyalar\u0131n\u0131 Kopyalama:<\/strong> Kaynak sunucudaki t\u00fcm <code>datadir<\/code> i\u00e7eri\u011fini (veya yaln\u0131zca ta\u015f\u0131mak istedi\u011finiz veritabanlar\u0131n\u0131n dizinlerini) hedef sunucudaki ayn\u0131 <code>datadir<\/code> konumuna kopyalay\u0131n. <code>rsync<\/code> bu i\u015flem i\u00e7in idealdir.<\/p>\n<pre><code class=\"language-bash\"># Kaynak sunucuda:\n    sudo rsync -avzP \/var\/lib\/mysql\/ user@hedef_sunucu_ip:\/var\/lib\/mysql\/\n    # Not: \/var\/lib\/mysql\/ i\u00e7indeki t\u00fcm dosyalar\u0131 ve dizinleri kopyalamak,\n    # MySQL sistem veritabanlar\u0131n\u0131 (mysql, performance_schema, sys) ve kullan\u0131c\u0131lar\u0131 da ta\u015f\u0131r.\n    # E\u011fer yaln\u0131zca belirli veritabanlar\u0131n\u0131 ta\u015f\u0131mak istiyorsan\u0131z,\n    # o veritaban\u0131n\u0131n dizinini (\u00f6rn. \/var\/lib\/mysql\/myapp_db) ve ilgili .ibd dosyalar\u0131n\u0131 kopyalaman\u0131z gerekir.\n    # Ancak bu, daha karma\u015f\u0131k olabilir ve genellikle t\u00fcm datadir'i kopyalamak daha g\u00fcvenlidir.<\/code><\/pre>\n<p>    <strong>\u00d6nemli Not:<\/strong> E\u011fer <code>mysql<\/code> sistem veritaban\u0131n\u0131 da kopyal\u0131yorsan\u0131z, kullan\u0131c\u0131 hesaplar\u0131 ve yetkilendirmeler de ta\u015f\u0131nacakt\u0131r. E\u011fer sadece uygulama veritabanlar\u0131n\u0131 kopyal\u0131yorsan\u0131z, hedef sunucuda kullan\u0131c\u0131lar\u0131 manuel olarak olu\u015fturman\u0131z gerekecektir.<br \/>\n4.  <strong>Dosya \u0130zinlerini Ayarlama:<\/strong> Hedef sunucuda kopyalanan dosyalar\u0131n ve dizinlerin MySQL kullan\u0131c\u0131s\u0131 ve grubuna ait oldu\u011fundan emin olun.<\/p>\n<pre><code class=\"language-bash\">sudo chown -R mysql:mysql \/var\/lib\/mysql\/\n    sudo chmod -R 700 \/var\/lib\/mysql\/ # Gerekirse<\/code><\/pre>\n<p>5.  <strong>MySQL Servisini Ba\u015flatma:<\/strong> Hedef sunucuda MySQL servisini ba\u015flat\u0131n.<\/p>\n<pre><code class=\"language-bash\">sudo systemctl start mysql # veya sudo service mysql start<\/code><\/pre>\n<p>    Servis ba\u015flat\u0131lamazsa, MySQL hata g\u00fcnl\u00fcklerini (<code>\/var\/log\/mysql\/error.log<\/code> veya <code>datadir<\/code> i\u00e7indeki <code>.err<\/code> dosyas\u0131) kontrol edin.<\/p>\n<h5>Avantajlar ve Dezavantajlar<\/h5>\n<p>*   <strong>Avantajlar:<\/strong> \u00c7ok h\u0131zl\u0131 veri aktar\u0131m\u0131, b\u00fcy\u00fck veritabanlar\u0131 i\u00e7in ideal, <code>mysqldump<\/code>'a g\u00f6re daha az CPU ve bellek t\u00fcketimi.<br \/>\n*   <strong>Dezavantajlar:<\/strong> Kaynak ve hedef MySQL s\u00fcr\u00fcmleri (ve genellikle minor s\u00fcr\u00fcmleri) ve i\u015fletim sistemi mimarisi (\u00f6rn. 64-bit) uyumlu olmal\u0131d\u0131r. Daha fazla kesinti s\u00fcresi gerektirebilir (\u00e7\u00fcnk\u00fc MySQL servisleri durdurulur). Daha az esnek.<\/p>\n<h4>Y\u00f6ntem 3: MySQL Replikasyonu Kullanarak Ta\u015f\u0131ma (Minimum Kesinti S\u00fcresi \u0130\u00e7in)<\/h4>\n<p>Bu y\u00f6ntem, neredeyse s\u0131f\u0131r kesinti s\u00fcresiyle bir veritaban\u0131n\u0131 ta\u015f\u0131mak i\u00e7in en iyi yakla\u015f\u0131mlardan biridir. Kaynak sunucuyu ana (master), hedef sunucuyu ise k\u00f6le (slave) olarak yap\u0131land\u0131rarak veritabanlar\u0131n\u0131 senkronize eder.<\/p>\n<h5>Ne Zaman Kullan\u0131l\u0131r?<\/h5>\n<p>*   Uygulaman\u0131n kesinti s\u00fcresinin minimumda tutulmas\u0131 gerekti\u011finde.<br \/>\n*   B\u00fcy\u00fck ve s\u00fcrekli de\u011fi\u015fen veritabanlar\u0131 i\u00e7in.<br \/>\n*   Daha karma\u015f\u0131k bir kurulum yapmaya istekli olundu\u011funda.<\/p>\n<h5>Ad\u0131mlar<\/h5>\n<p>1.  <strong>Kaynak Sunucuda \u0130kili G\u00fcnl\u00fcklemeyi (Binary Logging) Etkinle\u015ftirme:<\/strong><br \/>\n    <code>my.cnf<\/code> dosyas\u0131nda (genellikle <code>\/etc\/mysql\/my.cnf<\/code> veya <code>\/etc\/my.cnf<\/code>) a\u015fa\u011f\u0131daki ayarlar\u0131 yap\u0131n:<\/p>\n<pre><code class=\"language-ini\">[mysqld]\n    log_bin = mysql-bin\n    server_id = 1\n    expire_logs_days = 7 # Binary log dosyalar\u0131n\u0131 7 g\u00fcn sonra otomatik sil\n    binlog_format = ROW # Replikasyon i\u00e7in \u00f6nerilir<\/code><\/pre>\n<p>    De\u011fi\u015fiklikleri uygulamak i\u00e7in MySQL servisini yeniden ba\u015flat\u0131n.<\/p>\n<pre><code class=\"language-bash\">sudo systemctl restart mysql<\/code><\/pre>\n<p>2.  <strong>Kaynak Sunucuda Replikasyon Kullan\u0131c\u0131s\u0131 Olu\u015fturma:<\/strong><\/p>\n<pre><code class=\"language-sql\">CREATE USER 'replikasyon_kullanici'@'%' IDENTIFIED BY 'sifre';\n    GRANT REPLICATION SLAVE ON <em>.<\/em> TO 'replikasyon_kullanici'@'%';\n    FLUSH PRIVILEGES;<\/code><\/pre>\n<p>3.  <strong>Kaynak Sunucuda Mevcut Durumu Tespit Etme:<\/strong><\/p>\n<pre><code class=\"language-sql\">FLUSH TABLES WITH READ LOCK; -- Okuma kilidi, tutarl\u0131 bir yedek almak i\u00e7in\n    SHOW MASTER STATUS;<\/code><\/pre>\n<p>    Bu komutun \u00e7\u0131kt\u0131s\u0131n\u0131 not al\u0131n (File ve Position de\u011ferleri). \u00d6rne\u011fin:<br \/>\n    <code>File: mysql-bin.000001<\/code>, <code>Position: 12345<\/code><br \/>\n    Bu bilgiyi kaydettikten sonra kilitleri serbest b\u0131rak\u0131n:<\/p>\n<pre><code class=\"language-sql\">UNLOCK TABLES;<\/code><\/pre>\n<p>4.  <strong>Kaynak Veritaban\u0131n\u0131n \u0130lk Yede\u011fini Alma:<\/strong><br \/>\n    <code>mysqldump<\/code> ile veya fiziksel kopyalama ile kaynak veritaban\u0131n\u0131n tam bir yede\u011fini al\u0131n. <code>mysqldump<\/code> kullan\u0131yorsan\u0131z, <code>--master-data=2<\/code> yerine <code>--master-data=1<\/code> kullanmak, yedek dosyas\u0131n\u0131n ba\u015f\u0131na <code>CHANGE MASTER TO<\/code> komutunu ekler, ancak bu komutu manuel olarak ayarlayaca\u011f\u0131m\u0131z i\u00e7in \u00e7ok \u00f6nemli de\u011fil. <code>--single-transaction<\/code> kullanmay\u0131 unutmay\u0131n.<\/p>\n<pre><code class=\"language-bash\">mysqldump -u root -p --all-databases --single-transaction --routines --triggers --events | gzip > initial_backup.sql.gz<\/code><\/pre>\n<p>5.  <strong>Yede\u011fi Hedef Sunucuya Aktarma ve Geri Y\u00fckleme:<\/strong><br \/>\n    Yedek dosyas\u0131n\u0131 hedef sunucuya aktar\u0131n ve geri y\u00fckleyin (Y\u00f6ntem 1'deki gibi).<\/p>\n<pre><code class=\"language-bash\">scp \/path\/to\/initial_backup.sql.gz user@hedef_sunucu_ip:\/path\/to\/hedef\/dizin\/\n    gunzip < initial_backup.sql.gz | mysql -u root -p<\/code><\/pre>\n<p>6.  <strong>Hedef Sunucuyu Replikasyon K\u00f6lesi Olarak Yap\u0131land\u0131rma:<\/strong><br \/>\n    Hedef sunucuda <code>my.cnf<\/code> dosyas\u0131na a\u015fa\u011f\u0131daki ayarlar\u0131 ekleyin:<\/p>\n<pre><code class=\"language-ini\">[mysqld]\n    server_id = 2 # Kaynak sunucudan farkl\u0131 bir ID\n    log_bin = mysql-bin # E\u011fer master olarak da kullan\u0131lacaksa\n    binlog_format = ROW\n    relay_log = mysql-relay-bin\n    read_only = 1 # Ge\u00e7i\u015f s\u00fcresince veri yazmay\u0131 engellemek i\u00e7in<\/code><\/pre>\n<p>    MySQL servisini yeniden ba\u015flat\u0131n.<\/p>\n<pre><code class=\"language-bash\">sudo systemctl restart mysql<\/code><\/pre>\n<p>    Ard\u0131ndan MySQL istemcisinden a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n (3. ad\u0131mda not ald\u0131\u011f\u0131n\u0131z File ve Position de\u011ferlerini kullanarak):<\/p>\n<pre><code class=\"language-sql\">CHANGE MASTER TO\n    MASTER_HOST='kaynak_sunucu_ip',\n    MASTER_USER='replikasyon_kullanici',\n    MASTER_PASSWORD='sifre',\n    MASTER_LOG_FILE='mysql-bin.000001',\n    MASTER_LOG_POS=12345;\n\n    START SLAVE;<\/code><\/pre>\n<p>7.  <strong>Replikasyon Durumunu Kontrol Etme:<\/strong><br \/>\n    Hedef sunucuda replikasyonun d\u00fczg\u00fcn \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol edin:<\/p>\n<pre><code class=\"language-sql\">SHOW SLAVE STATUS\\G<\/code><\/pre>\n<p>    <code>Slave_IO_Running: Yes<\/code> ve <code>Slave_SQL_Running: Yes<\/code> oldu\u011fundan ve <code>Seconds_Behind_Master<\/code> de\u011ferinin <code>0<\/code> oldu\u011fundan emin olun.<br \/>\n8.  <strong>Uygulamalar\u0131 Yeni Sunucuya Y\u00f6nlendirme:<\/strong><br \/>\n    Replikasyon tamamen senkronize oldu\u011funda, uygulamalar\u0131n\u0131z\u0131 yeni (hedef) sunucuya y\u00f6nlendirin. Bu, uygulama yap\u0131land\u0131rma dosyalar\u0131ndaki veritaban\u0131 ba\u011flant\u0131 dizelerini de\u011fi\u015ftirmek anlam\u0131na gelir.<br \/>\n    *   Uygulamalar\u0131n\u0131z\u0131n ba\u011flant\u0131lar\u0131n\u0131 kaynak sunucudan hedef sunucuya y\u00f6nlendirmeden \u00f6nce, hedef sunucudaki <code>read_only = 1<\/code> ayar\u0131n\u0131 <code>read_only = 0<\/code> olarak de\u011fi\u015ftirip MySQL'i yeniden ba\u015flatman\u0131z gerekebilir, b\u00f6ylece hedef sunucuya yazma i\u015flemleri yap\u0131labilir.<br \/>\n    *   Bu ge\u00e7i\u015f s\u0131ras\u0131nda k\u0131sa bir kesinti ya\u015fanabilir.<br \/>\n9.  <strong>Eski Sunucuyu Devre D\u0131\u015f\u0131 B\u0131rakma:<\/strong><br \/>\n    Ge\u00e7i\u015f tamamland\u0131ktan ve yeni sunucunun istikrarl\u0131 \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olduktan sonra, eski (kaynak) sunucudaki replikasyonu durdurabilir ve MySQL servisini kapatabilirsiniz.<\/p>\n<h5>Avantajlar ve Dezavantajlar<\/h5>\n<p>*   <strong>Avantajlar:<\/strong> Minimum veya s\u0131f\u0131r kesinti s\u00fcresi, b\u00fcy\u00fck ve dinamik veritabanlar\u0131 i\u00e7in ideal, ge\u00e7i\u015f s\u0131ras\u0131nda veri kayb\u0131 riski \u00e7ok d\u00fc\u015f\u00fck.<br \/>\n*   <strong>Dezavantajlar:<\/strong> Kurulumu di\u011fer y\u00f6ntemlere g\u00f6re daha karma\u015f\u0131k, iki sunucunun da replikasyon i\u00e7in yap\u0131land\u0131r\u0131lmas\u0131 gerekir, replikasyon gecikmeleri izlenmelidir.<\/p>\n<h4>Y\u00f6ntem 4: Bulut Sa\u011flay\u0131c\u0131lar\u0131n Ara\u00e7lar\u0131 (AWS DMS, Azure Database Migration Service)<\/h4>\n<p>E\u011fer bulut ortam\u0131na ge\u00e7i\u015f yap\u0131yorsan\u0131z veya bulutlar aras\u0131 bir ta\u015f\u0131ma ger\u00e7ekle\u015ftiriyorsan\u0131z, bulut sa\u011flay\u0131c\u0131lar\u0131n\u0131n sundu\u011fu y\u00f6netilen ta\u015f\u0131ma hizmetleri s\u00fcreci b\u00fcy\u00fck \u00f6l\u00e7\u00fcde basitle\u015ftirebilir.<\/p>\n<h5>Ne Zaman Kullan\u0131l\u0131r?<\/h5>\n<p>*   Yerel (on-premise) bir MySQL sunucusundan AWS RDS, Azure Database for MySQL veya Google Cloud SQL gibi y\u00f6netilen bir bulut veritaban\u0131 hizmetine ge\u00e7i\u015f yaparken.<br \/>\n*   Bir bulut sa\u011flay\u0131c\u0131s\u0131ndan di\u011ferine ge\u00e7i\u015f yaparken.<br \/>\n*   Karma\u015f\u0131k veri d\u00f6n\u00fc\u015f\u00fcmleri veya s\u00fcrekli replikasyon gerektiren senaryolarda.<\/p>\n<h5>Genel Yakla\u015f\u0131m<\/h5>\n<p>1.  <strong>Kaynak ve Hedef U\u00e7 Noktalar\u0131 Tan\u0131mlama:<\/strong> Bulut ta\u015f\u0131ma servisinde (\u00f6rne\u011fin, AWS Database Migration Service - DMS), kaynak MySQL veritaban\u0131n\u0131z\u0131n ve hedef bulut veritaban\u0131n\u0131z\u0131n (\u00f6rne\u011fin, AWS RDS for MySQL) ba\u011flant\u0131 bilgilerini tan\u0131mlars\u0131n\u0131z.<br \/>\n2.  <strong>Ge\u00e7i\u015f G\u00f6revi Olu\u015fturma:<\/strong> Tam y\u00fck ge\u00e7i\u015fi (full load) ve\/veya s\u00fcrekli replikasyon (CDC - Change Data Capture) i\u00e7eren bir ge\u00e7i\u015f g\u00f6revi olu\u015fturursunuz. S\u00fcrekli replikasyon, veritaban\u0131 ta\u015f\u0131ma s\u0131ras\u0131nda kaynak veritaban\u0131ndaki de\u011fi\u015fiklikleri hedef veritaban\u0131na aktarmaya devam eder, b\u00f6ylece kesinti s\u00fcresi minimuma iner.<br \/>\n3.  <strong>\u0130zleme ve Do\u011frulama:<\/strong> Ge\u00e7i\u015f g\u00f6revini ba\u015flat\u0131r ve ilerlemesini izlersiniz. Veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc do\u011frulamak i\u00e7in kontroller yapars\u0131n\u0131z.<br \/>\n4.  <strong>Kesme ve Ge\u00e7i\u015f:<\/strong> Replikasyon tamamen senkronize oldu\u011funda, uygulamalar\u0131n\u0131z\u0131 yeni bulut veritaban\u0131na y\u00f6nlendirirsiniz.<\/p>\n<h5>Avantajlar ve Dezavantajlar<\/h5>\n<p>*   <strong>Avantajlar:<\/strong> Otomatikle\u015ftirilmi\u015f ve y\u00f6netilen bir s\u00fcre\u00e7, minimum kesinti s\u00fcresi, karma\u015f\u0131k senaryolar\u0131 destekler (veri d\u00f6n\u00fc\u015f\u00fcm\u00fc gibi), g\u00fcvenlik ve \u00f6l\u00e7eklenebilirlik avantajlar\u0131.<br \/>\n*   <strong>Dezavantajlar:<\/strong> Maliyetli olabilir (servis kullan\u0131m\u0131na ba\u011fl\u0131 olarak), belirli bir bulut sa\u011flay\u0131c\u0131s\u0131na ba\u011f\u0131ml\u0131l\u0131k, bulut platformunun \u00f6\u011frenme e\u011frisi.<\/p>\n<h3>Ta\u015f\u0131ma Sonras\u0131 Kontroller ve Optimizasyonlar: Ba\u015far\u0131l\u0131 Bir Ge\u00e7i\u015fin Teyidi<\/h3>\n<p>Veritaban\u0131 ba\u015far\u0131yla yeni sunucuya ta\u015f\u0131nd\u0131ktan sonra, her \u015feyin beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in bir dizi kontrol ve optimizasyon ad\u0131m\u0131 uygulamak \u00f6nemlidir.<\/p>\n<h4>Veri B\u00fct\u00fcnl\u00fc\u011f\u00fc Kontrol\u00fc<\/h4>\n<p>*   <strong>Sat\u0131r Say\u0131s\u0131 Kar\u015f\u0131la\u015ft\u0131rmas\u0131:<\/strong> Kaynak ve hedef veritabanlar\u0131ndaki her tablonun sat\u0131r say\u0131lar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<pre><code class=\"language-sql\">SELECT table_name, table_rows FROM information_schema.tables WHERE table_schema = 'your_database_name';<\/code><\/pre>\n<p>*   <strong>Sa\u011flama Toplamlar\u0131 (Checksums):<\/strong> B\u00fcy\u00fck tablolar i\u00e7in <code>CHECKSUM TABLE<\/code> komutunu kullanarak veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc kontrol edebilirsiniz.<\/p>\n<pre><code class=\"language-sql\">CHECKSUM TABLE your_table_name;<\/code><\/pre>\n<p>    Ancak, bu komut b\u00fcy\u00fck tablolar \u00fczerinde yava\u015f \u00e7al\u0131\u015fabilir ve performans\u0131 etkileyebilir. Daha geli\u015fmi\u015f ara\u00e7lar (\u00f6rne\u011fin, <code>pt-table-checksum<\/code> Percona Toolkit'ten) daha kapsaml\u0131 kar\u015f\u0131la\u015ft\u0131rmalar yapabilir.<br \/>\n*   <strong>\u00d6rnek Veri Sorgulama:<\/strong> Kritik tablolardan rastgele \u00f6rnek veriler \u00e7ekerek ve kar\u015f\u0131la\u015ft\u0131rarak g\u00f6rsel bir do\u011frulama yap\u0131n.<\/p>\n<h4>Uygulama Ba\u011flant\u0131lar\u0131n\u0131n G\u00fcncellenmesi<\/h4>\n<p>Uygulamalar\u0131n\u0131z\u0131n, web sunucular\u0131n\u0131z\u0131n ve di\u011fer servislerinizin veritaban\u0131 ba\u011flant\u0131 dizelerini (hostname, IP adresi, port) yeni MySQL sunucusuna i\u015faret edecek \u015fekilde g\u00fcncelleyin. Bu, uygulaman\u0131n \u00e7al\u0131\u015fmaya ba\u015flamas\u0131 i\u00e7in kritik bir ad\u0131md\u0131r. G\u00fcncelleme sonras\u0131 uygulamalar\u0131 yeniden ba\u015flatmay\u0131 unutmay\u0131n.<\/p>\n<h4>Kullan\u0131c\u0131 ve Yetkilendirme Kontrol\u00fc<\/h4>\n<p>T\u00fcm MySQL kullan\u0131c\u0131lar\u0131n\u0131n ve onlar\u0131n veritaban\u0131, tablo ve s\u00fctun seviyesindeki yetkilerinin yeni sunucuda do\u011fru bir \u015fekilde aktar\u0131ld\u0131\u011f\u0131ndan veya yeniden olu\u015fturuldu\u011fundan emin olun.<\/p>\n<pre><code class=\"language-sql\">SELECT user, host FROM mysql.user;\nSHOW GRANTS FOR 'your_user'@'your_host';<\/code><\/pre>\n<h4>Performans Testleri<\/h4>\n<p>Yeni sunucunun performans\u0131, kaynak sunucuya g\u00f6re nas\u0131l?<br \/>\n*   <strong>Temel Performans Metrikleri:<\/strong> CPU kullan\u0131m\u0131, bellek t\u00fcketimi, disk I\/O, a\u011f trafi\u011fi gibi sunucu kaynaklar\u0131n\u0131 izleyin.<br \/>\n*   <strong>Veritaban\u0131 Performans Metrikleri:<\/strong> MySQL durum de\u011fi\u015fkenlerini (<code>SHOW STATUS;<\/code>) ve yava\u015f sorgu g\u00fcnl\u00fcklerini (<code>slow_query_log<\/code>) inceleyin.<br \/>\n*   <strong>Y\u00fck Testleri:<\/strong> Uygulamalar\u0131n\u0131za ger\u00e7ek d\u00fcnya y\u00fck senaryolar\u0131n\u0131 uygulayarak performans testleri yap\u0131n.<\/p>\n<h4>MySQL Yap\u0131land\u0131rma Optimizasyonu<\/h4>\n<p>Yeni sunucunun donan\u0131m \u00f6zelliklerine (RAM miktar\u0131, CPU \u00e7ekirdek say\u0131s\u0131, disk tipi) ve uygulaman\u0131z\u0131n i\u015f y\u00fck\u00fcne g\u00f6re <code>my.cnf<\/code> dosyas\u0131ndaki MySQL yap\u0131land\u0131rma parametrelerini optimize edin. \u00d6zellikle a\u015fa\u011f\u0131daki parametreler \u00f6nemlidir:<br \/>\n*   <code>innodb_buffer_pool_size<\/code>: InnoDB tablolar\u0131 i\u00e7in en \u00f6nemli performans parametresi. Genellikle toplam RAM'in %50-70'i kadar ayarlan\u0131r.<br \/>\n*   <code>innodb_log_file_size<\/code>: InnoDB redo log dosyalar\u0131n\u0131n boyutu.<br \/>\n*   <code>max_connections<\/code>: Maksimum e\u015f zamanl\u0131 ba\u011flant\u0131 say\u0131s\u0131.<br \/>\n*   <code>query_cache_size<\/code> (MySQL 8.0 ve \u00fczeri i\u00e7in kald\u0131r\u0131lm\u0131\u015ft\u0131r): Sorgu \u00f6nbelle\u011fi boyutu (eski s\u00fcr\u00fcmler i\u00e7in).<br \/>\n*   <code>tmp_table_size<\/code>, <code>max_heap_table_size<\/code>: Bellek i\u00e7i ge\u00e7ici tablolar\u0131n boyutu.<br \/>\n*   <code>thread_cache_size<\/code>: \u0130\u015f par\u00e7ac\u0131\u011f\u0131 \u00f6nbelle\u011fi boyutu.<\/p>\n<h4>\u0130zleme ve G\u00fcnl\u00fckleme<\/h4>\n<p>Yeni sunucuda MySQL performans\u0131n\u0131, hata g\u00fcnl\u00fcklerini ve genel sistem sa\u011fl\u0131\u011f\u0131n\u0131 s\u00fcrekli izlemek i\u00e7in izleme ara\u00e7lar\u0131 (Prometheus, Grafana, Zabbix vb.) kurun ve yap\u0131land\u0131r\u0131n.<\/p>\n<h4>Eski Sunucunun Devre D\u0131\u015f\u0131 B\u0131rak\u0131lmas\u0131<\/h4>\n<p>Yeni sunucunun sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan ve t\u00fcm kontrollerin yap\u0131ld\u0131\u011f\u0131ndan emin olduktan sonra, eski MySQL sunucusunu g\u00fcvenli bir \u015fekilde kapat\u0131n ve yedekleme amac\u0131yla belirli bir s\u00fcre saklay\u0131n.<\/p>\n<h3>S\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar ve \u00c7\u00f6z\u00fcmleri<\/h3>\n<p>Veritaban\u0131 ta\u015f\u0131ma s\u00fcre\u00e7lerinde kar\u015f\u0131la\u015f\u0131labilecek baz\u0131 yayg\u0131n sorunlar ve bunlara y\u00f6nelik \u00e7\u00f6z\u00fcmler \u015funlard\u0131r:<\/p>\n<p>*   <strong>Karakter Seti Uyu\u015fmazl\u0131klar\u0131:<\/strong><br \/>\n    *   <strong>Sorun:<\/strong> Kaynak ve hedef sunuculardaki veya veritabanlar\u0131ndaki karakter setleri (charset) ve harmanlama (collation) ayarlar\u0131n\u0131n farkl\u0131 olmas\u0131, veri bozulmalar\u0131na veya yanl\u0131\u015f karakter g\u00f6sterimlerine yol a\u00e7abilir.<br \/>\n    *   <strong>\u00c7\u00f6z\u00fcm:<\/strong> Ta\u015f\u0131ma \u00f6ncesinde kaynak veritaban\u0131n\u0131n karakter setini ve harmanlamas\u0131n\u0131 belirleyin. Hedef sunucuda veritaban\u0131n\u0131 olu\u015ftururken ayn\u0131 karakter seti ve harmanlamay\u0131 kullan\u0131n (<code>CREATE DATABASE myapp_db CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;<\/code>). <code>mysqldump<\/code> yaparken <code>--default-character-set=utf8mb4<\/code> gibi parametreler kullanmak da yard\u0131mc\u0131 olabilir.<br \/>\n*   <strong>MySQL S\u00fcr\u00fcm Farkl\u0131l\u0131klar\u0131:<\/strong><br \/>\n    *   <strong>Sorun:<\/strong> B\u00fcy\u00fck s\u00fcr\u00fcm farkl\u0131l\u0131klar\u0131 (\u00f6rn. 5.6'dan 8.0'a) uyumluluk sorunlar\u0131na, eski \u00f6zelliklerin kald\u0131r\u0131lmas\u0131na veya yeni \u00f6zelliklerin beklenmedik davran\u0131\u015flar\u0131na neden olabilir.<br \/>\n    *   <strong>\u00c7\u00f6z\u00fcm:<\/strong> M\u00fcmk\u00fcnse ayn\u0131 veya yak\u0131n s\u00fcr\u00fcmler aras\u0131nda ta\u015f\u0131ma yap\u0131n. B\u00fcy\u00fck s\u00fcr\u00fcm y\u00fckseltmelerinde, \u00f6nce ara s\u00fcr\u00fcmlere y\u00fckseltme yapmay\u0131 (\u00f6rn. 5.6 -> 5.7 -> 8.0) veya <code>mysql_upgrade<\/code> gibi ara\u00e7lar\u0131 kullanmay\u0131 d\u00fc\u015f\u00fcn\u00fcn. Her s\u00fcr\u00fcm y\u00fckseltmesinde MySQL dok\u00fcmantasyonunu dikkatlice okuyun.<br \/>\n*   <strong>Disk Alan\u0131 Yetersizli\u011fi:<\/strong><br \/>\n    *   <strong>Sorun:<\/strong> Yedekleme dosyalar\u0131 veya geri y\u00fckleme s\u0131ras\u0131nda ge\u00e7ici dosyalar i\u00e7in yeterli disk alan\u0131 olmamas\u0131.<br \/>\n    *   <strong>\u00c7\u00f6z\u00fcm:<\/strong> Ta\u015f\u0131ma \u00f6ncesinde hem kaynak hem de hedef sunucularda yeterli disk alan\u0131 oldu\u011fundan emin olun. Yedek dosyalar\u0131n\u0131 s\u0131k\u0131\u015ft\u0131r\u0131n (<code>gzip<\/code>). Geri y\u00fckleme s\u0131ras\u0131nda <code>tmpdir<\/code> ayar\u0131n\u0131 daha geni\u015f bir diske i\u015faret edecek \u015fekilde de\u011fi\u015ftirebilirsiniz.<br \/>\n*   <strong>A\u011f Ba\u011flant\u0131s\u0131 Sorunlar\u0131:<\/strong><br \/>\n    *   <strong>Sorun:<\/strong> Sunucular aras\u0131 yava\u015f veya kesintili a\u011f ba\u011flant\u0131s\u0131, veri aktar\u0131m\u0131n\u0131 yava\u015flat\u0131r veya kesintiye u\u011frat\u0131r. G\u00fcvenlik duvar\u0131 (firewall) portlar\u0131 kapal\u0131 olabilir.<br \/>\n    *   <strong>\u00c7\u00f6z\u00fcm:<\/strong> A\u011f ba\u011flant\u0131s\u0131n\u0131n h\u0131z\u0131n\u0131 ve kararl\u0131l\u0131\u011f\u0131n\u0131 kontrol edin. <code>rsync<\/code> gibi ara\u00e7lar, kesintiye u\u011frayan aktar\u0131mlar\u0131 kald\u0131\u011f\u0131 yerden devam ettirebilir. Gerekli portlar\u0131n (\u00f6rn. 3306, 22) g\u00fcvenlik duvar\u0131nda a\u00e7\u0131k oldu\u011fundan emin olun.<br \/>\n*   <strong>\u0130zin Sorunlar\u0131:<\/strong><br \/>\n    *   <strong>Sorun:<\/strong> MySQL kullan\u0131c\u0131 izinlerinin veya dosya sistemi izinlerinin yetersiz olmas\u0131.<br \/>\n    *   <strong>\u00c7\u00f6z\u00fcm:<\/strong> MySQL root kullan\u0131c\u0131s\u0131 veya yeterli yetkilere sahip bir kullan\u0131c\u0131 ile i\u015flem yap\u0131n. Fiziksel dosya kopyalamada, <code>datadir<\/code> i\u00e7indeki dosyalar\u0131n ve dizinlerin <code>mysql<\/code> kullan\u0131c\u0131s\u0131 ve grubuna ait oldu\u011fundan emin olun (<code>chown -R mysql:mysql \/var\/lib\/mysql<\/code>).<br \/>\n*   <strong>Zaman A\u015f\u0131m\u0131 Hatalar\u0131:<\/strong><br \/>\n    *   <strong>Sorun:<\/strong> B\u00fcy\u00fck yedek dosyalar\u0131n\u0131n geri y\u00fcklenmesi s\u0131ras\u0131nda MySQL istemcisinin veya sunucusunun zaman a\u015f\u0131m\u0131na u\u011framas\u0131.<br \/>\n    *   <strong>\u00c7\u00f6z\u00fcm:<\/strong> MySQL istemcisinde <code>wait_timeout<\/code> gibi ayarlar\u0131 art\u0131r\u0131n. <code>mysqldump<\/code> ve <code>mysql<\/code> komutlar\u0131n\u0131 <code>nohup<\/code> veya <code>screen<\/code>\/<code>tmux<\/code> gibi ara\u00e7larla \u00e7al\u0131\u015ft\u0131rarak SSH oturumunun kapanmas\u0131ndan etkilenmemesini sa\u011flay\u0131n.<\/p>\n<h3>Sonu\u00e7: Ba\u015far\u0131l\u0131 Bir MySQL Veritaban\u0131 Ta\u015f\u0131mas\u0131 \u0130\u00e7in Anahtarlar<\/h3>\n<p>MySQL veritaban\u0131n\u0131 iki sunucu aras\u0131nda ta\u015f\u0131mak, dikkatli planlama, do\u011fru ara\u00e7 se\u00e7imi ve titiz uygulama gerektiren kritik bir s\u00fcre\u00e7tir. Bu rehberde ele al\u0131nan ad\u0131mlar\u0131 ve y\u00f6ntemleri takip ederek, olas\u0131 riskleri en aza indirebilir ve ba\u015far\u0131l\u0131 bir ge\u00e7i\u015f sa\u011flayabilirsiniz.<\/p>\n<p>Unutulmamas\u0131 gereken temel noktalar \u015funlard\u0131r:<\/p>\n<p>1.  <strong>Kapsaml\u0131 Planlama:<\/strong> Ta\u015f\u0131ma \u00f6ncesi haz\u0131rl\u0131klar, kesinti s\u00fcresi planlamas\u0131 ve geri d\u00f6n\u00fc\u015f stratejisi olu\u015fturmak, ba\u015far\u0131n\u0131n anahtar\u0131d\u0131r.<br \/>\n2.  <strong>Yedekleme ve Do\u011frulama:<\/strong> Herhangi bir ta\u015f\u0131ma i\u015flemine ba\u015flamadan \u00f6nce mutlaka tam ve do\u011frulanm\u0131\u015f bir yedek al\u0131n.<br \/>\n3.  <strong>Do\u011fru Y\u00f6ntem Se\u00e7imi:<\/strong> Veritaban\u0131n\u0131n boyutu, kesinti s\u00fcresi tolerans\u0131 ve kaynak\/hedef ortam uyumlulu\u011funa g\u00f6re en uygun ta\u015f\u0131ma y\u00f6ntemini se\u00e7in. K\u00fc\u00e7\u00fck veritabanlar\u0131 i\u00e7in <code>mysqldump<\/code> basit ve etkilidir; b\u00fcy\u00fck veritabanlar\u0131 ve minimum kesinti s\u00fcresi i\u00e7in fiziksel kopyalama veya replikasyon daha uygun olabilir.<br \/>\n4.  <strong>Test Etme:<\/strong> M\u00fcmk\u00fcnse, ta\u015f\u0131ma i\u015flemini bir test ortam\u0131nda ba\u015ftan sona sim\u00fcle edin.<br \/>\n5.  <strong>Ta\u015f\u0131ma Sonras\u0131 Kontroller:<\/strong> Veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc, uygulama ba\u011flant\u0131lar\u0131n\u0131 ve performans\u0131 dikkatlice do\u011frulay\u0131n.<br \/>\n6.  <strong>Optimizasyon:<\/strong> Yeni sunucunun donan\u0131m\u0131na ve i\u015f y\u00fck\u00fcne g\u00f6re MySQL yap\u0131land\u0131rmas\u0131n\u0131 optimize edin.<\/p>\n<p>Bu ad\u0131mlar\u0131 izleyerek, MySQL veritaban\u0131 ta\u015f\u0131ma i\u015fleminizi g\u00fcvenle ger\u00e7ekle\u015ftirebilir ve sistemlerinizin kesintisiz \u00e7al\u0131\u015fmaya devam etmesini sa\u011flayabilirsiniz.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi\nMySQL veritabanlar\u0131, modern web uygulamalar\u0131n\u0131n ve kurumsal sistemlerin belkemi\u011fini o","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[138],"tags":[],"class_list":{"0":"post-35270","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-mysql","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi\" \/>\n<meta property=\"og:description\" content=\"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi MySQL veritabanlar\u0131, modern web uygulamalar\u0131n\u0131n ve kurumsal sistemlerin belkemi\u011fini o\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-27T15:40:57+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"23 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi\",\"datePublished\":\"2025-11-27T15:40:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\"},\"wordCount\":3825,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"MySQL\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\",\"name\":\"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-11-27T15:40:57+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/","og_locale":"tr_TR","og_type":"article","og_title":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi","og_description":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi MySQL veritabanlar\u0131, modern web uygulamalar\u0131n\u0131n ve kurumsal sistemlerin belkemi\u011fini o","og_url":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-11-27T15:40:57+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"23 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi","datePublished":"2025-11-27T15:40:57+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/"},"wordCount":3825,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["MySQL"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/","url":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/","name":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-11-27T15:40:57+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-veritabanini-iki-sunucu-arasinda-tasima-rehberi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MySQL Veritaban\u0131n\u0131 \u0130ki Sunucu Aras\u0131nda Ta\u015f\u0131ma Rehberi"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/35270","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=35270"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/35270\/revisions"}],"predecessor-version":[{"id":35271,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/35270\/revisions\/35271"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=35270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=35270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=35270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}