Hi, Tony: Is there a reason why you couldn't just open the 20 questionable files with FM Pro, then immediately close them and put them on the server? I believe that would prevent FM Server from repeating the consistency check. Better yet, perhaps open and save as a compressed copy.
All this short of reverting to backup files or importing from backup data.
I want to be as lazy as possible (but no lazier)!
For example, I have a file that is 1.2 GB that is an archive from a list
server that has been closed. No need to edit or delete.
The file is useful as a read only reference and is currently locked on the
OS X level and hosted on my FileMaker Server.
If the FileMaker Server crashes, there should be no reason to check the file
constancy as it should not be able to change.
No need to exert any time or effort on the file at all if there is a crash.
No need to move, open, etc.
Being as lazy as possible is a legitimate use case that would free me (all
of us) to put my (our) energy into more productive purposes.
On one of the other lists, I got advice from experts that I respect that
caution is advised.
Therefore I am posting here, so that someone familiar with the FileMaker
Server code can offer an authoritative answer to the FileMaker community.
I am able to host a locked file and this has been confirmed by others.
The questions that remain are:
1. Will FileMaker Server skip the consistency check on a file locked on the
OS X level?
2. Is there any danger to hosting or restarting with a file locked on the OS