Hi Jeff, This is a great idea, I had not thought of it. Let me repeat it back to see if I have it:
[Server#1] Runs 4D Server that users are actively using. Code in a loop on the 4D Server calls "New Log File" every 10 minutes. Code in the loop then calls LEP to a script to transfer the last journal file to [Server#2]. [Server#2] Runs 4D Server that users aren't aware of. Code in a loop on the 4D Server detects that a complete journal file has arrived (as it will every ten minutes, my uncertainty is how it knows the file transfer is complete) and integrates it using INTEGRATE MIRROR LOG FILE. Code in the loop then calls LEP to a script to transfer this journal file to [Server#3]. 4D Backup runs on this machine and sends its backup file to [Server#3] [Server#3] This is a repository, nothing is actively running on it, it could be iCloud, Amazon S3, etc. Do I have this basically correct? Then some technical questions: It would seem that Server#1 never runs 4D Backup, because any restoration would be done using Server#2. Nevertheless, if Server#1 started up and somehow choked, a "normal" behavior would be to restore from backup and integrate the log file. Since this behavior would be turned off, what is the procedure you use if Server #1 won't start? Do you copy the mirror on Server #2 to Server#1? How do you handle the timing, so that [Server#2] knows that the file transfer is complete and it is OK to integrate the log file? Does [Server#1] somehow send a 'I'm Done' message to [Server#2] in your implementation? What do you do if [Server#1] dies to now point users to [Server#2], assuming the Server application is a built application so that the server address and port number are built into the (built) 4D Client? Many thanks! Bob Miller Chomerics, a division of Parker Hannifin Corporation ********************************************************************** 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] **********************************************************************
