{"id":5020,"date":"2019-01-05T13:44:44","date_gmt":"2019-01-05T13:44:44","guid":{"rendered":"http:\/\/mehmetsalihdeveci.net\/?p=5020"},"modified":"2019-02-28T08:24:53","modified_gmt":"2019-02-28T08:24:53","slug":"sql-server-alwayson-1","status":"publish","type":"post","link":"https:\/\/ittutorial.org\/sql-server-alwayson-1\/","title":{"rendered":"SQL Server AlwaysOn -1"},"content":{"rendered":"

Merhaba Arkada\u015flar,<\/p>\n

Bu ve bundan sonraki bir ka\u00e7 yaz\u0131mda sizlere Microsoft SQL Server 2012 ile beraber tan\u0131t\u0131lan AlwaysOn un ne oldu\u011funu kurulum konfig\u00fcrasyonunu vs anlataca\u011f\u0131m.<\/p>\n

\"\"<\/p>\n

<\/p>\n

 <\/p>\n\n

 <\/p>\n

Bu yaz\u0131n\u0131n devam\u0131 olan di\u011fer SQL Server AlwaysOn yaz\u0131lar\u0131ma a\u015fa\u011f\u0131daki linklerden ula\u015fabilirsiniz.<\/p>\n

https:\/\/ittutorial.org\/2019\/01\/06\/sql-server-alwayson-2\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2019\/01\/06\/sql-server-alwayson-3\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2019\/01\/06\/sql-server-alwayson-4\/<\/a><\/p>\n

Microsoft SQL Server taraf\u0131nda 2012 versiyonuyla beraber AlwaysOn Availability Groups \u00f6zelli\u011fini tan\u0131tt\u0131. Bu \u00f6zellik asl\u0131nda SQL Server taraf\u0131nda daha \u00f6nce bildi\u011fimiz Log Shipping<\/a>, Failover Clustering<\/a> ve Mirroring<\/a> \u00f6zelliklerinin biraraya getirilmesi sonucu olu\u015fturulmu\u015f bir \u00f6zellik diyebiliriz.<\/p>\n

\u00c7\u00fcnk\u00fc Log Shipping yaparken Disaster Recovery sa\u011flan\u0131yordu fakat anl\u0131k senkron de\u011fildi , Mirroringde anl\u0131k senkron oluyordu fakat Read Only se\u00e7ene\u011fi yoktu ayr\u0131ca Automatic Failover i\u00e7in Witness Server laz\u0131md\u0131. Failover Clustering de Cluster name ile 2 node a eri\u015fim vard\u0131 fakat Failover cluster da sadece High availability \u00e7\u00f6z\u00fcm\u00fcyd\u00fc bunlar\u0131n tamam\u0131n\u0131n avantajlar\u0131 biraraya getirilerek SQL Server Always On olu\u015fturuldu diyebiliriz. A\u015fa\u011f\u0131daki linklerden daha \u00f6nce yazd\u0131\u011f\u0131m Log Shipping, Mirroring ve Failover clustering yaz\u0131lar\u0131n\u0131 okuyarak AlwaysOn a neden ge\u00e7ildi vs daha detayl\u0131 \u00f6\u011frenebilirsiniz.<\/p>\n

https:\/\/ittutorial.org\/2013\/04\/10\/sql-server-2008-log-shipping-1\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2013\/04\/11\/sql-server-2008-log-shipping-2\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2013\/04\/03\/sql-server-2008-failover-cluster-1\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2013\/04\/04\/sql-server-2008-failover-cluster-2\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2013\/01\/29\/sql-server-2008-database-mirroring-1\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2013\/02\/05\/sql-server-2008-database-mirroring-2\/<\/a><\/p>\n

https:\/\/ittutorial.org\/2013\/02\/13\/sql-server-2008-database-mirroring-3\/<\/a><\/p>\n

 <\/p>\n

SQL Server AlwaysOnu a\u015fa\u011f\u0131daki \u015fekil \u00fczerinden\u00a0anlatay\u0131m.<\/p>\n

\"\"<\/p>\n

AlwaysOn, en az 2 sunucu \u00fcst\u00fcnde kurulan Windows Server Failover Cluster ( WSFC ) \u00fcst\u00fcnde \u00e7al\u0131\u015fan 2 sunucu aras\u0131nda kurulan ve Hem High Availability hemde Disaster Recovery i sa\u011flayan yeni bir SQL Server \u00e7\u00f6z\u00fcm\u00fcd\u00fcr.<\/p>\n

High Availability sa\u011flar diyoruz \u00e7\u00fcnk\u00fc T an\u0131nda Primary sunucuya bir \u015fey oldu\u011funda Automatic Failover ile Secondary node Primary olacakt\u0131r. Disaster Recovery sa\u011fl\u0131yor diyoruz \u00e7\u00fcnk\u00fc T an\u0131nda Primary sunucudaki disk ve sunucu ar\u0131zalansada Secondary sunucudaki Veritaban\u0131, Server ve Storage olarak ayr\u0131 ayr\u0131 oldu\u011fu i\u00e7in ordan kurtarabiliyoruz. Ayr\u0131ca Secondary Node Mirroring deki gibi bo\u015fa \u00e7al\u0131\u015fm\u0131yor bu Node uda Reporting ve Backup ama\u00e7l\u0131 kullanabilirsiniz.<\/p>\n

K\u0131saca kurumunuzda \u00e7al\u0131\u015fan SQL Server veritabanlar\u0131n\u0131z i\u00e7in High Availability ve Disaster Recovery birarada d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z tek \u00e7\u00f6z\u00fcm AlwaysOn \u00e7\u00f6z\u00fcm\u00fcd\u00fcr.<\/p>\n

AlwaysOn Availability Group: <\/strong>SQL Server 2012 ile gelen, database mirroring i\u015flemine alternatif olarak kullan\u0131labilecek bir yap\u0131d\u0131r. AlwaysOn Availability Group ile bir server \u00fczerindeki bir veritaban\u0131nda olan de\u011fi\u015fikliklerin senkron olarak farkl\u0131 bir server \u00fczerindeki kopyas\u0131na yans\u0131mas\u0131 sa\u011flan\u0131r. Bu yap\u0131n\u0131n mirroring i\u015flemine g\u00f6re avantajlar\u0131, birden fazla secondary server\u0131n aktif olarak kullan\u0131labilmesidir. Ayr\u0131ca primary server \u00fczerinde yazma i\u015flemleri yap\u0131l\u0131rken, raporlamalar i\u00e7in okuma i\u015flemi ve backup i\u015flemleri secondary server \u00fczerinden yap\u0131larak performans a\u00e7\u0131s\u0131ndan avantajlar elde edilebilir.<\/p>\n

AlwaysOn Kurulumu i\u00e7in gerekli Gereksinimleri a\u015fa\u011f\u0131daki gibidir.<\/p>\n

SQL Server 2012 AlwaysOn Availability Group y\u00f6nteminin veritaban\u0131 \u00fczerinde uygulanabilmesi i\u00e7in, Windows Server Failover Cluster yap\u0131s\u0131n\u0131n a\u015fa\u011f\u0131daki gibi konfig\u00fcre edilmi\u015f oldu\u011fu, ayn\u0131 \u00f6zelliklerde iki ya da daha fazla sunucu olmal\u0131d\u0131r. Ayr\u0131ca versiyonun en az SQL Server 2012\u2019nin de Enterprise Edition olmas\u0131 gerekmektedir.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

SQL Server 2012 \u00fczerinde AlwaysOn \u00f6zelli\u011finin aktif edilebilmesi i\u00e7in \u00f6ncelikle iki node\u2019un da a\u015fa\u011f\u0131daki gibi bir Cluster \u00fcyesi olmas\u0131 gerekir.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Konfig\u00fcrasyon yap\u0131lacak olan birinci node ile ikinci node aras\u0131nda 1433 ve 445 portlar\u0131 \u00fczerinden eri\u015fim i\u00e7in gerekli tan\u0131mlar\u0131n yap\u0131lmas\u0131 gerekir.<\/p>\n

Ayr\u0131ca availability group konfig\u00fcrasyonu s\u0131ras\u0131nda tan\u0131mlanmas\u0131 gereken ve availability gruba dahil edilecek olan veritabanlar\u0131n\u0131n ilk yedeklerinin al\u0131naca\u011f\u0131 bir klas\u00f6r \u00fczerinde payla\u015f\u0131m tan\u0131mlar\u0131n\u0131n yap\u0131lmas\u0131 gerekir. (Normal \u015fartlarda her iki sunucunun SQL Server ve SQL Agent hesaplar\u0131na ilgili klas\u00f6r \u00fczerinde read\/write yetkilerinin verilmesi yeterlidir. Fakat, \u00fcretim sunucusundaki SQL Server hesab\u0131 \u2018LOCAL SYSTEM\u2019 kullan\u0131c\u0131s\u0131 ise payla\u015f\u0131lan klas\u00f6r \u00fczerinde verilecek olan yetki \u2018everyone \u2013 read\/write\u2019 olmal\u0131d\u0131r.)<\/p>\n

Kaynak sunucudaki SQL Server \u00fczerinde konfig\u00fcrasyonu yapacak olan kullan\u0131c\u0131, Windows \u00fczerinde \u2018Administrator\u2019, SQL Server \u00fczerinde \u2018sysadmin\u2019 yetkisine sahip bir kullan\u0131c\u0131 olmal\u0131d\u0131r.<\/p>\n

AlwaysOn Availability Group yap\u0131s\u0131n\u0131n uygulanaca\u011f\u0131 sunucular\u0131n diskleri birbirinden ba\u011f\u0131ms\u0131z oldu\u011fundan, \u00f6ncelikle sunucular \u00fczerinde bulunacak olan veritabanlar\u0131n\u0131n data ve log dosyalar\u0131 i\u00e7in kullan\u0131lacak olan klas\u00f6rler her iki sunucuda da ayn\u0131 olacak \u015fekilde yarat\u0131lmal\u0131d\u0131r.<\/p>\n

Normal bir Failover Cluster kurulumundan farkl\u0131 olacak \u015fekilde AlwaysOn Availability Group i\u00e7in linkteki ad\u0131mlar<\/a> takip edilerek, her iki node \u00fczerinde Stand-Alone SQL Server kurulumlar\u0131 yap\u0131l\u0131r.<\/p>\n

 <\/p>\n

B\u00f6ylece bu yaz\u0131n\u0131n sonuna gelmi\u015f bulunmaktay\u0131m bir sonraki yaz\u0131da g\u00f6r\u00fc\u015fmek dile\u011fiyle esen kal\u0131n..<\/p>\n

 <\/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 Arkada\u015flar, Bu ve bundan sonraki bir ka\u00e7 yaz\u0131mda sizlere Microsoft SQL Server 2012 ile beraber tan\u0131t\u0131lan AlwaysOn un ne oldu\u011funu kurulum konfig\u00fcrasyonunu vs anlataca\u011f\u0131m.<\/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":[108,460,508,614,1000,1031,1515,1577,1583,1594,1601,1618,1619,1632,1647,1653],"class_list":["post-5020","post","type-post","status-publish","format-standard","","category-sql-server","category-veritabani","tag-alwayson","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-2012-alwayson","tag-sql-server-alwayson","tag-sql-server-alwayson-kurulumu","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\/5020","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=5020"}],"version-history":[{"count":2,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/5020\/revisions"}],"predecessor-version":[{"id":5799,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/posts\/5020\/revisions\/5799"}],"wp:attachment":[{"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/media?parent=5020"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/categories?post=5020"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ittutorial.org\/wp-json\/wp\/v2\/tags?post=5020"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}