{"id":3180,"date":"2013-04-11T09:08:58","date_gmt":"2013-04-11T09:08:58","guid":{"rendered":"http:\/\/mehmetsalihdeveci.net\/?p=3180"},"modified":"2019-02-28T08:50:58","modified_gmt":"2019-02-28T08:50:58","slug":"sql-server-2008-log-shipping-2","status":"publish","type":"post","link":"https:\/\/ittutorial.org\/sql-server-2008-log-shipping-2\/","title":{"rendered":"SQL SERVER 2008 LOG SHIPPING -2"},"content":{"rendered":"

Merhaba,<\/p>\n

Bu yaz\u0131mda \u00f6nceki yaz\u0131mda<\/a> ba\u015flad\u0131\u011f\u0131m SQL Server 2008 de Log Shipping teknolojisini anlatmaya devam edece\u011fim. Bu y\u00fczden bu yaz\u0131y\u0131 okumadan \u00f6nce \u00f6nceki yaz\u0131y\u0131<\/a> okuman\u0131z gerekmektedir.<\/p>\n

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

<\/p>\n\n

Bir \u00f6nceki yaz\u0131mda Log Shipping konfig\u00fcrasyonunu yapm\u0131\u015f ve ba\u015far\u0131l\u0131 bir \u015fekilde kurulumu tamamlam\u0131\u015ft\u0131m. \u015eimdi database lere bak\u0131p log Shipping \u00e7al\u0131\u015f\u0131yor mu \u00e7al\u0131\u015fm\u0131yor mu durumu nedir ? \u00d6nceki yaz\u0131da ba\u015flatm\u0131\u015f oldu\u011fum a\u015fa\u011f\u0131daki \u00f6rnek data insert scripti yine \u00e7al\u0131\u015fmaktad\u0131r. B\u00f6ylece sizlere datalar\u0131n kar\u015f\u0131 tarafa gitti\u011fini g\u00f6sterece\u011fim.<\/p>\n

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

Her 1 dakika da bir Transaction Log Backup al\u0131nmas\u0131 i\u00e7in Job da schedule d\u00fczenlemi\u015ftik. \u015eimdi Log lar\u0131n at\u0131laca\u011f\u0131 share dosyas\u0131na bakt\u0131\u011f\u0131m\u0131zda a\u015fa\u011f\u0131daki gibi log backup lar\u0131n buraya geldi\u011fini(Resimde Sa\u011f taraftaki k\u0131s\u0131mda) ve ayn\u0131 zamanda da Secondary Server da belirtti\u011fimiz yere de(Resimde Sol tarafta) kopyaland\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcyoruz. A\u015fa\u011f\u0131da Sol taraftaki Resimde TransactionLog_Files dizini Secondary Server da Sa\u011f taraftaki LogShipping_Share dosyas\u0131 ise Primary Server da bulunan log dosyalar\u0131n\u0131n bulundu\u011fu payla\u015f\u0131ml\u0131 dizinimizdir.<\/p>\n

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

Di\u011fer yandan \u00e7al\u0131\u015fan Backup, Copy ve Restore job lar\u0131n\u0131n history sine a\u015fa\u011f\u0131daki gibi bakarak joblarda hata al\u0131n\u0131p al\u0131nmad\u0131\u011f\u0131n\u0131 kontrol ediyoruz.<\/p>\n

Primary Database de \u00e7al\u0131\u015fan Backup Job history:<\/strong><\/p>\n

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

Secondary database de \u00e7al\u0131\u015fan Copy ve Restore Job History:<\/strong><\/p>\n

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

Yukarda job lar\u0131n history sinden de g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi joblar ba\u015far\u0131l\u0131 bir \u015fekilde \u00e7al\u0131\u015f\u0131yor. Di\u011fer yandan Log Shipping in durumunu a\u015fa\u011f\u0131daki gibi de kontrol edebilirsiniz. Burada son al\u0131nan backup ve secondary server i\u00e7in ise son ger\u00e7ekle\u015ftirilen copy ve Restore job \u0131n tarihini g\u00f6stermektedir.<\/p>\n

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

Primary Database i\u00e7in al\u0131nan durum raporu:<\/strong><\/p>\n

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

Secondary Database i\u00e7in al\u0131nan durum raporu:<\/strong><\/p>\n

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

Ayr\u0131ca bu job lar\u0131 schedule ederken 15 dakikadan eski dosyalar\u0131n silinmesini istemi\u015ftik. A\u015fa\u011f\u0131da da g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi 15 dakikadan daha eski dosyalar job taraf\u0131ndan silinmektedir.<\/p>\n

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

\u015eimdi datalar\u0131n birebir ayn\u0131s\u0131 olup olmad\u0131\u011f\u0131n\u0131 g\u00f6relim. Bunun i\u00e7in \u00fcstte ba\u015flatt\u0131\u011f\u0131m insert data scripti ni manuel olarak durduruyorum. Bir s\u00fcre sonra secondary database den a\u015fa\u011f\u0131daki sorguyu \u00e7ekti\u011fim zaman resimde g\u00f6r\u00fclen hatay\u0131 al\u0131yorum. Bu hatan\u0131n sebebi secondary server o an gelen transaction log backup \u0131 restore a\u015famas\u0131nda oldu\u011fu i\u00e7in sorguya izin vermiyor. Bunu ilk yaz\u0131mda Restore job \u0131n\u0131 schedule ederken Secondary Database ini Standby Mode olarak se\u00e7ti\u011fimiz zaman Disconnect users in the database when restoring backups \u0131 <\/strong>i\u015faretledi\u011fim i\u00e7in \u015fuanda bizim sorgumuza cevap vermiyor database…<\/p>\n

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

Bu sorgudan bir s\u00fcre sonra tekrar ayn\u0131 sorguyu \u00e7ekti\u011fim zaman a\u015fa\u011f\u0131daki gibi cevap al\u0131yorum. Tabloda 3404 kay\u0131t oldu\u011funu s\u00f6yl\u00fcyor ayn\u0131 sorguyu primary database ine att\u0131\u011f\u0131m zaman ayn\u0131 say\u0131da kay\u0131t oldu\u011funu g\u00f6r\u00fcyoruz.<\/p>\n

Secondary(Standby) Database i\u00e7in at\u0131lan sorgu ve cevab\u0131:<\/strong>
\n<\/a> \"38\"<\/a><\/p>\n

Primary(Production) Database i\u00e7in at\u0131lan sorgu ve cevab\u0131:<\/strong><\/p>\n

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

Tabloya gelen kay\u0131t say\u0131lar\u0131 ayn\u0131 a\u015fa\u011f\u0131daki gibi datalara da bakt\u0131\u011f\u0131m\u0131z zaman Primary database ine gelen t\u00fcm datalar ayn\u0131 zamanda Secondary database ine de gelmi\u015f.<\/p>\n

Primary(Production) Database i\u00e7in at\u0131lan sorgu ve cevab\u0131:<\/strong><\/p>\n

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

Secondary(Standby) Database i\u00e7in at\u0131lan sorgu ve cevab\u0131:<\/strong><\/p>\n

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

Datalar\u0131n da ayn\u0131 data oldu\u011funu g\u00f6rd\u00fckten sonra Log Shipping in ba\u015far\u0131l\u0131 bir \u015fekilde \u00e7al\u0131\u015fm\u0131\u015f oldu\u011funu uygulamal\u0131 olarakta g\u00f6rm\u00fc\u015f olduk. Datalar\u0131 birebir g\u00f6rebilmek i\u00e7in ya t\u00fcm transactionlar\u0131 durdurmak gerekiyor yada Log Shipping i durdurmak gerekiyor. T\u00fcm transactionlar\u0131 durdurmak production veritabanlar\u0131nda \u00e7ok yanl\u0131\u015f bir davran\u0131\u015f oldu\u011fundan log Shipping i durdurmak daha mant\u0131kl\u0131d\u0131r.<\/p>\n

Log Shipping le i\u015fimiz bitti kald\u0131rmak istiyorsak e\u011fer a\u015fa\u011f\u0131daki gibi kald\u0131rabiliriz.<\/p>\n

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

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

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

Log Shipping i kald\u0131rd\u0131ktan sonra istenildi\u011fi takdirde manuel failover i\u00e7in standby mode da olan Secondary database i normal mode a al\u0131p Uygulamay\u0131 buraya ba\u011flayabiliriz.<\/p>\n

A\u015fa\u011f\u0131da g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi TestDatabase veritaban\u0131 Standby Mode da sadece Read-Only olarak hizmet vermektedir.<\/p>\n

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

Secondary olarak se\u00e7ti\u011fimiz bu database e\u011fer primary database herhangi bir sebepten dolay\u0131 down olmu\u015fsa yada crash olmu\u015fsa secondary database i a\u015fa\u011f\u0131daki gibi normal mode a \u00e7ekip direk olarak uygulamay\u0131 buraya ba\u011flayabiliriz. Standby mode da olan TestDatabase veritaban\u0131m\u0131za son Transaction Log Backup \u0131 RESTORE WITH RECOVERY<\/strong> mode da restore ediyoruz ve a\u015fa\u011f\u0131daki resimde yan da da g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi TestDatabase adl\u0131 veritaban\u0131m\u0131z normal mode a ge\u00e7mi\u015f oldu.<\/p>\n

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

SQL Server 2008 de Log Shipping konulu yaz\u0131m\u0131 burada tamaml\u0131yorum. Bir sonraki yaz\u0131 da g\u00f6r\u00fc\u015fmek dile\u011fiyle Esen Kal\u0131n…<\/p>\n\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\u0131mda \u00f6nceki yaz\u0131mda ba\u015flad\u0131\u011f\u0131m SQL Server 2008 de Log Shipping teknolojisini anlatmaya devam edece\u011fim. Bu y\u00fczden bu yaz\u0131y\u0131 okumadan \u00f6nce \u00f6nceki yaz\u0131y\u0131 okuman\u0131z gerekmektedir.<\/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,614,1000,1031,1515,1577,1583,1594,1632,1647,1653],"class_list":["post-3180","post","type-post","status-publish","format-standard","","category-sql-server","category-veritabani","tag-database-high-availability","tag-deveci","tag-failover","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\/3180","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=3180"}],"version-history":[{"count":2,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/3180\/revisions"}],"predecessor-version":[{"id":5886,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/3180\/revisions\/5886"}],"wp:attachment":[{"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/media?parent=3180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/categories?post=3180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/tags?post=3180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}