We have a new Synology NAS (roughly 120TB usable) that I hope will replace about 3 separate media servers.
We have the following media-rich teams:
- Video (unsurprisingly huge storage needs)
- Web (surprisingly small storage needs)
- Art/Design (medium needs, often sharing content with everyone else)
- Radio (lots of audio, around 1TB so far)
I’ve gone back and forth on how to carve it up, but I know ultimately, I want to have the following conceptual shares:
Shared Folder Concepts:
- Active Working storage (current projects for up-coming events/delivery dates)
- Archive Storage (already produced and delivered, completed projects, preferably keeping items for 15 months before putting in “cold storage”)
- Library storage (common media re-used throughout the years, purchased transitions, audio packs, logos, etc.)
One non-shared volume:
- Cold Storage (likely one copy on Tape, and another copy in Azure Archival storage, only for critical files we never want to lose but don’t need on a regular basis, like teaching library masters)
The big concept I’m battling with now, is should I create 3 file shares and give all media teams access to all of them? Should I create a file share for each media team and then make folders within each of those for these 3 purposes?
Some things to consider:
- During active work is when media teams need to share the most.
- If I don’t set limits, media will just get stored in whatever volume has the most space.
- If I don’t make Archive or Library Storage read-only, it will be used as working folders.
Here’s what I think my next steps are based on what I’ve written above:
- Create a single 20TB “Work” share for current projects, and create sub-folders for each team allowing them to manage their working files in their preferred manner. All media staff would have read/write access to all folders in the Work share (I’m not messing with non-inherited permissions)
- Create a single 80TB “Archive” share for archives that we want access to reference throughout the year (this is that rolling 15 months), making it read-only for everyone and only allowing one “archiver” per team (to discourage it becoming a working folder)
- Create a single 20TB “Library” share for library files that is read-only for everyone and allowing only one “librarian” per team.
- Work with each team to make sure they understand what goes where and establish a schedule for archiving.
- Share sizes are not going to be carved into dedicated volumes (we just have one massive RAID 6 volume), they will just have a quota.
- Over the years we will add additional shelves of storage, possibly adding faster storage for editing directly from the storage array.
- Working folders will have nightly incremental backups with a rolling 14 days of retention to the older server this is replacing.
- Archival folders will have incremental backups taken nightly to tape with unlimited retention, and we’ll just cycle tapes every 6 months.
- Library folders will have incremental backups taken nightly to tape with unlimited retention, and we’ll cycle those tapes every 6 months as well, but I will also have them backed up nightly with only 7 days of retention somewhere local.
Any thoughts on this plan? I know every team is different, but I also know there are some common pitfalls the first time you do something like this that some of you may have run in to.