<?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: High Availability Configuration in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/high-availability-configuration/m-p/27542#M13863</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;They do rely on the secondary stores being network drives or local systems.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We don't have a remote content store to act as secondary content stores.&amp;nbsp; Such remote replication can be done with RSync, but to have full transactional replication, we'd have to think about writing a remote ContentStore.&amp;nbsp; Effectively, acting as a mapping service for file distribution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For inbound replication (i.e. a server lazily pulling the content in from a remote location), we could write a store on top of the webdav or web service interfaces.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 May 2006 16:02:58 GMT</pubDate>
    <dc:creator>derek</dc:creator>
    <dc:date>2006-05-18T16:02:58Z</dc:date>
    <item>
      <title>High Availability Configuration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/high-availability-configuration/m-p/27541#M13862</link>
      <description>I've been reading http://wiki.alfresco.com/wiki/High_Availability_Configuration and I am still confused about the content store replication setup.&amp;nbsp; It seems that the replication options (ReplicatingContentStore or ContentStoreReplicator) rely on the fact that the secondary stores will be mount point</description>
      <pubDate>Fri, 12 May 2006 15:34:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/high-availability-configuration/m-p/27541#M13862</guid>
      <dc:creator>ethanadams</dc:creator>
      <dc:date>2006-05-12T15:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability Configuration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/high-availability-configuration/m-p/27542#M13863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;They do rely on the secondary stores being network drives or local systems.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We don't have a remote content store to act as secondary content stores.&amp;nbsp; Such remote replication can be done with RSync, but to have full transactional replication, we'd have to think about writing a remote ContentStore.&amp;nbsp; Effectively, acting as a mapping service for file distribution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For inbound replication (i.e. a server lazily pulling the content in from a remote location), we could write a store on top of the webdav or web service interfaces.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 May 2006 16:02:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/high-availability-configuration/m-p/27542#M13863</guid>
      <dc:creator>derek</dc:creator>
      <dc:date>2006-05-18T16:02:58Z</dc:date>
    </item>
  </channel>
</rss>

