> On Oct 25, 2019, at 6:40 AM, Tim Nevels via 4D_Tech <[email protected]> > wrote: > > John was using a Time Machine backup and not a 4D backup, which is a > completely different type of backup and one that cannot be totally trusted > like you can with a 4D backup. Time Machine could have been copying the data > file at the exact time a flush was happening and not pick up every data file > change.
Tim, a minor correction. When I did my first “recover from backup”, I used the 4D backup associated with the current datafile and journal. Only after I found that after the recover from backup that the datafile still reported an incomplete flush did I turn to my time machine backups. Even with the time machine backups, I restored earlier 4D backups from time machine and attempted the 4D recover from backup without any success. No matter how far I went back I still could not get it to recover properly. John ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
