<?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 External Repository replication in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/External-Repository-replication/m-p/1826370#M19962</link>
    <description>&lt;P&gt;Hello, I am looking for any advice regarding the following disaster recovery situation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have Environment A and Environment B. For in case of complete disaster in A, we switch over to B.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both environments A and B have their own separate external repositories. However both repositories are named the same.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Env. A: Server Node A // Repository 1&lt;/P&gt;&lt;P&gt;Env. B: Server Node B // Repository 1&lt;/P&gt;&lt;P&gt;To keep both environments in sync, we have replicated databases in the repo for environment A into the repo in B. I was wondering what additional changes need to be made in the repo in B in order for environment B to have seamless functionality? As in the services all start and register correctly in the QMC?&lt;/P&gt;&lt;P&gt;I know there are hostname updates that need to be made to that it knows to accept connections from Server Node B instead of A, but what else is there? The services in Env. B are configured already to point to the name Repository 1 but might there be additional IDs that need to be altered in other tables?&lt;/P&gt;&lt;P&gt;I appreciate any help. Thank you.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 03 Aug 2021 13:51:46 GMT</pubDate>
    <dc:creator>qlik_Maestro</dc:creator>
    <dc:date>2021-08-03T13:51:46Z</dc:date>
    <item>
      <title>External Repository replication</title>
      <link>https://community.qlik.com/t5/Management-Governance/External-Repository-replication/m-p/1826370#M19962</link>
      <description>&lt;P&gt;Hello, I am looking for any advice regarding the following disaster recovery situation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have Environment A and Environment B. For in case of complete disaster in A, we switch over to B.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both environments A and B have their own separate external repositories. However both repositories are named the same.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Env. A: Server Node A // Repository 1&lt;/P&gt;&lt;P&gt;Env. B: Server Node B // Repository 1&lt;/P&gt;&lt;P&gt;To keep both environments in sync, we have replicated databases in the repo for environment A into the repo in B. I was wondering what additional changes need to be made in the repo in B in order for environment B to have seamless functionality? As in the services all start and register correctly in the QMC?&lt;/P&gt;&lt;P&gt;I know there are hostname updates that need to be made to that it knows to accept connections from Server Node B instead of A, but what else is there? The services in Env. B are configured already to point to the name Repository 1 but might there be additional IDs that need to be altered in other tables?&lt;/P&gt;&lt;P&gt;I appreciate any help. Thank you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 13:51:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/External-Repository-replication/m-p/1826370#M19962</guid>
      <dc:creator>qlik_Maestro</dc:creator>
      <dc:date>2021-08-03T13:51:46Z</dc:date>
    </item>
  </channel>
</rss>

