<?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: Replication for enterprise geodatabase having picture attachment in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577665#M45531</link>
    <description>&lt;P&gt;Use a backup solution for a backup purpose, and a failover solution for a failover purpose.&lt;/P&gt;&lt;P&gt;There is no "best" replication solution here.&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jan 2025 01:00:54 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2025-01-22T01:00:54Z</dc:date>
    <item>
      <title>Replication for enterprise geodatabase having picture attachment</title>
      <link>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577345#M45528</link>
      <description>&lt;P&gt;What is the best replication scenario for Feature Service that has picture attachment ? This feature Layer is consumed by Field Map / Survey123&lt;/P&gt;&lt;P&gt;I want to create a backup so that if there is emergency, I can restore it quickly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2025 09:01:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577345#M45528</guid>
      <dc:creator>yockee</dc:creator>
      <dc:date>2025-01-21T09:01:05Z</dc:date>
    </item>
    <item>
      <title>Re: Replication for enterprise geodatabase having picture attachment</title>
      <link>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577563#M45529</link>
      <description>&lt;P&gt;A replica isn't a backup; it's a point-in-time snapshot.&lt;/P&gt;&lt;P&gt;A true standby database is right pattern for failover/resiliency.&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2025 19:54:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577563#M45529</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2025-01-21T19:54:52Z</dc:date>
    </item>
    <item>
      <title>Re: Replication for enterprise geodatabase having picture attachment</title>
      <link>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577663#M45530</link>
      <description>&lt;P&gt;Ok, got it Vince.&lt;/P&gt;&lt;P&gt;So, if I have to choose a replication method, what would be the best ? One way or Two way ?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 00:23:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577663#M45530</guid>
      <dc:creator>yockee</dc:creator>
      <dc:date>2025-01-22T00:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: Replication for enterprise geodatabase having picture attachment</title>
      <link>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577665#M45531</link>
      <description>&lt;P&gt;Use a backup solution for a backup purpose, and a failover solution for a failover purpose.&lt;/P&gt;&lt;P&gt;There is no "best" replication solution here.&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 01:00:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/replication-for-enterprise-geodatabase-having/m-p/1577665#M45531</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2025-01-22T01:00:54Z</dc:date>
    </item>
  </channel>
</rss>

