You should look into setting up a mirror backup. You could write code to create a new journal file every 10 minutes (one line of code, not counting the scheduling loop), and then a (.bat/python/vba) script to transfer that journal file to the mirror server. On the mirror, integrate the journal and then copy it to a journal archive folder, which gets backed up safely to a remote site, Amazon S3, wherever.
Schedule a nightly 4D backup to run on the mirror, and ship it off site as well, and you'll be able to completely recover to within 10 minutes of the disaster, even if your entire data center gets destroyed. Jeff -- Jeffrey Kain [email protected] > On Sep 10, 2017, at 3:28 PM, Ronald Rosell via 4D_Tech <[email protected]> > wrote: > > Ideally we’d like the log files to be backed up remotely far more frequently > than the once-a-day full backups. Every ten minutes should do it. That way, > in the event of a catastrophic failure we could use the previous night’s > backup and the log file to reconstruct almost all of our data (up to the > 10-minute window). ********************************************************************** 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] **********************************************************************
