{"id":2900,"date":"2018-09-14T14:33:32","date_gmt":"2018-09-14T14:33:32","guid":{"rendered":"http:\/\/dbtut.com\/?p=2900"},"modified":"2018-12-06T08:45:34","modified_gmt":"2018-12-06T08:45:34","slug":"mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/","title":{"rendered":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica"},"content":{"rendered":"<p>&nbsp;<\/p>\n<p>To create\u00a0Availability Group(AG) Fail-over SQL Server Cluster with secondary replica we need 4 machines\/VMs which are as follows<\/p>\n<ol>\n<li>Domain Controller:\n<ol>\n<li>Machine Name: DC<\/li>\n<li>192.168.1.71<\/li>\n<li>Domain Name: TEST.<u><a href=\"http:\/\/text.com\/\">COM<\/a><\/u><\/li>\n<\/ol>\n<\/li>\n<li>Node1:\n<ol>\n<li>Machine Name: HClust01<\/li>\n<li>IP:\u00a0 192.168.1.81<\/li>\n<\/ol>\n<\/li>\n<li>Node2:\n<ol>\n<li>Machine Name: HClust02<\/li>\n<li>IP: 192.168.1.82<\/li>\n<\/ol>\n<\/li>\n<li>Node3:\n<ol>\n<li>Machine Name: HClust03<\/li>\n<li>IP: 192.168.1.83<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<p>&nbsp;<\/p>\n<p>To setup MSSQL Server Cluster we need to have WSFC \u2013 Windows Server Failover Clustering, FCI \u2013 Failover Cluster Instance (2-node) and AG \u2013 Availability group (2-node auto failover and 3<sup>rd<\/sup> node as Secondary Replica) is based on the following 4 phases. The above mentioned 3 nodes must be joined to domain i.e. all the nodes in WSFSC must be on same domain and same version of SQL Server and Operating System.<\/p>\n<ol>\n<li>Domain Controller<\/li>\n<li>WSFC<\/li>\n<li>FCI<\/li>\n<li>AG<\/li>\n<\/ol>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><em><u>Note: <\/u><\/em><em>FCI is based on 2 nodes with shared disk i.e. 2 nodes is having 1 SQL Server\u00a0<\/em><em>AG is having 2 SQL Server i.e. data disk is not shared<\/em><\/p>\n<p><strong>Phase 1: Setup Domain Controller<\/strong><\/p>\n<p><strong>\u00a0<img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/241-1.png\" \/><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/536.png\" \/><\/strong><\/p>\n<p>First we need to setup Domain Controller (DNS &amp; Active Directory). We have assigned the following configuration during setup<\/p>\n<ul>\n<li>Machine Name: DC<\/li>\n<li>192.168.1.71<\/li>\n<li>Domain Name: TEST.<u><a href=\"http:\/\/text.com\/\">COM<\/a><\/u><\/li>\n<\/ul>\n<p>Active Directory<\/p>\n<p><strong><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/211.png\" \/><\/strong><\/p>\n<p><b>Phase 2: Install &amp; Configure Windows Server Fail-over\u00a0Clustering (WSFC)<\/b><\/p>\n<p>First we need to create Windows Server Fail-over\u00a0Cluster on Node 1. We have setup following during configuration wizard. Moreover we need to locate shared disk as Quorum disk which is shared among all the nodes of the cluster<\/p>\n<ul>\n<li>Windows\u00a0Cluster\u00a0Name: TESTCLUST<\/li>\n<li>Cluster\u00a0IP: 192.168.1.85<\/li>\n<li>Shared Disk:2\n<ol>\n<li>Quorum: 2 GB (To Store System Status)<\/li>\n<li>Data: 50 GB (To Store Actual Data)<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/819-1.png\" \/><\/p>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/444.png\" \/><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/130.png\" \/><\/p>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/618.png\" \/><\/p>\n<p>After these configurations check the fail-over between 2 nodes at OS level.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Phase 3: Install &amp; Configure MSSQL Server Cluster-FCI<\/strong><\/p>\n<p>Install database failover cluster by running MSSQL Server 2012 Setup and select failover cluster option. We have done this on Cluster on Node 1 and have done following setup during configuration wizard. Then connect Node 2 and run MSSQL Server 2012 Setup now select add cluster node option and proceed with the wizard.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Database MSSQL Server\u00a0Cluster<\/strong><\/p>\n<p>Cluster\u00a0Name: CLUSTERTEST<\/p>\n<p>Cluster\u00a0IP: 192.168.1.90<\/p>\n<p>WSFC Role: SQL Server (MSSQL Server)<\/p>\n<p>&nbsp;<\/p>\n<p>The above cluster is based on the following 2 nodes<\/p>\n<p>Node1:\u00a0Machine Name: HClust01 ||| IP:\u00a0192.168.1.81<\/p>\n<p>Node2: Machine Name: HClust02 ||| IP: 192.168.1.82<\/p>\n<p>&nbsp;<\/p>\n<p>After this setup check &amp; confirm the database fail-over between these 2 nodes (SQL Level).<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/620.png\" \/><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/727.png\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Cluster Dependency Report<\/strong><\/p>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/874.png\" \/><\/p>\n<p><strong>SQL Server Connection<\/strong><\/p>\n<p><strong><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/134.png\" \/>\u00a0<\/strong><\/p>\n<p><strong>Phase 4: Install new SQL Server &amp; Configure AG \u2013 Availability Group<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p>Install a new standalone MSSQL Server 2012 and do the default configuration.<\/p>\n<p>Add this node to WSFC (i.e. the windows cluster that created earlier) and restart the instance. Now configure the availability group from MSSQL Server management studio and Setup the database as failover secondary replicas as 3rd node\u00a0for the database cluster. We need to create a shared location that is accessible to all the nodes. Database backup on primary need to be done that will be restore to Secondary AG Node to start the synchronization process. The synchronization mode can be either Asynchronous or Synchronous.<\/p>\n<p>&nbsp;<\/p>\n<p>The details for this cluster are as follows: Keep in mind that this failover is done manually<\/p>\n<p><strong>Database MSSQL Server\u00a0Cluster<\/strong><\/p>\n<p>Cluster\u00a0Name: CLUSTER<\/p>\n<p>IP Address: 192.168.1.173<\/p>\n<p>SQL Server Instance Name: AGSecondary<\/p>\n<p>WSFC Role: AG<\/p>\n<p>&nbsp;<\/p>\n<p>The above cluster is based on the following node<\/p>\n<p>Node3:\u00a0Machine Name: HClust03 ||| IP:\u00a0192.168.1.83<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/247.png\" \/><\/p>\n<p>After this setup check &amp; confirm the database fail-over between these 2 clusters (AG Group)<\/p>\n<p><strong><img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/125.png\" \/><\/strong><\/p>\n<p><b>Manual Fail-over\u00a0for 3<\/b><sup style=\"font-weight: bold;\">rd<\/sup><b> Node (SQL Server Level):<\/b><\/p>\n<p><strong>\u00a0<img decoding=\"async\" src=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/820.png\" \/><\/strong><\/p>\n<p>Under the tab of <strong>AlwaysOn High Availability <\/strong>right click the <strong>AG<\/strong>, select <b>Fail-over<\/b>\u00a0and proceed with the <strong>Fail Over Availability Group: AG <\/strong>widget. This is for <strong>Manual\u00a0<\/strong><b>Fail-over<\/b>\u00a0for both to come and leave from AG Group (In our case 3<sup>rd<\/sup> node).<\/p>\n\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_2900\" class=\"pvc_stats all  \" data-element-id=\"2900\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; To create\u00a0Availability Group(AG) Fail-over SQL Server Cluster with secondary replica we need 4 machines\/VMs which are as follows Domain Controller: Machine Name: DC 192.168.1.71 Domain Name: TEST.COM Node1: Machine Name: HClust01 IP:\u00a0 192.168.1.81 Node2: Machine Name: HClust02 IP: 192.168.1.82 Node3: Machine Name: HClust03 IP: 192.168.1.83 &nbsp; To setup MSSQL Server Cluster we need to &hellip;<\/p>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_2900\" class=\"pvc_stats all  \" data-element-id=\"2900\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"author":181,"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,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-2900","post","type-post","status-publish","format-standard","","category-mssql"],"aioseo_notices":[],"a3_pvc":{"activated":true,"total_views":602,"today_views":0},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica - Database Tutorials<\/title>\n<meta name=\"description\" content=\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2018-09-14T14:33:32+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-12-06T08:45:34+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png\" \/>\n<meta name=\"author\" content=\"Engr. Mohammad Rizwan Yasin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Engr. Mohammad Rizwan Yasin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\"},\"author\":{\"name\":\"Engr. Mohammad Rizwan Yasin\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/9b0bcfe5e42a7f42c1aed036ae5c9f53\"},\"headline\":\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica\",\"datePublished\":\"2018-09-14T14:33:32+00:00\",\"dateModified\":\"2018-12-06T08:45:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\"},\"wordCount\":609,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage\"},\"thumbnailUrl\":\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png\",\"articleSection\":[\"MSSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\",\"name\":\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage\"},\"thumbnailUrl\":\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png\",\"datePublished\":\"2018-09-14T14:33:32+00:00\",\"dateModified\":\"2018-12-06T08:45:34+00:00\",\"description\":\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage\",\"url\":\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png\",\"contentUrl\":\"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/9b0bcfe5e42a7f42c1aed036ae5c9f53\",\"name\":\"Engr. Mohammad Rizwan Yasin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/fe7a00fd631820cba9b5309a297ca14ce4b9e430fe57c00399e9cca2f0550e10?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/fe7a00fd631820cba9b5309a297ca14ce4b9e430fe57c00399e9cca2f0550e10?s=96&d=mm&r=g\",\"caption\":\"Engr. Mohammad Rizwan Yasin\"},\"url\":\"https:\/\/dbtut.com\/index.php\/author\/mohammadrizwan\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica - Database Tutorials","description":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica","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:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/","og_locale":"en_US","og_type":"article","og_title":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica - Database Tutorials","og_description":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica","og_url":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/","og_site_name":"Database Tutorials","article_published_time":"2018-09-14T14:33:32+00:00","article_modified_time":"2018-12-06T08:45:34+00:00","og_image":[{"url":"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png","type":"","width":"","height":""}],"author":"Engr. Mohammad Rizwan Yasin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Engr. Mohammad Rizwan Yasin","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/"},"author":{"name":"Engr. Mohammad Rizwan Yasin","@id":"https:\/\/dbtut.com\/#\/schema\/person\/9b0bcfe5e42a7f42c1aed036ae5c9f53"},"headline":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica","datePublished":"2018-09-14T14:33:32+00:00","dateModified":"2018-12-06T08:45:34+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/"},"wordCount":609,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage"},"thumbnailUrl":"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png","articleSection":["MSSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/","url":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/","name":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage"},"thumbnailUrl":"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png","datePublished":"2018-09-14T14:33:32+00:00","dateModified":"2018-12-06T08:45:34+00:00","description":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#primaryimage","url":"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png","contentUrl":"http:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/558.png"},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2018\/09\/14\/mssql-server-availability-groupag-fail-over-clustering-with-secondary-replica\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"MSSQL Server Availability Group(AG) : Fail-over Clustering with Secondary Replica"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/9b0bcfe5e42a7f42c1aed036ae5c9f53","name":"Engr. Mohammad Rizwan Yasin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/fe7a00fd631820cba9b5309a297ca14ce4b9e430fe57c00399e9cca2f0550e10?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/fe7a00fd631820cba9b5309a297ca14ce4b9e430fe57c00399e9cca2f0550e10?s=96&d=mm&r=g","caption":"Engr. Mohammad Rizwan Yasin"},"url":"https:\/\/dbtut.com\/index.php\/author\/mohammadrizwan\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/2900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/181"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=2900"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/2900\/revisions"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=2900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=2900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=2900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}