{"id":5934,"date":"2026-06-16T16:15:28","date_gmt":"2026-06-16T16:15:28","guid":{"rendered":"https:\/\/cloudsave.app\/knowledge-base\/mssql-transaction-log-full-recovery\/"},"modified":"2026-06-16T17:13:53","modified_gmt":"2026-06-16T17:13:53","slug":"mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri","status":"publish","type":"post","link":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/","title":{"rendered":"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri"},"content":{"rendered":"

Microsoft SQL Server y\u00f6neten Veritaban\u0131 Y\u00f6neticileri (DBA’lar) ve DevOps m\u00fchendisleri i\u00e7in, Hata 9002: ‘X’ veritaban\u0131 i\u00e7in i\u015flem g\u00fcnl\u00fc\u011f\u00fc (transaction log) dolu<\/em> uyar\u0131s\u0131 kadar an\u0131nda endi\u015fe yaratan \u00e7ok az uyar\u0131 vard\u0131r. \u0130\u015flem g\u00fcnl\u00fc\u011f\u00fc doldu\u011funda ve geni\u015fleyemedi\u011finde, veritaban\u0131 fiilen salt okunur hale gelir. T\u00fcm INSERT<\/code>, UPDATE<\/code> ve DELETE<\/code> i\u015flemleri durur, uygulama i\u015flemleri ba\u015far\u0131s\u0131z olur ve \u00fcretim s\u00fcreci durma noktas\u0131na gelir.<\/p>\n

SQL Server i\u015flem g\u00fcnl\u00fc\u011f\u00fc mimarisini anlamak, k\u00f6k nedeni do\u011fru bir \u015fekilde te\u015fhis etmek ve h\u0131zl\u0131 kurtarma prosed\u00fcrlerini uygulamak, y\u00fcksek eri\u015filebilirli\u011fi s\u00fcrd\u00fcrmek i\u00e7in kritik becerilerdir. Bu kapsaml\u0131 k\u0131lavuz, i\u015flem g\u00fcnl\u00fc\u011f\u00fcn\u00fcn mekani\u011fini, acil bir durumda dolu bir g\u00fcnl\u00fc\u011f\u00fcn nas\u0131l \u00e7\u00f6z\u00fclece\u011fini ve bunun tekrar ya\u015fanmas\u0131n\u0131 \u00f6nlemek i\u00e7in mimari en iyi uygulamalar\u0131 incelemektedir.<\/p>\n

SQL Server \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Mimarisi<\/h2>\n

Dolu bir i\u015flem g\u00fcnl\u00fc\u011f\u00fcnde sorun gidermek i\u00e7in, \u00f6nce SQL Server’\u0131n verileri nas\u0131l yazd\u0131\u011f\u0131n\u0131 ve y\u00f6netti\u011fini anlaman\u0131z gerekir.<\/p>\n

\u00d6nceden Yazma G\u00fcnl\u00fc\u011f\u00fc (Write-Ahead Logging – WAL)<\/h3>\n

SQL Server, \u00d6nceden Yazma G\u00fcnl\u00fc\u011f\u00fc (WAL) protokol\u00fcn\u00fc kullan\u0131r. Bir veri de\u011fi\u015fikli\u011fi ger\u00e7ekle\u015fti\u011finde, de\u011fi\u015fiklik \u00f6nce bellekteki i\u015flem g\u00fcnl\u00fc\u011f\u00fcne yaz\u0131l\u0131r, ard\u0131ndan veritaban\u0131 dosyalar\u0131ndaki (MDF\/NDF) ger\u00e7ek veri sayfalar\u0131 g\u00fcncellenmeden \u00f6nce diskteki fiziksel g\u00fcnl\u00fck dosyas\u0131na aktar\u0131l\u0131r. Bu, ACID (Atomiklik, Tutarl\u0131l\u0131k, \u0130zolasyon, Dayan\u0131kl\u0131l\u0131k) uyumlulu\u011funu garanti eder ve bir \u00e7\u00f6kme durumunda SQL Server’\u0131n i\u015flemleri yeniden oynatabilmesini (ileri sarma) veya geri alabilmesini (geri alma) sa\u011flar.<\/p>\n

Sanal G\u00fcnl\u00fck Dosyalar\u0131 (VLF) ve D\u00f6ng\u00fcsel G\u00fcnl\u00fckleme<\/h3>\n

Dahili olarak, fiziksel i\u015flem g\u00fcnl\u00fc\u011f\u00fc dosyas\u0131 (LDF), Sanal G\u00fcnl\u00fck Dosyalar\u0131 (VLF) ad\u0131 verilen daha k\u00fc\u00e7\u00fck, mant\u0131ksal b\u00f6l\u00fcmlere ayr\u0131lm\u0131\u015ft\u0131r. \u0130\u015flem g\u00fcnl\u00fc\u011f\u00fc d\u00f6ng\u00fcsel olarak \u00e7al\u0131\u015f\u0131r. G\u00fcnl\u00fck kay\u0131tlar\u0131 yaz\u0131ld\u0131k\u00e7a, bir VLF’yi doldurur ve bir sonrakine ge\u00e7er.<\/p>\n

G\u00fcnl\u00fck, fiziksel dosyan\u0131n sonuna ula\u015ft\u0131\u011f\u0131nda, ba\u015fa d\u00f6nmeye \u00e7al\u0131\u015f\u0131r. Ancak, bir VLF’nin \u00fczerine yaln\u0131zca o VLF etkin de\u011fil<\/strong> (inactive) olarak i\u015faretlenmi\u015fse yazabilir. T\u00fcm VLF’ler etkinse (yani SQL Server taraf\u0131ndan hala ihtiya\u00e7 duyulan g\u00fcnl\u00fck kay\u0131tlar\u0131n\u0131 i\u00e7eriyorlarsa), g\u00fcnl\u00fck ba\u015fa d\u00f6nemez. Otomatik b\u00fcy\u00fcme (auto-growth) etkinse ve disk alan\u0131 mevcutsa, fiziksel dosya b\u00fcy\u00fcr. Disk doluysa veya otomatik b\u00fcy\u00fcme k\u0131s\u0131tlanm\u0131\u015fsa, Hata 9002 ile kar\u015f\u0131la\u015f\u0131rs\u0131n\u0131z.<\/p>\n

G\u00fcnl\u00fck K\u0131rpma (Truncation) vs. G\u00fcnl\u00fck K\u00fc\u00e7\u00fcltme (Shrinking)<\/h3>\n

Yayg\u0131n bir yanl\u0131\u015f kan\u0131, g\u00fcnl\u00fc\u011f\u00fc k\u0131rpman\u0131n fiziksel dosya boyutunu k\u00fc\u00e7\u00fcltt\u00fc\u011f\u00fcd\u00fcr.
\n* G\u00fcnl\u00fck K\u0131rpma (Log Truncation):<\/strong> Etkin VLF’leri etkin de\u011fil olarak i\u015faretleme ve alan\u0131 yeniden kullan\u0131m i\u00e7in uygun hale getirme i\u015flemidir. Disk \u00fczerindeki LDF dosyas\u0131n\u0131n boyutunu k\u00fc\u00e7\u00fcltmez<\/em>.
\n* G\u00fcnl\u00fck K\u00fc\u00e7\u00fcltme (Log Shrinking):<\/strong> LDF dosya boyutunu fiziksel olarak azaltma ve alan\u0131 i\u015fletim sistemine geri verme i\u015flemidir.<\/p>\n

Tam (Full) Kurtarma modelinde, g\u00fcnl\u00fck k\u0131rpma yaln\u0131zca<\/em> bir i\u015flem g\u00fcnl\u00fc\u011f\u00fc yede\u011fi ba\u015far\u0131yla tamamland\u0131\u011f\u0131nda ger\u00e7ekle\u015fir (g\u00fcnl\u00fc\u011f\u00fc etkin tutan ba\u015fka bir i\u015flem olmad\u0131\u011f\u0131n\u0131 varsayarsak).<\/p>\n

“\u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu” Hatas\u0131n\u0131 (Hata 9002) Te\u015fhis Etme<\/h2>\n

G\u00fcnl\u00fck doldu\u011funda, ilk ad\u0131m\u0131n\u0131z k\u00f6r\u00fc k\u00f6r\u00fcne disk alan\u0131 eklemek veya dosyalar\u0131 k\u00fc\u00e7\u00fcltmek olmamal\u0131d\u0131r. G\u00fcnl\u00fc\u011f\u00fcn neden k\u0131rp\u0131lamad\u0131\u011f\u0131n\u0131 belirlemelisiniz. SQL Server, sys.databases<\/code> katalog g\u00f6r\u00fcn\u00fcm\u00fc arac\u0131l\u0131\u011f\u0131yla g\u00fcnl\u00fc\u011f\u00fcn yeniden kullan\u0131lmas\u0131n\u0131 neyin engelledi\u011fini size tam olarak s\u00f6yleyen yerle\u015fik bir mekanizma sa\u011flar.<\/p>\n

Darbo\u011faz\u0131 belirlemek i\u00e7in a\u015fa\u011f\u0131daki T-SQL komutunu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n

SELECT \n    name AS DatabaseName, \n    recovery_model_desc AS RecoveryModel, \n    log_reuse_wait_desc AS LogReuseWaitReason\nFROM sys.databases\nWHERE name = 'YourDatabaseName';\n<\/code><\/pre>\n
Ayr\u0131ca i\u015flem g\u00fcnl\u00fcklerinizin mevcut alan kullan\u0131m\u0131n\u0131 \u015fu \u015fekilde kontrol edebilirsiniz:<\/p>\n
DBCC SQLPERF(LOGSPACE);\n<\/code><\/pre>\n
Yayg\u0131n log_reuse_wait_desc<\/code> Durumlar\u0131<\/h3>\n
    \n
  1. LOG_BACKUP:<\/strong> Veritaban\u0131 Tam veya Toplu G\u00fcnl\u00fckl\u00fc (Bulk-Logged) kurtarma modelindedir ve yak\u0131n zamanda bir i\u015flem g\u00fcnl\u00fc\u011f\u00fc yede\u011fi al\u0131nmam\u0131\u015ft\u0131r. Bu en yayg\u0131n nedendir.<\/li>\n
  2. ACTIVE_TRANSACTION:<\/strong> Uzun s\u00fcren bir i\u015flem (\u00f6rne\u011fin, b\u00fcy\u00fck bir dizin yeniden olu\u015fturma veya unutulmu\u015f, tamamlanmam\u0131\u015f bir i\u015flem) g\u00fcnl\u00fc\u011f\u00fc etkin tutuyordur.<\/li>\n
  3. REPLICATION \/ CDC:<\/strong> \u0130\u015flemsel \u00c7o\u011faltma (Transactional Replication) veya De\u011fi\u015fiklik Verisi Yakalama (CDC) etkindir ve G\u00fcnl\u00fck Okuyucu Arac\u0131s\u0131 (Log Reader Agent) i\u015flemleri hen\u00fcz i\u015flememi\u015ftir.<\/li>\n
  4. AVAILABILITY_REPLICA:<\/strong> AlwaysOn Kullan\u0131labilirlik Grubunda, ikincil bir kopya ba\u011flant\u0131s\u0131 kesilmi\u015f veya \u00e7ok yava\u015f senkronize oluyor, bu da birincil kopyay\u0131 g\u00fcnl\u00fck kay\u0131tlar\u0131n\u0131 ikincil kopya \u00fczerinde sertle\u015fene kadar tutmaya zorluyor.<\/li>\n<\/ol>\n
    H\u0131zl\u0131 Kurtarma Stratejileri: Sorunu \u00dcretimde \u00c7\u00f6zme<\/h2>\n
    D\u00f6nd\u00fcr\u00fclen log_reuse_wait_desc<\/code> de\u011ferine ba\u011fl\u0131 olarak, acil durum yan\u0131t\u0131n\u0131z de\u011fi\u015fecektir. En yayg\u0131n senaryolar i\u00e7in h\u0131zl\u0131 kurtarma stratejileri \u015funlard\u0131r.<\/p>\n
    Senaryo 1: Eksik veya Ba\u015far\u0131s\u0131z G\u00fcnl\u00fck Yedekleri (LOG_BACKUP<\/code>)<\/h3>\n
    Bekleme t\u00fcr\u00fc LOG_BACKUP<\/code> ise, \u00e7\u00f6z\u00fcm basittir: i\u015flem g\u00fcnl\u00fc\u011f\u00fcn\u00fc yedeklemeniz gerekir.<\/p>\n
    BACKUP LOG [YourDatabaseName] \nTO DISK = 'N:BackupsYourDatabaseName_EmergencyLog.trn' \nWITH COMPRESSION, STATS = 10;\n<\/code><\/pre>\n
    Yedekleme tamamland\u0131\u011f\u0131nda, etkin olmayan VLF’ler k\u0131rp\u0131lacak ve SQL Server normal i\u015flemlerine devam edecektir. Yedekleme s\u00fcr\u00fcc\u00fcn\u00fcz doluysa, ge\u00e7ici bir a\u011f payla\u015f\u0131m\u0131na veya bir null cihaz\u0131na yedeklemeniz gerekebilir (veritaban\u0131 kolayca yeniden olu\u015fturulabilir de\u011filse, g\u00fcnl\u00fck zincirini k\u0131rd\u0131\u011f\u0131 i\u00e7in \u015fiddetle tavsiye edilmez):<\/p>\n
    -- UYARI: Bu, g\u00fcnl\u00fck zincirini k\u0131rar ve noktadan noktaya kurtarmay\u0131 tehlikeye atar.\n-- Sadece kesinlikle gerekliyse kullan\u0131n ve hemen ard\u0131ndan TAM yedekleme yap\u0131n.\nBACKUP LOG [YourDatabaseName] TO DISK = 'NUL';\n<\/code><\/pre>\n
    Senaryo 2: Uzun S\u00fcren Etkin \u0130\u015flemler (ACTIVE_TRANSACTION<\/code>)<\/h3>\n
    Tek bir i\u015flem saatlerce \u00e7al\u0131\u015f\u0131yorsa, t\u00fcm s\u00fcre boyunca g\u00fcnl\u00fck k\u0131rp\u0131lmas\u0131n\u0131 engeller. \u0130lk olarak, sorunlu i\u015flemi tan\u0131mlay\u0131n:<\/p>\n
    DBCC OPENTRAN('YourDatabaseName');\n<\/code><\/pre>\n
    Bu komut, en eski etkin i\u015flemi ve onun Sunucu \u0130\u015flem Kimli\u011fini (SPID) d\u00f6nd\u00fcr\u00fcr. Dinamik y\u00f6netim g\u00f6r\u00fcn\u00fcmlerini (DMV’ler) sorgulayarak SPID’nin ne yapt\u0131\u011f\u0131 hakk\u0131nda daha fazla ayr\u0131nt\u0131 toplayabilirsiniz:<\/p>\n
    SELECT \n    s.session_id,\n    s.login_name,\n    s.host_name,\n    r.start_time,\n    r.status,\n    r.command,\n    t.text AS QueryText\nFROM sys.dm_exec_sessions s\nJOIN sys.dm_exec_requests r ON s.session_id = r.session_id\nCROSS APPLY sys.dm_exec_sql_text(r.sql_handle) t\nWHERE s.session_id = <SPID_FROM_DBCC_OPENTRAN>;\n<\/code><\/pre>\n
    \u0130\u015flem hatal\u0131 bir sorgu veya durmu\u015f bir s\u00fcre\u00e7se, g\u00fcnl\u00fc\u011f\u00fc serbest b\u0131rakmak i\u00e7in onu sonland\u0131rman\u0131z gerekebilir.<\/p>\n
    KILL <SPID>;\n<\/code><\/pre>\n
    Not: B\u00fcy\u00fck bir i\u015flemi sonland\u0131rmak, \u00f6nemli miktarda zaman alabilen ve ge\u00e7ici olarak ek g\u00fcnl\u00fck etkinli\u011fi olu\u015fturacak bir geri alma i\u015flemini tetikleyecektir. Geri alma s\u0131ras\u0131nda SQL Server hizmetini yeniden ba\u015flatmay\u0131n, aksi takdirde veritaban\u0131 yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda kurtarma moduna girer.<\/em><\/p>\n
    Senaryo 3: Acil Durum Alan Tahsisi (Disk %100 Dolu)<\/h3>\n
    LDF dosyas\u0131 t\u00fcm s\u00fcr\u00fcc\u00fcy\u00fc t\u00fckettiyse, yedekleme bile yapamazs\u0131n\u0131z \u00e7\u00fcnk\u00fc SQL Server yedekleme olay\u0131n\u0131 kaydetmek i\u00e7in az miktarda g\u00fcnl\u00fck alan\u0131na ihtiya\u00e7 duyar. Bu senaryoda, kullan\u0131labilir alan\u0131 olan farkl\u0131 bir s\u00fcr\u00fcc\u00fcde ikincil bir g\u00fcnl\u00fck dosyas\u0131 eklemelisiniz.<\/p>\n
    ALTER DATABASE [YourDatabaseName]\nADD LOG FILE \n(\n    NAME = N'YourDatabaseName_Log2',\n    FILENAME = N'E:TempLogsYourDatabaseName_Log2.ldf',\n    SIZE = 5GB,\n    MAXSIZE = 50GB,\n    FILEGROWTH = 1GB\n);\n<\/code><\/pre>\n
    Bu, SQL Server’a an\u0131nda nefes alacak alan sa\u011flar. Veritaban\u0131 \u00e7evrimi\u00e7i oldu\u011funda, bir i\u015flem g\u00fcnl\u00fc\u011f\u00fc yede\u011fi al\u0131n, ikincil g\u00fcnl\u00fck dosyas\u0131n\u0131 bo\u015falt\u0131n ve kald\u0131r\u0131n:<\/p>\n
    -- 1. G\u00fcnl\u00fc\u011f\u00fc k\u0131rpmak i\u00e7in bir g\u00fcnl\u00fck yede\u011fi al\u0131n\nBACKUP LOG [YourDatabaseName] TO DISK = '...';\n\n-- 2. Ge\u00e7ici g\u00fcnl\u00fck dosyas\u0131n\u0131 bo\u015falt\u0131n\nDBCC SHRINKFILE (N'YourDatabaseName_Log2', EMPTYFILE);\n\n-- 3. Ge\u00e7ici g\u00fcnl\u00fck dosyas\u0131n\u0131 kald\u0131r\u0131n\nALTER DATABASE [YourDatabaseName] REMOVE FILE [YourDatabaseName_Log2];\n<\/code><\/pre>\n
    \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc \u00d6nleme ve Y\u00f6netimi \u0130\u00e7in En \u0130yi Uygulamalar<\/h2>\n
    Reaktif sorun giderme streslidir ve SLA’lar\u0131 etkiler. Kurumsal veritaban\u0131 kararl\u0131l\u0131\u011f\u0131 i\u00e7in proaktif mimari ve operasyonel en iyi uygulamalar\u0131 uygulamak esast\u0131r.<\/p>\n
    1. Sa\u011flam, Otomatik Bir Yedekleme Stratejisi Uygulay\u0131n<\/h3>\n
    Bir veritaban\u0131 Tam kurtarma modelindeyse, s\u0131k i\u015flem g\u00fcnl\u00fc\u011f\u00fc yedeklemeleri zorunludur. Kurtarma Noktas\u0131 Hedefinize (RPO) ve i\u015flem hacminize ba\u011fl\u0131 olarak, g\u00fcnl\u00fck yedeklemeleri her 5 ila 15 dakikada bir ger\u00e7ekle\u015fmelidir.<\/p>\n
    CloudSave gibi kurumsal yedekleme \u00e7\u00f6z\u00fcmleri bu s\u00fcreci \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirir. VDI (Sanal Cihaz Aray\u00fcz\u00fc) arac\u0131l\u0131\u011f\u0131yla do\u011frudan SQL Server ile entegre olan CloudSave, DBA’lar\u0131n politika odakl\u0131, y\u00fcksek frekansl\u0131 i\u015flem g\u00fcnl\u00fc\u011f\u00fc yedeklemeleri yap\u0131land\u0131rmas\u0131na olanak tan\u0131r. Bu, g\u00fcnl\u00fcklerin s\u00fcrekli olarak k\u0131rp\u0131lmas\u0131n\u0131, g\u00fcvenli bir \u015fekilde \u015fifrelenmesini ve tesis d\u0131\u015f\u0131 veya de\u011fi\u015ftirilemez bulut depolama alan\u0131nda saklanmas\u0131n\u0131 sa\u011flayarak, karma\u015f\u0131k \u00f6zel SQL Agent i\u015flerine ihtiya\u00e7 duymadan LOG_BACKUP<\/code> bekleme durumunu \u00f6nler.<\/p>\n
    2. \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fcn\u00fc Do\u011fru Boyutland\u0131r\u0131n ve VLF’leri Y\u00f6netin<\/h3>\n
    \u0130\u015flem g\u00fcnl\u00fc\u011f\u00fc boyutunuzu y\u00f6netmek i\u00e7in otomatik b\u00fcy\u00fcmeye g\u00fcvenmek tehlikeli bir anti-kal\u0131pt\u0131r. Otomatik b\u00fcy\u00fcme i\u015flemleri maliyetlidir ve disk s\u0131f\u0131rla ba\u015flat\u0131l\u0131rken (An\u0131nda Dosya Ba\u015flatma etkinle\u015ftirilmedik\u00e7e, ki bu g\u00fcnl\u00fck dosyalar\u0131 i\u00e7in ge\u00e7erli de\u011fildir<\/em>) i\u015flem i\u015flemeyi duraklat\u0131r.<\/p>\n
    Ayr\u0131ca, s\u0131k ve k\u00fc\u00e7\u00fck otomatik b\u00fcy\u00fcmeler (\u00f6rne\u011fin, her seferinde %10 veya 50MB b\u00fcy\u00fctmek) VLF par\u00e7alanmas\u0131na<\/strong> yol a\u00e7ar. Binlerce k\u00fc\u00e7\u00fck VLF’ye sahip bir i\u015flem g\u00fcnl\u00fc\u011f\u00fc, veritaban\u0131 ba\u015flatma s\u00fcrelerini, yedekleme performans\u0131n\u0131 ve \u00e7o\u011faltma gecikmesini ciddi \u015fekilde d\u00fc\u015f\u00fcr\u00fcr.<\/p>\n
      \n
    • G\u00fcnl\u00fc\u011f\u00fc \u00f6nceden boyutland\u0131r\u0131n:<\/strong> En b\u00fcy\u00fck bak\u0131m i\u015flemlerinizi (dizin yeniden olu\u015fturma gibi) analiz edin ve LDF dosyas\u0131n\u0131 b\u00fcy\u00fcmeye gerek kalmadan bunlar\u0131 kar\u015f\u0131layacak \u015fekilde \u00f6nceden boyutland\u0131r\u0131n.<\/li>\n
    • Sabit otomatik b\u00fcy\u00fcme ayarlay\u0131n:<\/strong> VLF’lerin sa\u011fl\u0131kl\u0131 bir boyutta olu\u015fturulmas\u0131n\u0131 sa\u011flamak i\u00e7in otomatik b\u00fcy\u00fcmeyi y\u00fczdeden sabit bir boyuta (\u00f6rne\u011fin 1GB veya 5GB) de\u011fi\u015ftirin.<\/li>\n<\/ul>\n
      VLF say\u0131n\u0131z\u0131 a\u015fa\u011f\u0131daki sorguyu kullanarak kontrol edebilirsiniz (SQL Server 2017+ i\u00e7in):<\/p>\n
      SELECT \n    db_name(database_id) AS DatabaseName,\n    COUNT(vlf_sequence_number) AS VLF_Count\nFROM sys.dm_db_log_info(DB_ID('YourDatabaseName'));\n<\/code><\/pre>\n
      VLF say\u0131n\u0131z 500’\u00fcn \u00fczerindeyse, sessiz bir d\u00f6nem beklemeyi, g\u00fcnl\u00fc\u011f\u00fc minimum boyuta k\u00fc\u00e7\u00fcltmeyi ve manuel olarak b\u00fcy\u00fck par\u00e7alar halinde gerekli boyutuna geri b\u00fcy\u00fctmeyi d\u00fc\u015f\u00fcn\u00fcn.<\/p>\n
      3. Dizin Bak\u0131m \u0130\u015flemlerini Optimize Edin<\/h3>\n
      Dizin yeniden olu\u015fturma i\u015flemleri, Toplu G\u00fcnl\u00fckl\u00fc kurtarma modelinde bile (dizin t\u00fcr\u00fcne ba\u011fl\u0131 olarak) tamamen g\u00fcnl\u00fc\u011fe kaydedilen i\u015flemlerdir. 500GB’l\u0131k bir dizini yeniden olu\u015fturmak en az 500GB i\u015flem g\u00fcnl\u00fc\u011f\u00fc kayd\u0131 olu\u015fturacakt\u0131r.<\/p>\n
      Bak\u0131m s\u0131ras\u0131nda g\u00fcnl\u00fck \u015fi\u015fmesini azaltmak i\u00e7in:
      \n*   Dizinleri yeniden olu\u015ftururken SORT_IN_TEMPDB = ON<\/code> kullan\u0131n. Bu, s\u0131ralama a\u015famas\u0131n\u0131 TempDB’ye aktararak kullan\u0131c\u0131 veritaban\u0131n\u0131n i\u015flem g\u00fcnl\u00fc\u011f\u00fc \u00fczerindeki y\u00fck\u00fc azalt\u0131r.
      \n*   M\u00fcmk\u00fcn oldu\u011funda dizin yeniden olu\u015fturma<\/em> yerine dizin yeniden d\u00fczenleme<\/em> (reorganize) kullan\u0131n, \u00e7\u00fcnk\u00fc yeniden d\u00fczenlemeler g\u00fcnl\u00fck a\u00e7\u0131s\u0131ndan daha verimlidir ve t\u00fcm i\u015flemi geri almadan kesintiye u\u011frat\u0131labilir.
      \n*   B\u00fcy\u00fck DELETE<\/code> veya UPDATE<\/code> i\u015flemlerini toplu (batch) hale getirin. 10 milyon sat\u0131r\u0131 tek bir i\u015flemde silmek yerine, 50.000’lik par\u00e7alar halinde silin, onaylay\u0131n ve g\u00fcnl\u00fck yedeklemelerinin gruplar aras\u0131nda g\u00fcnl\u00fc\u011f\u00fc k\u0131rpmas\u0131na izin verin.<\/p>\n
      4. Y\u00fcksek Eri\u015filebilirlik ve \u00c7o\u011faltma Topolojilerini \u0130zleyin<\/h3>\n
      AlwaysOn Kullan\u0131labilirlik Gruplar\u0131nda, birincil kopya, g\u00fcnl\u00fck kay\u0131tlar\u0131 t\u00fcm senkron ve asenkron ikincil kopyalarda sertle\u015fene kadar g\u00fcnl\u00fc\u011f\u00fcn\u00fc k\u0131rpamaz.<\/p>\n
      Bir ikincil kopya \u00e7evrimd\u0131\u015f\u0131 olursa veya a\u011f bant geni\u015fli\u011fi birincil kopyan\u0131n i\u015flem olu\u015fturma h\u0131z\u0131na ayak uyduramazsa, birincil kopyan\u0131n g\u00f6nderim kuyru\u011fu b\u00fcy\u00fcyecek ve g\u00fcnl\u00fck dolacakt\u0131r (AVAILABILITY_REPLICA<\/code> bekleme t\u00fcr\u00fc).<\/p>\n
      SQLServer:Replica > Log Send Queue<\/code> performans sayac\u0131 i\u00e7in sa\u011flam bir izleme uygulay\u0131n. Bir ikincil kopya kal\u0131c\u0131 olarak kaybolursa, onu Kullan\u0131labilirlik Grubundan kald\u0131rman\u0131z veya birincil g\u00fcnl\u00fc\u011f\u00fcn k\u0131rp\u0131lmas\u0131na izin vermek i\u00e7in veri hareketini ask\u0131ya alman\u0131z gerekir.<\/p>\n
      Sonu\u00e7<\/h2>\n
      Dolu bir i\u015flem g\u00fcnl\u00fc\u011f\u00fc ile kar\u015f\u0131la\u015fmak veritaban\u0131 y\u00f6neticileri i\u00e7in bir ge\u00e7i\u015f t\u00f6renidir, ancak uzun s\u00fcreli kesintilerle sonu\u00e7lanmak zorunda de\u011fildir. \u00d6nceden Yazma G\u00fcnl\u00fc\u011f\u00fc ve VLF’lerin mekani\u011fini anlayarak, sys.databases<\/code> kullanarak k\u00f6k nedeni h\u0131zl\u0131 bir \u015fekilde te\u015fhis edebilir ve do\u011fru h\u0131zl\u0131 kurtarma stratejisini uygulayabilirsiniz.<\/p>\n
      Uzun vadeli kararl\u0131l\u0131k, reaktif d\u00fczeltmelerden uzakla\u015fmaya ba\u011fl\u0131d\u0131r. G\u00fcnl\u00fck dosyalar\u0131n\u0131z\u0131 \u00f6nceden boyutland\u0131rmak, bak\u0131m rutinlerini optimize etmek ve s\u0131k\u0131, otomatik g\u00fcnl\u00fck yedekleme programlar\u0131n\u0131 zorunlu k\u0131lmak i\u00e7in CloudSave gibi kurumsal s\u0131n\u0131f yedekleme platformlar\u0131ndan yararlanmak, i\u015flem g\u00fcnl\u00fcklerinizin sa\u011fl\u0131kl\u0131, k\u0131rp\u0131lm\u0131\u015f ve y\u00fcksek verimli \u00fcretim i\u015f y\u00fcklerini desteklemeye haz\u0131r kalmas\u0131n\u0131 sa\u011flayacakt\u0131r.<\/p>\n","protected":false},"excerpt":{"rendered":"
      ** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"MSSQL Transaction Log Full: Prevention & Recovery","rank_math_description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","rank_math_focus_keyword":"MSSQL transaction log full","footnotes":""},"categories":[735],"tags":[1200,4262,4263,4264,4265,4266,4267],"class_list":["post-5934","post","type-post","status-publish","format-standard","hentry","category-database-backup","tag-database-administration","tag-error-9002","tag-log-backup","tag-mssql","tag-sql-recovery","tag-sql-server","tag-transaction-log"],"yoast_head":"\nMSSQL Transaction Log Full: Prevention & Recovery<\/title>\n<meta name=\"description\" content=\"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri\" \/>\n<meta property=\"og:description\" content=\"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/\" \/>\n<meta property=\"og:site_name\" content=\"CloudSave\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-16T16:15:28+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-16T17:13:53+00:00\" \/>\n<meta name=\"author\" content=\"shervinrv\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"shervinrv\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/\"},\"author\":{\"name\":\"shervinrv\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"headline\":\"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri\",\"datePublished\":\"2026-06-16T16:15:28+00:00\",\"dateModified\":\"2026-06-16T17:13:53+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/\"},\"wordCount\":2039,\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"keywords\":[\"Database Administration\",\"Error 9002\",\"Log Backup\",\"MSSQL\",\"SQL Recovery\",\"SQL Server\",\"Transaction Log\"],\"articleSection\":[\"Database Backup\"],\"inLanguage\":\"tr\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/\",\"name\":\"MSSQL Transaction Log Full: Prevention & Recovery\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/#website\"},\"datePublished\":\"2026-06-16T16:15:28+00:00\",\"dateModified\":\"2026-06-16T17:13:53+00:00\",\"description\":\"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/#website\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/\",\"name\":\"CloudSave\",\"description\":\"CloudSave\",\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\",\"name\":\"shervinrv\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"contentUrl\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"width\":859,\"height\":150,\"caption\":\"shervinrv\"},\"logo\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\"},\"sameAs\":[\"http:\\\/\\\/cloudsave.app\"],\"url\":\"https:\\\/\\\/cloudsave.app\\\/tr\\\/knowledge-base\\\/author\\\/shervinrv\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MSSQL Transaction Log Full: Prevention & Recovery","description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/","og_locale":"tr_TR","og_type":"article","og_title":"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri","og_description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","og_url":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/","og_site_name":"CloudSave","article_published_time":"2026-06-16T16:15:28+00:00","article_modified_time":"2026-06-16T17:13:53+00:00","author":"shervinrv","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"shervinrv","Tahmini okuma s\u00fcresi":"12 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/#article","isPartOf":{"@id":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/"},"author":{"name":"shervinrv","@id":"https:\/\/cloudsave.app\/tr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"headline":"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri","datePublished":"2026-06-16T16:15:28+00:00","dateModified":"2026-06-16T17:13:53+00:00","mainEntityOfPage":{"@id":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/"},"wordCount":2039,"publisher":{"@id":"https:\/\/cloudsave.app\/tr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"keywords":["Database Administration","Error 9002","Log Backup","MSSQL","SQL Recovery","SQL Server","Transaction Log"],"articleSection":["Database Backup"],"inLanguage":"tr"},{"@type":"WebPage","@id":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/","url":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/","name":"MSSQL Transaction Log Full: Prevention & Recovery","isPartOf":{"@id":"https:\/\/cloudsave.app\/tr\/#website"},"datePublished":"2026-06-16T16:15:28+00:00","dateModified":"2026-06-16T17:13:53+00:00","description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","breadcrumb":{"@id":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cloudsave.app\/tr\/knowledge-base\/mssql-i-%c5%9flem-g%c3%bcnl%c3%bc%c4%9f%c3%bc-dolu-%c3%b6nleme-ve-h%c4%b1zl%c4%b1-kurtarma-stratejileri\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudsave.app\/tr\/"},{"@type":"ListItem","position":2,"name":"MSSQL \u0130\u015flem G\u00fcnl\u00fc\u011f\u00fc Dolu: \u00d6nleme ve H\u0131zl\u0131 Kurtarma Stratejileri"}]},{"@type":"WebSite","@id":"https:\/\/cloudsave.app\/tr\/#website","url":"https:\/\/cloudsave.app\/tr\/","name":"CloudSave","description":"CloudSave","publisher":{"@id":"https:\/\/cloudsave.app\/tr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudsave.app\/tr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/cloudsave.app\/tr\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d","name":"shervinrv","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","url":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","contentUrl":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","width":859,"height":150,"caption":"shervinrv"},"logo":{"@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png"},"sameAs":["http:\/\/cloudsave.app"],"url":"https:\/\/cloudsave.app\/tr\/knowledge-base\/author\/shervinrv\/"}]}},"_links":{"self":[{"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/posts\/5934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/comments?post=5934"}],"version-history":[{"count":1,"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/posts\/5934\/revisions"}],"predecessor-version":[{"id":5999,"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/posts\/5934\/revisions\/5999"}],"wp:attachment":[{"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/media?parent=5934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/categories?post=5934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudsave.app\/tr\/wp-json\/wp\/v2\/tags?post=5934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}