On Tue, Mar 16, 2010 at 10:13 AM, Steven M. Caesare <[email protected]> wrote: > If the originating app isn’t prepared to do anything than write a single log > file without closing, then figuring out how to do deltas on a currently open > file seems “challenging” to say the least.
Seriously? We're talking about a program that simply continuously appends to a log file. The concept has been around since the dawn of the computer age. I'm pretty sure rsync would do a fine job at this. It's lightweight and and only does "delta" copies. It should be able to cope with satellite latency fairly well. Run it on a schedule as often as you need/want. The only potential problem might be if the writing program has opened the file in such a way that it locks it against any other program even reading it. (Windows has a crazy number of different ways to open a file, and some of them default to rather restrictive locking.) If this is a problem, then ROBOCOPY with the /B switch to another local file (and then rsync the other file) might work around that. (/B tells ROBOCOPY to request "backup semantics", which is another one of those ways to open a file. Sometimes it works around locking issues.) -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
