[Deploying Sakai] Seeking NFS migration advice

[Sam Ottenhoff]

Rsyncing while Sakai is running should be fine.

Linux inotify will tell you about all filesystem change actions.  You can
use a daemon like lsyncd to monitor these inotify events and then rsync
just the changed files every XX minutes.

  https://code.google.com/p/lsyncd/

Alternatively, you could monitor the CONTENT_RESOURCE database table for
modified and added files and perform an rsync on only the modified files.
I've never taken this approach, but it may very well involve decoding the
binary XML info held in that table.

--Sam



On Tue, Feb 3, 2015 at 1:42 PM, Crossman, Eric <ecrossman at ufl.edu> wrote:

>  Here at the University of Florida we are in the midst of migrating our
> Sakai-related NFS exports from one appliance to another (going from EMC
> NSG8 to Isilon). One of the obstacles we have run into is the sheer size of
> our content file system. Our production content file systems is now around
> 9.0 TB. According to our TSM backups, this is well over 10,000,000 files.
> In our attempts to perform incremental rsync updates of this file system to
> the new Isilon NFS mount, we have found that it is taking 11-12 hours to
> complete. Declaring an outage of 12+ hours is obviously unacceptable to our
> users.
>
>
>
> We are trying to determine some alternative approaches in order to
> minimize the downtime required for this transition. We would like to know
> what are the ramifications if we were to rsync sub-sets of the content file
> system while Sakai is still running and available to users. Are there any
> in-memory caches or places in the database that would be out of sync if the
> underlying file system contents changes while Sakai is running? Any other
> considerations that we may be overlooking?
>
>
>
> Are there any other suggestions of other approaches to move the content
> file system?
>
>
>
> Thanks,
>
> Eric Crossman
>
> University of Florida
>
>
>
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20150203/642b48a8/attachment.html