We run a mirror here -- soon to be several mirrors. Overall it works great. There's practically zero overhead in the "New Log File" command (milliseconds). My only advice would be to make the transfer of the logs happen outside of 4D. Write a script in Python or PowerShell to handle the moving of the journal files from the production server to the mirror, and maintain an archive of all your journal files in case you need to restore a backup and integrate them all again.
-- Jeffrey Kain [email protected] > On Mar 21, 2017, at 4:44 PM, Cannon Smith via 4D_Tech <[email protected]> > wrote: > > Hi Paul, > > I’m just working out how to do this theoretically at the moment. But, no, > they won’t be on the same local network. I want them geographically diverse. > And I think I want an additional place (FTP site) that is away from both of > them to keep a copy of each log file in case the mirror can’t be reached for > awhile. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
