Use case: NFS share(s) as file storage for media archiving attached to load-balanced web servers.
Am in the process of completing a move of some archives I host over to NFS shares. I have been creating a separate dataset per each "client/user" and also a unique NFS share for each. Each linux web server then has the multiple NFS shares mounted, symlinked to the appropriate web-root directory. It is important to keep each archive on it own dataset for quota purposes BUT, do I really need to have separate NFS shares? Looking to see if anyone has seen a pro or con in production to multiple shares or just linking to the specific dataset path?
Currently= 4 datasets and 4 NFS shares
Any benefit to = 4 datasets but 1 NFS share?
Thanks
Am in the process of completing a move of some archives I host over to NFS shares. I have been creating a separate dataset per each "client/user" and also a unique NFS share for each. Each linux web server then has the multiple NFS shares mounted, symlinked to the appropriate web-root directory. It is important to keep each archive on it own dataset for quota purposes BUT, do I really need to have separate NFS shares? Looking to see if anyone has seen a pro or con in production to multiple shares or just linking to the specific dataset path?
Currently= 4 datasets and 4 NFS shares
Any benefit to = 4 datasets but 1 NFS share?
Thanks