<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cluster failover in Sense doesn't work. in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927391#M22056</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/178668"&gt;@Jio&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you completely shut down the central, the failover won't work.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Failover works if Engines, Proxy, Scheduler, Printing or Repository services are stopped.&lt;/P&gt;
&lt;P&gt;But if you stop the Repository DATABASE service, then nothing will work anymore.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For such scenario, you would need to install the Repository Database in a dedicated server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the below article we mention it:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Knowledge/Failover-Central-node-requirements-and-considerations/ta-p/1713240" target="_blank"&gt;https://community.qlik.com/t5/Knowledge/Failover-Central-node-requirements-and-considerations/ta-p/1713240&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;
&lt;P&gt;Benoit&lt;/P&gt;</description>
    <pubDate>Fri, 06 May 2022 14:35:05 GMT</pubDate>
    <dc:creator>Benoit_C</dc:creator>
    <dc:date>2022-05-06T14:35:05Z</dc:date>
    <item>
      <title>Cluster failover in Sense doesn't work.</title>
      <link>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927202#M22054</link>
      <description>&lt;P&gt;Hallo All,&lt;/P&gt;
&lt;P&gt;we have a multi node sense deployemnt.&lt;/P&gt;
&lt;P&gt;Everything is registers well in QMC. The central en Rim node works fiine.&lt;/P&gt;
&lt;P&gt;but when we shut &amp;nbsp;down the central node, the Rim node Doesn’t take over the funtion of the central node even after 15 minutes ( waittime is 10 minutes).&lt;/P&gt;
&lt;P&gt;the is no firewall Between the systems. And every tcp Port is accessible booth sides.&lt;/P&gt;
&lt;P&gt;Any ons aan Kees wherry to check and how to solve this.&lt;/P&gt;
&lt;P&gt;Extra info: the postgresql is ruiming om the Central node (by &amp;nbsp;default)&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2022 07:56:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927202#M22054</guid>
      <dc:creator>Jio</dc:creator>
      <dc:date>2022-05-06T07:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover in Sense doesn't work.</title>
      <link>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927391#M22056</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/178668"&gt;@Jio&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you completely shut down the central, the failover won't work.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Failover works if Engines, Proxy, Scheduler, Printing or Repository services are stopped.&lt;/P&gt;
&lt;P&gt;But if you stop the Repository DATABASE service, then nothing will work anymore.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For such scenario, you would need to install the Repository Database in a dedicated server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the below article we mention it:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Knowledge/Failover-Central-node-requirements-and-considerations/ta-p/1713240" target="_blank"&gt;https://community.qlik.com/t5/Knowledge/Failover-Central-node-requirements-and-considerations/ta-p/1713240&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;
&lt;P&gt;Benoit&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2022 14:35:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927391#M22056</guid>
      <dc:creator>Benoit_C</dc:creator>
      <dc:date>2022-05-06T14:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover in Sense doesn't work.</title>
      <link>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927405#M22057</link>
      <description>&lt;P&gt;Hello Benoit_C,&lt;/P&gt;
&lt;P&gt;Thanks for the response.&lt;/P&gt;
&lt;P&gt;Now i understand it. To use Qliksense for Failover (Cluster services), you need to put the fileshare and the Reporsitory database on a different dedicated server.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many Thanks,&lt;/P&gt;
&lt;P&gt;Regards&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jio&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2022 15:24:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927405#M22057</guid>
      <dc:creator>Jio</dc:creator>
      <dc:date>2022-05-06T15:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster failover in Sense doesn't work.</title>
      <link>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927763#M22060</link>
      <description>&lt;P&gt;Hello Jio,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm glad it has been an useful answer.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Benoit&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 06:11:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Cluster-failover-in-Sense-doesn-t-work/m-p/1927763#M22060</guid>
      <dc:creator>Benoit_C</dc:creator>
      <dc:date>2022-05-09T06:11:42Z</dc:date>
    </item>
  </channel>
</rss>

