<?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 QV server DR best practice in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QV-server-DR-best-practice/m-p/1041403#M1253399</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our QV site contain large models and as so, large QVDs (10-20 GB each), which contains historical data updated with incremental process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apparently the DR process that replicates the server (which backs up changes) sees the QVDs as completely changed, so it is backing up about 200 GB daily!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was asked by my system administrator to find the best practice for DR on QV server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess I could split the historical QVD... (although in some cases I need to look in the history with peek functions..)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would love to get any input on that issue, including QV side solutions, as well as DR tools and process solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
    <dc:creator>anatezra</dc:creator>
    <dc:date>2026-01-26T18:19:17Z</dc:date>
    <item>
      <title>QV server DR best practice</title>
      <link>https://community.qlik.com/t5/QlikView/QV-server-DR-best-practice/m-p/1041403#M1253399</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our QV site contain large models and as so, large QVDs (10-20 GB each), which contains historical data updated with incremental process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apparently the DR process that replicates the server (which backs up changes) sees the QVDs as completely changed, so it is backing up about 200 GB daily!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was asked by my system administrator to find the best practice for DR on QV server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess I could split the historical QVD... (although in some cases I need to look in the history with peek functions..)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would love to get any input on that issue, including QV side solutions, as well as DR tools and process solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QV-server-DR-best-practice/m-p/1041403#M1253399</guid>
      <dc:creator>anatezra</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
  </channel>
</rss>

