I’d like to gather some insights from those with experience managing large media libraries that are exposed by a unified media server, specifically pertaining to Plex/Emby. I’d also appreciate any insights on types of setups that may be adjacent to this idea.
I rapidly filled up about 70 TB of storage, out of 108 TB usable space, on my Plex NAS (which lives on a Synology DS1821+ filled with 18 TB drives) within a year between ongoing weekend hobby BD rips of my physical library and various media hoarding. I’m currently thinking about expansion for the future. For consideration is how to do this while maximizing storage space between split libraries. This Plex library is further split up among sub-libraries per genre. It is all stored within on main directory (“Libraries”). My initial target is probably to double the available storage.
Is it better to:
I rapidly filled up about 70 TB of storage, out of 108 TB usable space, on my Plex NAS (which lives on a Synology DS1821+ filled with 18 TB drives) within a year between ongoing weekend hobby BD rips of my physical library and various media hoarding. I’m currently thinking about expansion for the future. For consideration is how to do this while maximizing storage space between split libraries. This Plex library is further split up among sub-libraries per genre. It is all stored within on main directory (“Libraries”). My initial target is probably to double the available storage.
Is it better to:
- Expand the storage by adding additional expansion units/additional NAS?
- An issue I see here is efficient usage of available storage, as certain sub-libraries will fill up faster than others. Generally connectivity between the pools won’t be an issue, whether over an eSATA expansion unit or an additional NAS over the network.
- Build a bigger NAS with more storage capacity?
- An issue here is eventually a bigger NAS will run out of space as well, thus circling back to the original issue.
- Expand the storage by adding additional expansion units/additional NAS, and tie it together with MergerFS, so that only a single directory is exposed to the media server?
- I don’t have a lot of experience with MergerFS beyond the conceptual level, and will appreciate comments. My general understanding is MergerFS will dynamically allocate files to whatever available storage there is. Wouldn’t this fragment sub-libraries?
- Use a cloud storage provider such as Google to store the bulk of the library in the cloud, while using MergerFS to expose a single directory to the media server?
- This introduces complexity by having part of the storage in the cloud, and no longer available locally. The scenarios I’ve read about have most files pushed to the cloud, then re-downloaded when a file is requested by the media server, then re-uploaded again after the file is no longer needed after a set period of ti There is also an upload limit for most cloud providers, e.g. Google is 50 GB/day.