[mythtv-users] feature request for a backup recording location and db incase of a master server failure

[Aran Cox]

On Mon, Nov 10, 2003 at 06:36:09PM -0800, Chris Germano wrote:
> There is another problem that I have neglected is the fact that the remote myth will be sharing the master SQL database and I guess it wouldn't solve anything if it can't connect with it to begin with. Anyway this would be another area for some improvement. Integrate a thread into myth that listens for the connection of the DB, makes periodic backups of it localy and if the main connection should fail it could switch over to the local copy. It would have to have some kind of master overide setup (and AI) for when it connects again to merge the tables but this would allow the networked myths to be more reliable and independent if something happens to the server. I also recommend having it notify visually, like an alert that states the database hasn't synced up in a while or something like that if this feature is every implemented. Don't say this is a waste of time because having two seperate databases really sucks and defeats the whole purpose of mythtv's networkability interface for sharing records and tuners.

I think maybe you're asking a lot here.  Maybe you should look into 
MySQL's replication features?  As I recall they were mostly one way
but perhaps they've gotten more sophisticated since I last looked
at them.

Aran

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-users/attachments/20031114/33f7ff32/attachment.pgp