{"id":3133,"date":"2013-04-10T12:22:39","date_gmt":"2013-04-10T12:22:39","guid":{"rendered":"http:\/\/mehmetsalihdeveci.net\/?p=3133"},"modified":"2019-04-26T16:30:31","modified_gmt":"2019-04-26T16:30:31","slug":"sql-server-2008-log-shipping-1","status":"publish","type":"post","link":"https:\/\/ittutorial.org\/sql-server-2008-log-shipping-1\/","title":{"rendered":"SQL SERVER 2008 LOG SHIPPING -1"},"content":{"rendered":"

Merhaba,<\/p>\n

Bu yaz\u0131 dizimde sizlere SQL Server 2008 de Log Shipping teknolojisini anlataca\u011f\u0131m. SQL Server Log Shipping teknolojisini k\u0131saca anlatt\u0131ktan sonra Log Shipping kurulumu ve testlerini g\u00f6rsel olarak g\u00f6sterece\u011fim.<\/p>\n

\"Log<\/a><\/p>\n

<\/p>\n\n

Log Shipping teknolojisi SQL Server 2000 den belli gelen ve SQL Server 2012 ile devam eden bir teknolojidir. Log Shipping teknolojisi SQL Server da hem High Availability hemde Disaster Recovery \u00e7\u00f6z\u00fcm\u00fc olarak ge\u00e7erlidir. Bu iki \u00f6zelli\u011fi \u015fu \u015fekilde sa\u011flamaktad\u0131r. Ana veritaban\u0131m\u0131z\u0131n transaction log lar\u0131ndan belli aral\u0131klarla beslenen bir yedek yada ikincil veritaban\u0131 olas\u0131 bir felaket an\u0131nda Ana veritaban\u0131 olarak hemen hizmet verebilmektedir. Ayr\u0131ca datalar\u0131m\u0131z da korundu\u011fu i\u00e7in ayn\u0131 zamanda da Disaster Recovery \u00e7\u00f6z\u00fcm\u00fcn\u00fc de sa\u011flam\u0131\u015f oluyor.<\/p>\n

Log Shipping in \u00e7al\u0131\u015fma stratejisini teorik olarak \u015f\u00f6yle ifade edebiliriz. Production ortam\u0131nda bulunan bir veritaban\u0131m\u0131z\u0131n Felaket an\u0131nda bir kopyas\u0131n\u0131n tutulmas\u0131n\u0131 istiyorsak ve felakete u\u011frayan database in bir an \u00f6nce data kayb\u0131 olmadan yada minimum data kayb\u0131yla tekrar hizmet vermesini istiyorsak Log Shipping teknolojisini kullanmam\u0131z gerekmektedir. Bu teknolojide Production database in belli aral\u0131klarla birebir kopyas\u0131 farkl\u0131 bir sunucuda ki instance da tutulur ve bu secondary database dedi\u011fimiz database belli aral\u0131klarla s\u00fcrekli olarak Production veritaban\u0131ndan beslenir. B\u00f6ylece felaket an\u0131nda production database ine eri\u015fim yoksa e\u011fer direk secondary veritaban\u0131m\u0131z ana veritaban\u0131 olarak kullan\u0131ma a\u00e7\u0131labilir.<\/p>\n

Genel itibariyle Log Shipping in avantajlar\u0131 ve dezavantajlar\u0131n\u0131 a\u015fa\u011f\u0131daki gibi s\u0131ralayabiliriz.<\/p>\n

Avantajlar<\/strong>
\n——————————–<\/p>\n

    \n
  1. Hem Disaster Recovery hemde High Availability \u00e7\u00f6z\u00fcm\u00fc sunar.<\/span><\/li>\n
  2. Maliyet a\u00e7\u0131s\u0131ndan \u00e7ok ucuz bir teknolojidir. SQL Server 2008 den itibaren express s\u00fcr\u00fcm\u00fc hari\u00e7 t\u00fcm versiyonlarda bu teknoloji kullan\u0131labilir.<\/li>\n
  3. Kurulumu ve bak\u0131m\u0131 kolay bir teknolojidir.<\/li>\n
  4. Bir veritaban\u0131 i\u00e7in s\u0131n\u0131rs\u0131z say\u0131da log ship yap\u0131lacak yedek database imkan\u0131 sunmaktad\u0131r. Buda bir uygulaman\u0131n downtime s\u00fcresini en minimuma indirmek i\u00e7in bir imkand\u0131r.<\/li>\n
  5. Standby mode da olan Secondary database \u00a0hi\u00e7bir manuel i\u015flem yapmadan read-only modda reporting imkan\u0131 sunmaktad\u0131r.<\/li>\n
  6. Kullan\u0131c\u0131 hatalar\u0131na kar\u015f\u0131 eski transaction log backuplar ile hatadan d\u00f6n\u00fclebilir.<\/li>\n<\/ol>\n

    Dezavantajlar
    \n—————————-<\/strong><\/p>\n

      \n
    1. Log Shipping de otomatik failover yok bu durumda failover durumu ger\u00e7ekle\u015fti\u011finde database admini hemen manuel failover yapmak zorunda.<\/span><\/li>\n
    2. Manuel Failover durumundan dolay\u0131 Downtime olas\u0131l\u0131\u011f\u0131 senkron mirroring e g\u00f6re daha fazlad\u0131r.<\/li>\n
    3. Belirlenen schedule aral\u0131\u011f\u0131na ba\u011fl\u0131 olarak ana veritaban\u0131 down oldu\u011fu zaman veri kayb\u0131 ya\u015fanabilir.<\/li>\n<\/ol>\n

      \u015eimdi \u00f6rnek bir database \u00fczerinden Log Shipping konfig\u00fcrasyonu yap\u0131p Log Shipping in ger\u00e7eklenmesini g\u00f6rsel olarak a\u015fa\u011f\u0131da maddeler halinde g\u00f6sterece\u011fim. \u0130\u015flemlere ba\u015flamadan \u00f6nce Log Shipping i\u00e7in gereken \u00f6n gereksinimleri a\u015fa\u011f\u0131daki gibi belirleyebiliriz.<\/p>\n

        \n
      1. Production Veritaban\u0131 dedi\u011fimiz primary veritaban\u0131 log shipping i\u00e7in Recovery Model i ya Full yada Bulk-Logged olmal\u0131.<\/span><\/li>\n
      2. Production veritaban\u0131n bulundu\u011fu server \u00fczerinde Secondary Server \u0131n eri\u015febilece\u011fi bir payla\u015f\u0131m alan\u0131 bulunmal\u0131. Bu payla\u015f\u0131ma Production ortam\u0131ndan transaction log backup lar gelecek, secondary server ise gelen bu backup lar\u0131 kendi server \u0131na kopyalay\u0131p restore edecek.<\/li>\n
      3. Log Shipping konfig\u00fcrasyonunu ger\u00e7ekle\u015ftirecek kullan\u0131c\u0131n\u0131n sysadmin olmas\u0131 gerekmektedir.<\/li>\n<\/ol>\n

        Log Shipping i\u015flemini ger\u00e7ekle\u015ftirece\u011fimiz SQL Server Instance lar\u0131 ve stat\u00fcleri a\u015fa\u011f\u0131daki gibidir.<\/p>\n

        Primary (Production) Veritaban\u0131:<\/strong> MYTESTINSTANCE<\/p>\n

        Secondary (Standby) Veritaban\u0131<\/strong>: TEST2008R2<\/p>\n

        Prerequisite leri belirttikten sonra \u015fimdi Log Shipping e ba\u015fl\u0131yorum. Bunun i\u00e7in a\u015fa\u011f\u0131daki gibi TestDatabase olu\u015fturup i\u00e7ine TestTable adl\u0131 \u00f6rnek bir tablo olu\u015fturuyorum.<\/p>\n

        \"1\"<\/a><\/p>\n

        Bu database de g\u00f6rebilmeniz a\u00e7\u0131s\u0131ndan TestTable tablosuna a\u015fa\u011f\u0131daki gibi \u00f6rnek datalar insert ediyorum. Yaz\u0131 serisinin sonunda log shipping testinde bu datalardan log shipping in ger\u00e7ekle\u015fti\u011fini ispat edece\u011fim.<\/p>\n

        \"2\"<\/a><\/p>\n

        Log Shipping e ba\u015flamadan \u00f6nce ad\u0131mlar\u0131n\u0131 a\u015fa\u011f\u0131daki gibi s\u0131ralayabiliriz.<\/p>\n

          \n
        1. Production veritaban\u0131n\u0131n Full Backup \u0131n\u0131 al ve Secondary Server \u00fczerindeki instance a bu backup \u0131 NoRecovery Mode<\/strong> da restore et.<\/span><\/li>\n
        2. Production veritaban\u0131ndan Transaction Log Backup al ve\u00a0Secondary Server \u00fczerindeki instance a bu backup \u0131\u00a0NoRecovery Mode<\/strong>\u00a0da restore et<\/li>\n
        3. Log Shipping Konfig\u00fcrasyonunu ger\u00e7ekle\u015ftirme.<\/li>\n<\/ol>\n

          1. Production Veritaban\u0131m\u0131z olan TestDatabase adl\u0131 veritaban\u0131n\u0131 a\u015fa\u011f\u0131daki gibi full backup \u0131n\u0131 al\u0131p Standby veritaban\u0131na NoRecovery mode da restore ediyorum.<\/p>\n

          \"3\"<\/a><\/p>\n

          \"6\"<\/a><\/p>\n

          2.Production veritaban\u0131n\u0131n transaction log backup \u0131n\u0131 al\u0131p a\u015fa\u011f\u0131daki gibi Standby veritaban\u0131na NoRecovery Mode da restore ediyoruz.<\/p>\n

          \"4\"<\/a><\/p>\n

          \"7\"<\/a><\/p>\n

          3. Bu ad\u0131mda Log Shipping Konfig\u00fcrasyonuna ba\u015fl\u0131yorum. \u0130\u015flem ad\u0131mlar\u0131nda s\u0131ras\u0131 ile ad\u0131mlar\u0131n ekran g\u00f6r\u00fcnt\u00fcs\u00fc a\u015fa\u011f\u0131daki gibidir.<\/p>\n

          TestDatabase veritaban\u0131na sa\u011f t\u0131klay\u0131p Properties sekmesinden Transaction Log Shipping men\u00fcs\u00fcne geliyoruz ve a\u015fa\u011f\u0131daki g\u00f6r\u00fcnt\u00fcde ok la g\u00f6sterildi\u011fi gibi Bu database i Log Shipping Konfig\u00fcrasyonu i\u00e7in Enable ediyoruz.<\/p>\n

          \"8\"<\/a><\/p>\n

          A\u015fa\u011f\u0131daki gibi Transaction Log Backup job \u0131 i\u00e7in a\u015fa\u011f\u0131daki gibi bir Schedule belirliyoruz. Her g\u00fcn 1 dakika aral\u0131klarla Backup al\u0131nmas\u0131n\u0131 ve 15 dk dan daha eski dosyalar\u0131n silinmesini a\u015fa\u011f\u0131daki gibi i\u015faretliyorum.<\/p>\n

          \"9\"<\/a><\/p>\n

          \"10\"<\/a><\/p>\n

          Primary server \u00fczerinde Secondary Server \u0131n eri\u015febilece\u011fi bir Share alan\u0131 olu\u015fturup bunu a\u015fa\u011f\u0131daki path lere yaz\u0131yorum.<\/p>\n

          \"11\"<\/a><\/p>\n

          Primary Veritaban\u0131 \u00fczerinde Transaction Log Backup alacak job i\u00e7in gerekli konfig\u00fcrasyonlar\u0131 yukar\u0131daki gibi girip OK butonuna bast\u0131m. \u015eimdi a\u015fa\u011f\u0131da Secondary Veritaban\u0131 i\u00e7in gerekli konfig\u00fcrasyonlar\u0131 yap\u0131yorum.<\/p>\n

          \"12\"<\/a><\/p>\n

          \"13\"<\/a><\/p>\n

          Secondary Database i\u00e7in gerekli konfig\u00fcrasyonlar\u0131 a\u015fa\u011f\u0131daki gibi yap\u0131yorum. Initalize Secondary Database sekmesindeki gereksinimleri yukar\u0131da ger\u00e7ekle\u015ftirdim. \u015eimdi Primary Sunucu \u00fczerindeki Transaction Log Backup lar\u0131 Secondary Server e ta\u015f\u0131yacak ve bunu Burdaki Standby veritaban\u0131na Restore edecek Copy ve Restore Joblar\u0131n\u0131 a\u015fa\u011f\u0131daki gibi olu\u015fturuyorum.<\/p>\n

          \"14\"<\/a><\/p>\n

          \"15\"<\/a><\/p>\n

          Copy job \u0131 i\u00e7in yukar\u0131da Schedule ile job \u0131n ko\u015fma aral\u0131\u011f\u0131n\u0131 3 dk olarak belirttik ve 15 dk dan eski dosyalar\u0131nda silinmesi i\u015faretledik. \u00a0Secondary Server \u00fczerinde bu dosyalar\u0131n kopyalanaca\u011f\u0131 path i de a\u015fa\u011f\u0131daki gibi belirttim.<\/p>\n

          \"16\"<\/a><\/p>\n

          Restore Job \u0131n\u0131 da benzer \u015fekilde a\u015fa\u011f\u0131daki gibi Schedule unu belirtiyoruz.<\/p>\n

          \"17\"<\/a><\/p>\n

          A\u015fa\u011f\u0131daki ad\u0131mda Secondary veritaban\u0131m\u0131z\u0131n modunu belirliyoruz. Ben Veritaban\u0131m\u0131n modunu Standby mode olarak belirledim. B\u00f6ylece Secondary veritaban\u0131 Restore job \u0131n\u0131n \u00e7al\u0131\u015fmad\u0131\u011f\u0131 aral\u0131klarda Read-only mode da olacak ve raporlamaya a\u00e7\u0131k olacakt\u0131r.
          \n<\/a>           \"18\"<\/a><\/p>\n

          Her iki Copy ve Restore job lar i\u00e7in gerekli Schedule lar\u0131 ve path leri yukarda girdikten sonra OK butonuna t\u0131kl\u0131yoruz.<\/p>\n

          \"19\"<\/a><\/p>\n

          \"20\"<\/a><\/p>\n

          Yukarda da g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi herhangi bir s\u0131k\u0131nt\u0131 meydana gelmedi\u011fi i\u00e7in Log Shipping Konfig\u00fcrasyonu ba\u015far\u0131l\u0131 bir \u015fekilde tamamland\u0131. Kurulum ba\u015far\u0131l\u0131 tamamland\u0131\u011f\u0131 i\u00e7in Primary veritaban\u0131 alt\u0131nda Backup, Secondary Veritaban\u0131nda ise Copy ve Restore job \u0131 olu\u015facakt\u0131r. Bunlar\u0131n olu\u015fmu\u015f oldu\u011funu a\u015fa\u011f\u0131daki gibi g\u00f6rebiliriz.<\/p>\n

          \"21\"<\/a><\/p>\n

          \"22\"<\/a><\/p>\n

          Log Shipping Konfig\u00fcrasyonunu tamamlad\u0131m ve bu yaz\u0131m\u0131n da sonuna geldim. Bir sonraki yaz\u0131da Ayn\u0131 konfig\u00fcrasyon \u00fczerinden log Shipping in ilgili datalarla ve testlerle ger\u00e7ekle\u015fti\u011fini g\u00f6sterece\u011fim.<\/p>\n

          \u015eimdilik Esen Kal\u0131n…<\/p>\n\n

           <\/p>\n

          Oracle Exadata SQL Server Goldengate Weblogic EBS ve Linux konusunda a\u015fa\u011f\u0131daki konularda 7×24 Uzman Dan\u0131\u015fmanlara yada E\u011fitimlere mi\u00a0<\/span>\u0130htiyac\u0131n\u0131z var mehmet.deveci@gridgroup.com.tr adresine mail atarak Bizimle ileti\u015fime ge\u00e7ebilirsiniz.<\/span><\/p>\n

          – Oracle Veritaban\u0131 Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Oracle Veritaban\u0131 Bak\u0131m ve Destek<\/span>
          \n– Exadata Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Exadata Bak\u0131m ve Destek<\/span>
          \n– SQL Server Veritaban\u0131 Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– SQL Server Veritaban\u0131 Bak\u0131m ve Destek<\/span>
          \n– Goldengate Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Goldengate Bak\u0131m ve Destek<\/span>
          \n– Linux Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Linux Bak\u0131m ve Destek<\/span>
          \n– Oracle EBS Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Oracle EBS Bak\u0131m ve Destek<\/span>
          \n– Weblogic Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Weblogic Bak\u0131m ve Destek<\/span>
          \n– Oracle Veritaban\u0131 E\u011fitimleri<\/span>
          \n– Oracle VM Server Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Oracle VM Server Bak\u0131m ve Destek<\/span>
          \n– Oracle EPPM Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Oracle EPPM Bak\u0131m ve Destek<\/span>
          \n– Oracle Primavera Dan\u0131\u015fmanl\u0131\u011f\u0131<\/span>
          \n– Oracle Primavera Bak\u0131m ve Destek<\/span>
          \n– Oracle E\u011fitimleri<\/span>
          \n– SQL Server E\u011fitimleri<\/span>
          \n– Goldengate E\u011fitimleri<\/span>
          \n– Exadata E\u011fitimleri<\/span>
          \n– Linux E\u011fitimleri<\/span>
          \n– Oracle EBS E\u011fitimleri<\/span>
          \n– Oracle VM Server E\u011fitimleri<\/span>
          \n– Weblogic E\u011fitimleri<\/span>
          \n– Oracle EPPM E\u011fitimleri<\/span>
          \n– Oracle Primavera E\u011fitimleri<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

          Merhaba, Bu yaz\u0131 dizimde sizlere SQL Server 2008 de Log Shipping teknolojisini anlataca\u011f\u0131m. SQL Server Log Shipping teknolojisini k\u0131saca anlatt\u0131ktan sonra Log Shipping kurulumu ve testlerini g\u00f6rsel olarak g\u00f6sterece\u011fim.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[19,23],"tags":[460,508,1000,1031,1515,1577,1583,1594,1632,1647,1653],"class_list":["post-3133","post","type-post","status-publish","format-standard","","category-sql-server","category-veritabani","tag-database-high-availability","tag-deveci","tag-log-shipping","tag-mehmet-salih-deveci","tag-salih-deveci","tag-sql-server","tag-sql-server-2008","tag-sql-server-2008-log-shipping","tag-sql-server-disaster-recovery","tag-sql-server-high-availability","tag-sql-server-log-shipping"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/3133","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/comments?post=3133"}],"version-history":[{"count":2,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/3133\/revisions"}],"predecessor-version":[{"id":5887,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/3133\/revisions\/5887"}],"wp:attachment":[{"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/media?parent=3133"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/categories?post=3133"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/tags?post=3133"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}