Hi Rudy, > What I do, is set up the mirror to do the automatic backup, but without a log > file. Whenever there is an issue with the master database, you can restore > the backup of the mirror database and integrate all the incremental log files > that have been generated after the last backup.
If I understand this correctly, you backup the Mirror server (so the 4BK files are from the mirror). Then, if a problem occurs, you restore the 4BK from the mirror server, and then integrate the Journal files from the primary server. I don't think that would work; I am pretty sure you would get an error about the journal file being too recent/old or in some other way not corresponding to the backup... I believe, the correct approach, is to move the remaining journal files to the mirror and let the mirror integrate them as it would normally do so (using the INTEGRATE MIRROR LOG FILE command). ^ This gets your mirror up-to-date. From this point, you could then copy the up-to-date files back to the primary server, then perform a backup and reseed the mirror with the new files. I hope that is clear. Kind Regards, Tim PENNER ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
