[mythtv-users] Multiple directories for MythTV recordings?

[Allen T. Gilliland IV]

I am also of the opinion that it would be nice to
support multiple record directories.  I'm not even
thinking about doing anything fancy with nfs or other
backends ... I just want to be able to add more HDD's
to my current backend as easily as possible.

I have an 80 gig drive setup with all my recordings
and system setup on it ... now what if i want to add
another drive for more recording storage?  I have
never really messed with raid, but from my
understanding you wouldn't be able to raid 2 drives
once 1 is already full of data.

This just seems like a feature that would be well
worth supporting.


--- Max <max-mythtv-users at lasevich.net> wrote:
> Sounds like a neat solution. The only potential
> pitfall I can see is what
> will happen if the recording is being viewed while
> transfer is in progress.
> Also I cannot run slave backend on the nfs server
> (it's actually a winblows
> appliance, I've considered loading linux on it, but
> decided it is not worth
> the trouble and time to mess with it.) but I can set
> up a backend on one of
> the non-myth linux servers and access it via NFS.
> But would it not be easier
> to just update the storage path on same server and
> read it via NFS without
> need for second backend? Is the path global for the
> server or is it set per
> file?
> 
> -M
> 
> >
> > Don't know if this would work, but...
> >
> > what if you ran a slave mythbacked process on your
> NFS server.  No tuner
> > card, so it won't try to record anything.  After
> the master backend has
> > recorded a program, you could copy the files over
> to the slave backend's
> > storage directory.  When the files are not found
> on the master backend, it
> > will (I think?) query the slave backend for them. 
> Should be not much load
> > on your NFS box, since all the slave backend would
> be doing is serving
> files
> > for playback (not encoding, decoding or GUI). 
> Actually, now that I think
> > about it, if you set it up so that your
> NFS-mounted storage directory has
> > the same path on both your frontend (NFS client?)
> and slave backend (NFS
> > server), when you play it back it will play
> directly from the NFS-mounted
> > storage directory, so you don't even need a second
> backend running.  The
> > only other thing you'd probably have to do is
> update the 'recorded' table
> > for the moved recordings to reflect the new
> storage host and path.  You
> > could easily automate both the NFS copy/move and
> the database update with
> a
> > script.
> >
> > -JAC
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at snowman.net
> >
>
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
> >
> 
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at snowman.net
>
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users