Re: In-place importing as sysadmin
Posted: Wed Feb 14, 2018 4:32 pm
What I mean is that, since I'll be the only person running in-place imports and since those will be outside normal working hours, I can have repo path by default pointing to a subdirectory that is a share, and when in-place imports are necessary:
1) change repo path to exclude the subdirectory - new files will be saved locally on the OMERO.server machine
2) Run in-place imports - those should work since symlinks would be between the OMERO.server machine and the storage server where the data is
3) change repo path back to including the subdirectory - new files are again saved on a remote share
Is that a bit clearer? As an example, out current data dir is /data/omerodata, which is itself a symlink to a mount point. If I make that a local directory and create a new symlink for the same mount point at /data/omerodata/remote, I can include "/remote/" on my default repo path, remove it any time I need to run an in-place import, and add it again at the end of it. In my mind, that works just fine!
1) change repo path to exclude the subdirectory - new files will be saved locally on the OMERO.server machine
2) Run in-place imports - those should work since symlinks would be between the OMERO.server machine and the storage server where the data is
3) change repo path back to including the subdirectory - new files are again saved on a remote share
Is that a bit clearer? As an example, out current data dir is /data/omerodata, which is itself a symlink to a mount point. If I make that a local directory and create a new symlink for the same mount point at /data/omerodata/remote, I can include "/remote/" on my default repo path, remove it any time I need to run an in-place import, and add it again at the end of it. In my mind, that works just fine!