Best practice for document network data storage

I’m using Mayan within a Docker setup and it stores all document data in a local docker volume on the docker host. For my production environment I would like to improve the data storage concept in favor of better space and backup possibilities. So I’m planning to move Mayans document storage target to a NAS.

As there are many options to do that I wonder if there is a recommended way for a configuration:

  • What is the best mounting point?

    • OS level (docker host)?
    • docker volume level?
    • Mayan’s config path?
  • Which is the best protocol to use?

    • iSCSI?
    • NFS
    • SMB?

Any better solutions? In may case all components (docker host, NAS, …) are all in local networks, no cloud environment or remote servers are inveolved.

Best regards, Torsten

I would like to know what’s best practice for this situation as well.

Specifically is it better to use Docker Volumes or a Mount point?

Thanks

There is no single best practice.

Like performance tuning, storage layout will depend on the workload of the installation and what are your priorities (speed, bandwidth, concurrency, security, disaster recovery).

Each installation will have its own recommendation of the storages to use and how to use them per app.

Along with support and performance tuning, this is one of the most common works and major benefit of a support plan.

1 Like

I guess a more specific question for me…

Do you see any downside to using Docker Volumes?

We will eventually have around 80,000 documents. And only LAN users will be accessing the documents.