: Ed HAMMOND
We were attempting to use the command on relaunching our server after
an abnormal shutdown.
Please think carefully about that idea.
If there was an abnormal shutdown and the risk is to have lost something, don’t trust verify. Don’t forget, the message is “seems to be ok”. It is not “it is ok”.
You will never know what you just lost. Nothing, something, a lot, you don’t know.
4D offers since 1992 a save way. You know 100% what happend. Just use it.
When 4D starts to write in the data file, it sets a flag. Then it writes new/modified/deleted content and update the index. Then it writes the last operation number in the data file, finally it removes the flag.
Then 4D starts and there is no “dirty” flag, there was no open read operation. No need to verify, that is a fact. Then 4D compares the operation counter with the operation counter in the journal. If both are identical, there was no unsaved data in the cache. No question, it is a fact.
If the operations counter is different AND you followed best practice and both “automatic restore” check boxes are set, 4D automatically integrates the missing operations from the journal in data file and update index. Data is correct, no need to verify, all is fine.
If dirty flag is set, 4D restores last full backup and integrates log file. All data here, all data clean, no need to verify, all is fine.
This are facts.
Verify/Repair is to be used if you have lost your backup disk and your data disk became corrupt. This is a disaster operations, to be used after a fire or massive hardware fault. This is not for daily usage.
Verify cannot find missing or lost or never saved data.