The mysql database is just a bunch of files too. Why not just stop the database and rsync them with the .nuv files then start it up again? Look for ,frm, ,myd, and .myi files.
On 4/15/05, Robert Johnston <[EMAIL PROTECTED]> wrote: > On 4/15/05, Mark Gardner <[EMAIL PROTECTED]> wrote: > > > I like to share recordings between two backends - one > > > in the US and one in Germany. Has anyone done this > > > yet? Or an idea how to do that. Data could be rsync'ed > > > over night but how to get the database updated or how > > > to select the recordings I want. This would be a nice > > > new feature. > > > Thanks. > > > > I think Rsync would be your best option for the Data Portion. One > > idea would be to just point myhth backend to only one of the Mysql > > Servers. IE both US and Germany point to the Mysql instance in > > Germany. (Then again i don't know how heavily the database is hit when > > starting a show or if the lag would be acceptable.) > > I'm not sure how it's done in MySQL, but in MSSQL you'd use the > Replication Service for this, which would keep both DB's in sync > pretty much all of the time, and isn't that heavy. Try searching for > "MySQL Replication" and see if that helps > -- > Robert "Anaerin" Johnston > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
