{"id":8828,"date":"2016-09-09T05:08:13","date_gmt":"2016-09-09T03:08:13","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/"},"modified":"2016-09-09T05:08:13","modified_gmt":"2016-09-09T03:08:13","slug":"edb-failover-manager-2-1-two-new-features","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/","title":{"rendered":"EDB Failover Manager 2.1, (two) new features"},"content":{"rendered":"<p>In the <a href=\"http:\/\/dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\" target=\"_blank\" rel=\"noopener\">last post we upgraded EDB EFM from version 2.0 to 2.1<\/a>. In this post we&#8217;ll look at the <a href=\"https:\/\/www.enterprisedb.com\/docs\/en\/2.1\/edbfm\/EDB_Failover_Manager_Guide.1.03.html#\" target=\"_blank\" rel=\"noopener\">new features<\/a>. Actually we&#8217;ll look only at two of the new features in this post:<\/p>\n<ul>\n<li>Failover Manager now simplifies cluster startup with the auto.allow.hosts property<\/li>\n<li>efm promote now includes a -switchover option; the -switchover option instructs Failover Manager to perform a failover, promoting a Standby to Master, and then, return the Master node to the cluster as a Standby node. For more information<\/li>\n<\/ul>\n<p>Lets go &#8230;<\/p>\n<p><!--more--><\/p>\n<p>My failover cluster status is still fine:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\tStandby     192.168.22.243       UP     UP        \n\tMaster      192.168.22.245       UP     UP        \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.243 192.168.22.245\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t192.168.22.243\n\nPromote Status:\n\n\tDB Type     Address              XLog Loc         Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       0\/3C000220       \n\tStandby     192.168.22.243       0\/3C000220       \n\n\tStandby database(s) in sync with master. It is safe to promote.\n<\/pre>\n<p>The first bit we&#8217;re going to change is the auto.allow.hosts on the database servers. According to the documentation this should eliminate the need to allow the hosts to join the cluster and registration should happen automatically. So, lets change it from &#8220;false&#8221; to &#8220;true&#8221; on all nodes:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@ppasstandby efm-2.1]$ grep allow.hosts efm.properties\nauto.allow.hosts=true\n<\/pre>\n<p>&#8230; and then lets add all nodes to the efm.nodes files on the witness:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ cat efm.nodes\n# List of node address:port combinations separated by whitespace.\n# The list should include at least the membership coordinator's address.\n192.168.22.244:9998 192.168.22.243:9998 192.168.22.245:9998\n<\/pre>\n<p>When we now shutdown the EFM service on all hosts and bring it up again on the witness what is the result?<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ systemctl stop efm-2.1.service  # do this on all hosts\n<\/pre>\n<p>Lets start on the witness again:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ systemctl start efm-2.1.service\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.243 192.168.22.245\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t(List is empty.)\n\nPromote Status:\n\nDid not find XLog location for any nodes.\n<\/pre>\n<p>So far so good, all nodes are in the &#8220;Allowed&#8221; list. What happens when we start EFM on the current primary node:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@ppasstandby efm-2.1]$  systemctl start efm-2.1.service\n[root@ppasstandby efm-2.1]$ \n<\/pre>\n<p>We should see the node as a member now without explicitly allowing it to join: <\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\tMaster      192.168.22.245       UP     UP        \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.243 192.168.22.245\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t(List is empty.)\n\nPromote Status:\n\n\tDB Type     Address              XLog Loc         Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       0\/3D000060       \n\n\tNo standby databases were found.\n<\/pre>\n<p>Cool, same on the standby node:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbppas edb-efm]$ cat efm.nodes\n# List of node address:port combinations separated by whitespace.\n# The list should include at least the membership coordinator's address.\n192.168.22.244:9998\n[root@edbppas edb-efm]$  systemctl start efm-2.1.servic\n<\/pre>\n<p>What is the status:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\tMaster      192.168.22.245       UP     UP        \n\tStandby     192.168.22.243       UP     UP        \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.243 192.168.22.245\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t192.168.22.243\n\nPromote Status:\n\n\tDB Type     Address              XLog Loc         Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       0\/3D000060       \n\tStandby     192.168.22.243       0\/3D000060       \n\n\tStandby database(s) in sync with master. It is safe to promote.\n<\/pre>\n<p>Perfect. Makes it a bit easier and fewer things to remember to bring up a failover cluster. <\/p>\n<p>Coming to the &#8220;big&#8221; new feature (at least in my opinion): Switching to the standby and making the old master automatically a new standby which follows the new master. According to the docs all we need to do is this:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm promote efm -switchover\n<\/pre>\n<p>Does it really work?<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm promote efm -switchover\nPromote\/switchover command accepted by local agent. Proceeding with promotion and will reconfigure original master. Run the 'cluster-status' command for information about the new cluster state.\n<\/pre>\n<p>Hm, lets check the status:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\tMaster      192.168.22.243       UP     UP        \n\tStandby     192.168.22.245       UP     UP        \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.245 192.168.22.243\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t192.168.22.245\n\nPromote Status:\n\n\tDB Type     Address              XLog Loc         Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.243       0\/410000D0       \n\tStandby     192.168.22.245       0\/410000D0       \n\n\tStandby database(s) in sync with master. It is safe to promote.\n<\/pre>\n<p>It really worked! And backwards:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\n[root@edbbart ~]$ \/usr\/edb-efm\/bin\/efm promote efm -switchover\nPromote\/switchover command accepted by local agent. Proceeding with promotion and will reconfigure original master. Run the 'cluster-status' command for information about the new cluster state.\n\n[root@edbbart ~]$ \/usr\/edb-efm\/bin\/efm cluster-status efm\nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n    Agent Type  Address              Agent  DB       Info\n    --------------------------------------------------------------\n    Witness     192.168.22.244       UP     N\/A       \n    Standby     192.168.22.243       UP     UP        \n    Master      192.168.22.245       UP     UP        \n\nAllowed node host list:\n    192.168.22.244 192.168.22.245 192.168.22.243\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n    192.168.22.243\n\nPromote Status:\n\n    DB Type     Address              XLog Loc         Info\n    --------------------------------------------------------------\n    Master      192.168.22.245       0\/480001A8       \n    Standby     192.168.22.243       0\/480001A8       \n\n    Standby database(s) in sync with master. It is safe to promote.\n<\/pre>\n<p>Cool, that is really a great new feature.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the last post we upgraded EDB EFM from version 2.0 to 2.1. In this post we&#8217;ll look at the new features. Actually we&#8217;ll look only at two of the new features in this post: Failover Manager now simplifies cluster startup with the auto.allow.hosts property efm promote now includes a -switchover option; the -switchover option [&hellip;]<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[713,464,77],"type_dbi":[],"class_list":["post-8828","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-enterprisedb","tag-failover-cluster","tag-postgresql"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>EDB Failover Manager 2.1, (two) new features - dbi Blog<\/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\/edb-failover-manager-2-1-two-new-features\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EDB Failover Manager 2.1, (two) new features\" \/>\n<meta property=\"og:description\" content=\"In the last post we upgraded EDB EFM from version 2.0 to 2.1. In this post we&#8217;ll look at the new features. Actually we&#8217;ll look only at two of the new features in this post: Failover Manager now simplifies cluster startup with the auto.allow.hosts property efm promote now includes a -switchover option; the -switchover option [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-09-09T03:08:13+00:00\" \/>\n<meta name=\"author\" content=\"Open source 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=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 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\\\/edb-failover-manager-2-1-two-new-features\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/4bae5e5dd8c7d48edbd948772b49b202\"},\"headline\":\"EDB Failover Manager 2.1, (two) new features\",\"datePublished\":\"2016-09-09T03:08:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/\"},\"wordCount\":318,\"commentCount\":0,\"keywords\":[\"enterprisedb\",\"Failover cluster\",\"PostgreSQL\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/\",\"name\":\"EDB Failover Manager 2.1, (two) new features - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2016-09-09T03:08:13+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/4bae5e5dd8c7d48edbd948772b49b202\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-2-1-two-new-features\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EDB Failover Manager 2.1, (two) new features\"}]},{\"@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\\\/4bae5e5dd8c7d48edbd948772b49b202\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"caption\":\"Open source Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"EDB Failover Manager 2.1, (two) new features - dbi Blog","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\/edb-failover-manager-2-1-two-new-features\/","og_locale":"en_US","og_type":"article","og_title":"EDB Failover Manager 2.1, (two) new features","og_description":"In the last post we upgraded EDB EFM from version 2.0 to 2.1. In this post we&#8217;ll look at the new features. Actually we&#8217;ll look only at two of the new features in this post: Failover Manager now simplifies cluster startup with the auto.allow.hosts property efm promote now includes a -switchover option; the -switchover option [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/","og_site_name":"dbi Blog","article_published_time":"2016-09-09T03:08:13+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Open source Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4bae5e5dd8c7d48edbd948772b49b202"},"headline":"EDB Failover Manager 2.1, (two) new features","datePublished":"2016-09-09T03:08:13+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/"},"wordCount":318,"commentCount":0,"keywords":["enterprisedb","Failover cluster","PostgreSQL"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/","url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/","name":"EDB Failover Manager 2.1, (two) new features - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-09-09T03:08:13+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4bae5e5dd8c7d48edbd948772b49b202"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-two-new-features\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"EDB Failover Manager 2.1, (two) new features"}]},{"@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\/4bae5e5dd8c7d48edbd948772b49b202","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","caption":"Open source Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8828","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\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8828"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8828\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8828"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}