[mythtv-users] Additional Storage

Ryan Steffes rbsteffes at gmail.com
Tue Nov 27 15:31:49 UTC 2007

On Nov 27, 2007 10:08 AM,  <jedi at mishnet.org> wrote:
> > Jay R. Ashworth wrote:
> >>
> >> There is one reason why that's not the same (and not quite as good) as
> >> merely copying the dump file...
> >>
> >> If you copy the dump file, you only have to lock the whole database
> >> *once*, and all your backup files are exactly the same.  This can be
> >> useful...
> OTOH, doing a remote dump only requires the same network
> access that MythTV itself does. You don't have to setup
> anything extra. You don't worry about how you are going to
> get the other exact copy to the separate machine.
> For this application, locking the database more than once is
> a relatively minor issue. It's a very small, low transaction
> volume database.

Well that just depends on your timing.  Locking the database three or
four times for twenty to thirty seconds each would be annoying, but
probably not catastrophic, during recording or commflagging.

As for moving it, you can add in a call to scp to copy the file over
ssh with only a small bit of additional work to set up a key file.
(Process described here: http://www.linuxjournal.com/node/8600/print )

More information about the mythtv-users mailing list