![]() ![]() Open FileMaker, and from the menu select File > Recover….A clone is nice because it will make the recovery faster, but it will not tell you if the corruption is in your data and not your schema. Make a compacted copy or clone of the backup.Ideally, move this file to a non-server machine (it’s best not to take up resources on the server machine) Grab a recent backup of the file you think may be corrupted.Here is a step by step guide to running a recovery process: How can I verify if my file is corrupted?įileMaker has a Recovery feature that allows you to determine if your file is safe to use or not. Generally, if something seems fishy, it’s worth ruling out corruption!.If the file size increases dramatically from one backup to the next, without a large data increase to explain it, it’s possible that corruption is the cause.If you are working in Manage Database on a hosted file and you lose connectivity to the file while Manage Database is open, your file may be corrupted.You should always back up your backup copies, not the hosted files located inside the FileMaker Server > Data > Databases. Time Machine, Crashplan, etc.) is backing up the hosted FileMaker files, they could get corrupted. If your OS level backup software on your server (i.e.For example, if there was a power outage. ![]() If that ever happens, you should verify there is no corruption.
0 Comments
Leave a Reply. |