Hi everyone!
Reading the openbis documentation about archiving ( Data archiving — Python documentation ), it only supports archiving via strongbox.
In our university setting, we have possibility to upload files to a network nfs share that is then backed up and working as a backup archive.
Would it be possible to redirect Openbis archiving feature to dump the datasets on a mounted nfs instead of strongbox?
Dear Farman,
In principle, it does not matter which backend you’re using for archiving, as long as this backend provides a filesystem accessible from the host where openBIS is running on. We mention StrongBox in our documentation (which has been superseded by StrongLink), since the MultiDataSetArchiver (which we’d recommend to use) has been designed to be fully compliant with the features provided by this backend, as described in depth here.
However, it is not compulsory to make use of all the sanity checks and workflows. For example, if your backend is just a plain NFS-mounted disk which itself is not being backed up, you could omit the replication workflow, and hence also skip the specification of parameters such as archiver.replicated-destination.
For specific questions concerned about setting up archiving for your specific infrastructure, please consider opening a ticket with openbis-support@id.ethz.ch.
Thank you Richardw, that was a very helpful answer and clarified a lot of things. I think I’ll be able to relatively easily set it up!
Have a nice weekend,
/Filip