[JPR]
Hi Justin,

Tim's explanation is the good one. When 4D starts flushing the cache, it writes 
a flag into the .4DD file, and clears it when the flush is complete. 

Here are some answers:

> Are you sure the marker is stored in the data file?
Yes, I do.

> If I restore a backup from Time Machine that I know was good and verify the 
> records in the MSC, the verify fails saying the last database flush did not 
> complete.
When you do a backup with any other program than 4D, including Time Machine, 
you backup what is on disk, but not the cache itself. This is why only 4D 
Backup can be trusted.

> I would think that the marker is stored someplace else. 
No, it's not.

> If I run a repair on the datafile 4D crashes. I have tried to run the repair 
> several times and it crashes at the same spot every time.
Then you probably have a damaged sector on your disk, or at least a damaged 4D 
block that 4D cannot read and process.

> I ran a repair on the structure and it failed reporting that the flush did 
> not complete.
Yes, because the flag is not in the structure file.

> Finally I ran a repair on the datafile using record headers and it looks like 
> I am back in. Just waiting on reindexing to finish.
This is one of the 2 safe solutions. Almost. But not 100% reliable. You may 
have lost some record(s) and the data integrity is not guaranteed. For 
instance, you may lose Client record, but still have Invoices for this Client. 
This is the last solution when everything else has failed.

The only 100% accurate way is to restart from the Backup file (made by 4D) and  
integrate the current log file(s). This is the only way to be sure of the data 
integrity.

My very best,

JPR

PS: Data Analyzer can show you where is the Cache Flushing Flag, but doesn't 
allow you to clear it, for it is the worst thing to do...


**********************************************************************
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]
**********************************************************************

Reply via email to