{"id":8548,"date":"2016-07-12T20:27:03","date_gmt":"2016-07-12T18:27:03","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/"},"modified":"2016-07-12T20:27:03","modified_gmt":"2016-07-12T18:27:03","slug":"sql-server-2016-alwayson-direct-seeding-and-backup-considerations","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/","title":{"rendered":"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations"},"content":{"rendered":"<p>As promised in my <a href=\"http:\/\/dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-performance-considerations\/\" target=\"_blank\" rel=\"noopener noreferrer\">prior blog post<\/a>, we\u2019ll talk now about direct seeding feature and backups. We found an interesting LIMIT_CONCURRENT_BACKUPS value for current state of the <em>hadr_automatic_seeding_state_transition<\/em> event. As said last time, this value is meaningful by itself.<\/p>\n<p>So let\u2019s try to perform a backup while the database is concerned by an active seeding session. In fact, my backup was blocked (as I supposed) and here what I found from the sys.dm_tran_locks and sys.dm_exec_requests DMVs.<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SELECT\t\n\tr.command,\n\tr.wait_type,\n\tr.wait_resource,\n\tDB_NAME(tl.resource_database_id) as [database_name],\n\ttl.resource_type,\n\ttl.resource_subtype,\n\ttl.request_mode,\n\ttl.request_type,\n\ttl.request_status,\n\tr.session_id as blocked_session_id,\n\tr.blocking_session_id\nFROM sys.dm_tran_locks as tl\njoin sys.dm_exec_requests as r\n\ton tl.request_session_id = r.session_id\nWHERE tl.request_session_id = &lt;concerned session&gt;<\/pre>\n<p>&nbsp;<\/p>\n<ul>\n<li>The blocked session (my backup)<\/li>\n<\/ul>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-9730\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963.jpg\" alt=\"blog 100 - AG direct seeding - 1 - blocked session\" width=\"900\" height=\"48\" \/><\/a><\/p>\n<ul>\n<li>Blocking session (my direct seeding session)<\/li>\n<\/ul>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-2-blocking-session-e1468353487242.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-9731\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-2-blocking-session-e1468353487242.jpg\" alt=\"blog 100 - AG direct seeding - 2 - blocking session\" width=\"900\" height=\"186\" \/><\/a><\/p>\n<p>In short, my backup session is waiting on database object with a LCK_M_U lock type\u00a0that is already held by my direct seeding session. But the interesting part is that adding a database with direct seeding mode seems to be similar to performing a backup operation from a locking perspective. We also recognize characteristic wait types that occur during a backup operation (ASYNC_IO_COMPLETION, BACKUPBUFFER). So direct seeding as a streaming backup? Well that sounds good!<\/p>\n<p>Well, let\u2019s continue with this other query<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SELECT \n\tr.command,\n\tr.wait_type,\n\tr.wait_resource,\n\tr.scheduler_id\nfrom sys.dm_exec_requests as r\njoin sys.dm_os_schedulers as s\n\ton s.scheduler_id = r.scheduler_id\nwhere r.session_id = 82\n\tAND s.status = 'VISIBLE ONLINE'<\/pre>\n<p>&nbsp;<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-3-direct-seeding-internal.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-9732\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-3-direct-seeding-internal.jpg\" alt=\"blog 100 - AG direct seeding - 3 - direct seeding internal\" width=\"476\" height=\"64\" \/><\/a><\/p>\n<p>Do you notice the command text related to the direct seeding session? VDI_CLIENT_WORKER <span style=\"color: #000000;font-family: Calibri\">seems to indicate that SQL Server is using the virtual device interface internally during the seeding operation (VDI prefix as Virtual Device Interface). If SQL Server uses backup stream and VDI interface internally during seeding operation, it may explain why\u00a0it has to limit concurrent backups in our case.<\/span><\/p>\n<p>How to check if SQL Server uses VDI during direct seeding operation? Well, we know that using VDI implies to use sqlvdi.dll. So my first idea consisted in checking if the corresponding dll is loaded as module used by the sqlservr.exe process and the tasklist tool is a good candidate to answer to our need.<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-4-direct-seeding-sqlvdi-dll.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-9733\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-4-direct-seeding-sqlvdi-dll.jpg\" alt=\"blog 100 - AG direct seeding - 4 - direct seeding sqlvdi dll\" width=\"675\" height=\"344\" \/><\/a><\/p>\n<p>The above picture seems to confirm my assumption but this test is not perfect. Indeed, we may also\u00a0claim that\u00a0anything else\u00a0(excluding the seeding operation itself)\u00a0could have trigger the load of the sqlvdi.dll. So my second idea was <span style=\"color: #000000;font-family: Calibri\">to capture the stack dump from the windbg tool while running the seeding session and here what I was able to see:<\/span><\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-5-direct-seeding-and-windbg.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-9734\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-5-direct-seeding-and-windbg.jpg\" alt=\"blog 100 - AG direct seeding - 5 - direct seeding and windbg\" width=\"1024\" height=\"173\" \/><\/a><\/p>\n<p>We may\u00a0recognize <em>CHadrBuildSourceStateLimitConcurrentBackups<\/em> (similar to value LIMIT_CONCURRENT_BACKUPS value from the <em>hadr_automatic_seeding_state_transition<\/em> event) what is a parameter to the function <em>CallFunctAndResumeBuildTask(). <\/em>Let&#8217;s also notice the use of <em>sqlmin!CHadrBuildSourceStateSeeding::CreateVdiSession<\/em> function that seems to\u00a0confirm that\u00a0SQL Server is using VDI session during seeding process.<\/p>\n<p><span style=\"color: #000000;font-family: Calibri\">Ok after this funny test, let&#8217;s back to something more important to keep in mind: we know that direct seeding will limit concurrent backups. Thus it will imply than our existing RPO may be impacted especially if the seeding operation takes a very long time. <\/span><\/p>\n<p><span style=\"color: #000000;font-family: Calibri\">Happy database seeding!!<\/span><\/p>\n<p>By David Barbarin<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As promised in my prior blog post, we\u2019ll talk now about direct seeding feature and backups. We found an interesting LIMIT_CONCURRENT_BACKUPS value for current state of the hadr_automatic_seeding_state_transition event. As said last time, this value is meaningful by itself. So let\u2019s try to perform a backup while the database is concerned by an active seeding [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":8554,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[466,297,202,860,878,51,566,879],"type_dbi":[],"class_list":["post-8548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","tag-alwayson","tag-availability-groups","tag-backup","tag-direct-seeding","tag-limit_concurrent_backups","tag-sql-server","tag-sql-server-2016","tag-sql-server-2016-alwayson-direct-seeding-and-backup-considerations"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.5) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SQL Server 2016 AlwaysOn: Direct seeding and backups<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations\" \/>\n<meta property=\"og:description\" content=\"As promised in my prior blog post, we\u2019ll talk now about direct seeding feature and backups. We found an interesting LIMIT_CONCURRENT_BACKUPS value for current state of the hadr_automatic_seeding_state_transition event. As said last time, this value is meaningful by itself. So let\u2019s try to perform a backup while the database is concerned by an active seeding [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-07-12T18:27:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"900\" \/>\n\t<meta property=\"og:image:height\" content=\"48\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Microsoft Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Microsoft Team\" \/>\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:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations\",\"datePublished\":\"2016-07-12T18:27:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/\"},\"wordCount\":487,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg\",\"keywords\":[\"AlwaysOn\",\"Availability groups\",\"Backup\",\"direct seeding\",\"LIMIT_CONCURRENT_BACKUPS\",\"SQL Server\",\"SQL Server 2016\",\"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/\",\"name\":\"SQL Server 2016 AlwaysOn: Direct seeding and backups\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg\",\"datePublished\":\"2016-07-12T18:27:03+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/bfab48333280d616e1170e7369df90a4\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg\",\"width\":900,\"height\":48},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/bfab48333280d616e1170e7369df90a4\",\"name\":\"Microsoft Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"caption\":\"Microsoft Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/microsoft-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Server 2016 AlwaysOn: Direct seeding and backups","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:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations","og_description":"As promised in my prior blog post, we\u2019ll talk now about direct seeding feature and backups. We found an interesting LIMIT_CONCURRENT_BACKUPS value for current state of the hadr_automatic_seeding_state_transition event. As said last time, this value is meaningful by itself. So let\u2019s try to perform a backup while the database is concerned by an active seeding [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/","og_site_name":"dbi Blog","article_published_time":"2016-07-12T18:27:03+00:00","og_image":[{"width":900,"height":48,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg","type":"image\/jpeg"}],"author":"Microsoft Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Team","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations","datePublished":"2016-07-12T18:27:03+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/"},"wordCount":487,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg","keywords":["AlwaysOn","Availability groups","Backup","direct seeding","LIMIT_CONCURRENT_BACKUPS","SQL Server","SQL Server 2016","SQL Server 2016 AlwaysOn: Direct seeding and backup considerations"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/","name":"SQL Server 2016 AlwaysOn: Direct seeding and backups","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg","datePublished":"2016-07-12T18:27:03+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-100-AG-direct-seeding-1-blocked-session-e1468353425963-1.jpg","width":900,"height":48},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-2016-alwayson-direct-seeding-and-backup-considerations\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server 2016 AlwaysOn: Direct seeding and backup considerations"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4","name":"Microsoft Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","caption":"Microsoft Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8548"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8548\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/8554"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8548"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}