For most of the rows, this will be a “0”.
The 2nd column in the FileMaker Recovery Tool is an error code column. You can look through this log file to get a little more detail on what has failed. For instance, your folders may look like – Good_Removed, Good_And_Morning_Removed, and so on.Ī log file gets generated when you perform a recovery. Create a new folder for each stage you are working and have the folder name be a very specific description of where you are in the surgery. Perform Surgeryīefore starting with the repair process, save copies of the file as you go along. Import data into the new file with the most recent data, and host your updated file as a replacement of your corrupted file. Keep in mind, if there has been any code, or layout or schema changes in production since the last good backup, you will need to repeat those changes. Create a clone of the good backup and create a compact copy of the clone. Run your recent backups through the recovery process until you find the most recent backup that passes the recovery check. Once you identify a corrupted file, you have two options to repair it – Revert to a Backup or Perform Surgery. Once the recovery process is complete, FileMaker will alert you if there were any issues found. Check the consistency of the file first and then continue with the recovery process. Select the compacted copy/clone and run the recovery. Once completed, open FileMaker and from the menu select File > Recover. Make a clone, as it works well and makes the recovery faster, but it will not tell you if the corruption is in your data and not your schema. Move this file to a non-server machine and don’t take up resources on the server machine. To verify a corrupted file, start with a recent backup of the file you think may be corrupted.
If you are working within the Manage Database option on a hosted file and you can’t access the file while open, your file may be corrupted.
Always clone your ‘backup copies’, not the hosted files located inside the FileMaker Server > Data > Databases
If your OS level backup software is backing up the hosted FileMaker files, they could get corrupted.If you have a habit of shutting down the server machine without properly closing down the files in FileMaker Server, then you should verify the corruption.Unexpected or unexplained behavior with the file.If you are experiencing the following issues, chances are that your file may be corrupted:
Fortunately, while it’s an inconvenience, it’s not normally a disaster and we’ll explore how to identify whether your file is corrupted, how to repair a corrupted file with FileMaker recovery tool. File corruption can happen anytime, no matter how hard we try to prevent it.