Database verification schedules: what they check and when to run them
BeginnerLearn how FileMaker Server's Verify schedule works, what it detects, and how to interpret the results.
What you'll learn
- What a Verify schedule checks and what it does NOT repair
- How to create and schedule a verification
- How to interpret the result in the Event Log
A Verify schedule checks a hosted database block by block for corruption without taking it offline. It is the safest way to get early warning of disk-level damage before a full recovery becomes necessary.
Stuck is a valid status
Need a second brain on this one?
If this lesson just collided with your real schema, script stack, or deadline, book consulting and turn the confusion into a concrete plan.
What Verify checks
Verify reads every block of the .fmp12 file and confirms the data integrity checksum. It detects physical corruption — damaged pages caused by disk errors, bad sectors, or interrupted writes. It does NOT check data logic, relationships, or script correctness. Verify does not repair damage; it reports it.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo