<?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: multi-node-with-shared-persistence-distributed-db-and-file-storage failover in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433308#M430843</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you need to handle in some way the Repository and shared folder fault. Qlik Sense does not offer an Out-of-the-box solution, that's why you need to wider scenarios considering standard ways to make a system reliable. What I proposed so far are just some (not exhaustive) options.&lt;/P&gt;&lt;P&gt;My best advice, if you have any doubt about the topic, is to involve Qlik Consultant or a Certified Qlik Partner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 01 Oct 2017 19:38:24 GMT</pubDate>
    <dc:creator>Vincenzo_Esposito</dc:creator>
    <dc:date>2017-10-01T19:38:24Z</dc:date>
    <item>
      <title>multi-node-with-shared-persistence-distributed-db-and-file-storage failover</title>
      <link>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433305#M430840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi techies,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have deployed one shared persistence where I have created one central node Server1 , RIM node as Server2&amp;nbsp; same acting as Failover candidate, one node for Repository database and One is for Application strorage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can make failover candidate of Central node but how to save these two repository and shared application server if anyone of them get down ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Sep 2017 12:06:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433305#M430840</guid>
      <dc:creator>rohitk1609</dc:creator>
      <dc:date>2017-09-28T12:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: multi-node-with-shared-persistence-distributed-db-and-file-storage failover</title>
      <link>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433306#M430841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;Hi Rohit, have a look here&amp;nbsp;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/276321"&gt;https://community.qlik.com/thread/276321&lt;/A&gt;, you need to rely on different standard e.g.&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp; SAN/NAS on RAID Disks for Shared folder&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp; Postgres HA for the Repository&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp; Rely on a Virtual HA solution like VMWare HA for the Repository and/or Shared folder&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Oct 2017 17:01:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433306#M430841</guid>
      <dc:creator>Vincenzo_Esposito</dc:creator>
      <dc:date>2017-10-01T17:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: multi-node-with-shared-persistence-distributed-db-and-file-storage failover</title>
      <link>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433307#M430842</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you saying just to avoid single point failure we should store our repository and apps in other location. and you have mentioned some ways where to store apps and repository ?? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Oct 2017 18:55:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433307#M430842</guid>
      <dc:creator>rohitk1609</dc:creator>
      <dc:date>2017-10-01T18:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: multi-node-with-shared-persistence-distributed-db-and-file-storage failover</title>
      <link>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433308#M430843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you need to handle in some way the Repository and shared folder fault. Qlik Sense does not offer an Out-of-the-box solution, that's why you need to wider scenarios considering standard ways to make a system reliable. What I proposed so far are just some (not exhaustive) options.&lt;/P&gt;&lt;P&gt;My best advice, if you have any doubt about the topic, is to involve Qlik Consultant or a Certified Qlik Partner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Oct 2017 19:38:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/multi-node-with-shared-persistence-distributed-db-and-file/m-p/1433308#M430843</guid>
      <dc:creator>Vincenzo_Esposito</dc:creator>
      <dc:date>2017-10-01T19:38:24Z</dc:date>
    </item>
  </channel>
</rss>

