On Friday 27 June 2014 07:59:14 am Rob Landry wrote: > I have been doing the imports at the studio and synchronizing that > Rvendell system to the one at the transmitter via rsync and a Perl script > that compares the relevant parts of the two MySQL databases. The idea is > that if he loses the RD box at the transmitter, he can temporarily feed > the station through a pair of Barix boxes from an identical box at the > studio (albeit with dropouts) until I can go rescue the one at the > transmitter.
More and more sounds like the perfect rsync job. Remember, rsync was designed for this explicitly. It can use the highest lossless compression possible to transfer data across choked connections. It transfers *only* those parts of a file that have changed. ( or replace the whole file, your choice ) (( in other words, your perl script is redundant, and slow )) It will reconnect and continue on its own. It can establish it's own ssh encrypted compressed channel. ( or any other protocol it knows about ) It can compress some files, but not others. ( if for some reason you want this compressed during transfer, but not that ) And more. Rsync does all of this by passing brief messages from one end to the other for all of the negotiation, again to minimize bandwidth use. About the only thing I think rsync won't do, is to copy from one remote host to another remote host. The only disadvantage in your case that I can imagine, is that the most often you can have all of this checked in 1K or so of message passing, is every minute. -- Cowboy http://cowboy.cwf1.com Micro Credo: Never trust a computer bigger than you can lift. _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
