{"id":6068,"date":"2024-11-25T14:03:21","date_gmt":"2024-11-25T22:03:21","guid":{"rendered":"https:\/\/jetstreamsoft.com\/portal\/?post_type=ht_kb&#038;p=6068"},"modified":"2024-11-25T14:04:13","modified_gmt":"2024-11-25T22:04:13","slug":"point-in-time-recovery-error-failed-to-reach-server","status":"publish","type":"ht_kb","link":"https:\/\/jetstreamsoft.com\/portal\/jetstream-knowledge-base\/point-in-time-recovery-error-failed-to-reach-server\/","title":{"rendered":"Point in Time Recovery Error: &#8220;Failed to reach server&#8221;"},"content":{"rendered":"\n<p class=\"is-style-info wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">This article applies to JSDR software version(s) 4.2.x.xxx and above.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem<\/h2>\n\n\n\n<p class=\"\">The error message &#8220;<em>Failed to reach server<\/em>&#8221; can appear under certain circumstances when using Point in Time Recovery (PITR). Here are two common examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Enabling PITR on a protected domain that was initially configured <em>without<\/em> PITR, may display the error message &#8220;<em>Failed to reach server.<\/em>&#8220;<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img fetchpriority=\"high\" decoding=\"async\" width=\"500\" height=\"220\" src=\"https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server.png\" alt=\"\" class=\"wp-image-6069\" srcset=\"https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server.png 500w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server-300x132.png 300w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server-50x22.png 50w\" sizes=\"(max-width: 500px) 100vw, 500px\" \/><figcaption class=\"wp-element-caption\">Error message appears when PITR is enabled on a non-PITR domain.<\/figcaption><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">After (correctly) initiating a PITR session on a PITR domain, the action may stall for an extended period of time and then display the error message &#8220;<em>Failed to reach server.<\/em>&#8220;<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full is-resized\"><img decoding=\"async\" width=\"800\" height=\"630\" src=\"https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server2.png\" alt=\"\" class=\"wp-image-6070\" style=\"width:641px;height:auto\" srcset=\"https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server2.png 800w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server2-300x236.png 300w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server2-768x605.png 768w, https:\/\/jetstreamsoft.com\/portal\/wp-content\/uploads\/2024\/11\/failed-to-reach-server2-50x39.png 50w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><figcaption class=\"wp-element-caption\">Error message appears after the PITR session does not start.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li class=\"\">Ensure the PITR function is being operated correctly.\n<ul class=\"wp-block-list\">\n<li class=\"\">E.g., The protected domain must be enabled for PITR before a PITR session can be started.<br><br><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li class=\"\">This problem can also occur if there are any issues with the DRVA associated with the protected domain.\n<ul class=\"wp-block-list\">\n<li class=\"\">Ensure the DRVA VM is up and running.<\/li>\n\n\n\n<li class=\"\">Ensure there are no network issues with the DRVA.<\/li>\n\n\n\n<li class=\"\">Check the operation and performance of DRVA-to-MSA communication.<\/li>\n\n\n\n<li class=\"\">Verify the replication log volume is not reporting any errors.<br><br><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p class=\"is-style-alert wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">The DRVA must be fully functional for PITR sessions to operate correctly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Problem The error message &#8220;Failed to reach server&#8221; can appear under certain circumstances when using Point in Time Recovery (PITR). Here are two common examples: Troubleshooting<\/p>\n","protected":false},"author":1,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"ht-kb-category":[92],"ht-kb-tag":[214],"class_list":["post-6068","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-troubleshooting","ht_kb_tag-vmprotection"],"_links":{"self":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/6068","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/comments?post=6068"}],"version-history":[{"count":1,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/6068\/revisions"}],"predecessor-version":[{"id":6071,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/6068\/revisions\/6071"}],"wp:attachment":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/media?parent=6068"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-category?post=6068"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-tag?post=6068"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}