We have a bit of a unique case.
Our files are of audio book segments, some of which are well over an
hour in length.
So we have pretty substantial storage needs but a lower number of
individual files.
I have installed a 5 disk raid device that will let me attach by iSCSI
to the main Rivendell server. From there I also use NFS.
If I had the budget for a 2nd RAID, I would set it up as a shadow
and keep it up to date with rsync and then serve NFS from that.
Or something like that.
Chris Howard
Classic Book Radio
WMFH-LP Columbus, MS
On 1/20/20 7:38 PM, Robert Jeffares wrote:
Hi Steve,
I have a server with 4TB /var/snd with 102541 audio tracks using 3.8
TB. This year we will upgrade to 8TB
I have considered various NAS deployments but have never been that
brave. No reason why they won't work.
Make sure you have 100% backup.
I have a number of client computers who access /var/snd in various
ways. The local network client over NFS operates without issue. A
remote client over VPN worked.
But the big question is what happens to the music scheduler with that
many titles to manage and the answer is it slows down.
The machine creating the music schedules needs ram. Real RAM.
RD and MySQL now Maria will work with what RAM is available, but the
more songs in the library with attendant scheduler codes slows the
process down.
This has nothing to do with where the sound files are stored. It's all
dependent on the capability of the server processor and the amount of
available RAM.
I have a new server in process which will have more RAM to see if I
can get my log assembly time down.
On 21/01/20 8:10 am, Steve wrote:
Hello,
Is anyone using /var/snd over NFS for the server side in a
server/client setup? We have NFS in use for /var/snd for all of the
clients
but the disk location of /var/snd is physically in the same machine
as the Rivendell server itself.
The problem is that we need disk space, lots of it, to store all of
the music - thousands of CDs that need to be ripped. I'd like to
deploy a virtual machine running CentOS as the Rivendell server and
then create an NFS-shared directory on a NAS that would be mounted
remotely (in the same LAN) as /var/snd on the Rivendell server. Maybe
that leads to another issue: What are the practical limitations
of the built-in music scheduler in handling that much music? Should
we limit the amount of schedule-eligible music?
I've gathered from the mailing list archive that there have been
mixed results for this scenario.
Steve
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
