<?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: alf_data moving to network drive in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/alf-data-moving-to-network-drive/m-p/157569#M111740</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is possible provided that the protocol you use to mount the remote drive supports file locking (something that Alfresco tests at startup - you'll get an error message if it doesn't).&amp;nbsp; I believe most modern remote filesystem protocols (including the native Windows CIFS server, NFS, GFS etc.) support locking, so you should be fine if your configuration is relatively standard.&amp;nbsp; That said I'd definitely want to test this in a non-production environment first, both functionally and for performance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for performance, yes it will suffer across the board and not just with CIFS, but the extent to which it will suffer depends on a large number of factors (network bandwidth and latency between the Alfresco server and the file server, network utilisation, Alfresco and file server utilisations, etc. etc.).&amp;nbsp; With a few exceptions, Alfresco tends to be I/O bound (both the database and the filesystem that alf_data resides on) and remote file I/O is rarely anywhere near as fast as local I/O (with the possible exception of a SAN technology).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;That said if all you want to do is mirror the alf_data directory to another machine for backup purposes you might consider using a replicated content store instead, since this can have most of the performance benefits of a local content store, while still mirroring the content off to a remote content store as well.&amp;nbsp; See &lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/wiki/Cluster_Configuration_V1.4_to_V2.1.2" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Cluster_Configuration_V1.4_to_V2.1.2&lt;/A&gt;&lt;SPAN&gt; for details (even though you're probably not configuring a cluster, the configuration for a replicated content store is the same as for a cluster).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another thing I would consider is keeping the Lucene indexes local, but configure the backup-lucene-index directory to be on the remote machine.&amp;nbsp; This will keep Lucene performance high, while still allowing you to backup the Lucene indexes simply by backing up the remote machine's filesystem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2008 06:47:25 GMT</pubDate>
    <dc:creator>pmonks</dc:creator>
    <dc:date>2008-06-05T06:47:25Z</dc:date>
    <item>
      <title>alf_data moving to network drive</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alf-data-moving-to-network-drive/m-p/157568#M111739</link>
      <description>Is it possible to set the alf_data directory to reside on a machine within the network, using a mapped network drive?So have the main Alfresco Install on : C\alfrescoThen the alf_data file store on: x:\alf_dataThe reason for this is that we have a server that we can run alfresco but another file ser</description>
      <pubDate>Wed, 04 Jun 2008 10:44:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alf-data-moving-to-network-drive/m-p/157568#M111739</guid>
      <dc:creator>wiffle</dc:creator>
      <dc:date>2008-06-04T10:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: alf_data moving to network drive</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alf-data-moving-to-network-drive/m-p/157569#M111740</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;This is possible provided that the protocol you use to mount the remote drive supports file locking (something that Alfresco tests at startup - you'll get an error message if it doesn't).&amp;nbsp; I believe most modern remote filesystem protocols (including the native Windows CIFS server, NFS, GFS etc.) support locking, so you should be fine if your configuration is relatively standard.&amp;nbsp; That said I'd definitely want to test this in a non-production environment first, both functionally and for performance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for performance, yes it will suffer across the board and not just with CIFS, but the extent to which it will suffer depends on a large number of factors (network bandwidth and latency between the Alfresco server and the file server, network utilisation, Alfresco and file server utilisations, etc. etc.).&amp;nbsp; With a few exceptions, Alfresco tends to be I/O bound (both the database and the filesystem that alf_data resides on) and remote file I/O is rarely anywhere near as fast as local I/O (with the possible exception of a SAN technology).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;That said if all you want to do is mirror the alf_data directory to another machine for backup purposes you might consider using a replicated content store instead, since this can have most of the performance benefits of a local content store, while still mirroring the content off to a remote content store as well.&amp;nbsp; See &lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/wiki/Cluster_Configuration_V1.4_to_V2.1.2" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Cluster_Configuration_V1.4_to_V2.1.2&lt;/A&gt;&lt;SPAN&gt; for details (even though you're probably not configuring a cluster, the configuration for a replicated content store is the same as for a cluster).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another thing I would consider is keeping the Lucene indexes local, but configure the backup-lucene-index directory to be on the remote machine.&amp;nbsp; This will keep Lucene performance high, while still allowing you to backup the Lucene indexes simply by backing up the remote machine's filesystem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 06:47:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alf-data-moving-to-network-drive/m-p/157569#M111740</guid>
      <dc:creator>pmonks</dc:creator>
      <dc:date>2008-06-05T06:47:25Z</dc:date>
    </item>
  </channel>
</rss>

