[ome-users] suggestions for FS managed repository layout (omero.fs.repo.path)

[Carnë Draug]

Hi

We are considering changing the layout of the FS managed repository [1]
in our main omero instance because it's growing too large and is
causing issues for our IT department to perform the backups.

Our idea is that by having time at the root of the layout instead of
usernames we could have individual partitions for older years.  These
partitions could be mounted read only and a backup archived (I'm
hoping OMERO can handle it properly if a user tries to delete data
from a read-only filesystem).

So something like:

    %year%-%month/%user%_%userId%/%time%

or even something like:

    %year%-%month%/%time%

since the actual user is not that important at this level.  Has anyone
tried alternative layouts?  I remember the OMERO FS workshop at OME
user's meetings [2] having some suggestions but has anyone tried
different layouts and could share their experience?  What's the
advantages of different layouts and what possibilities do they enable?

Also, I understand that omero.fs.repo.path does not automatically move
any files or changes their paths in the database.  Is there any
"sanctioned" tool to perform this job?  Or are we advised,
understandably, against messing with things at that level?

Thank you
David

[1] https://docs.openmicroscopy.org/omero/5.3.5/sysadmins/config.html#omero-fs-repo-path
[2] http://downloads.openmicroscopy.org/presentations/2014/Paris-Workshops/OMERO-FS-Workshop/#/13