![]() 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. Any time you shut down your server machine without properly closing down the files in FileMaker Server.Unexpected or unexplained behavior (for example an odd behavior will start happening once in a while and the only way to fix it is to restart FileMaker).Repeated crashing of the FileMaker file.You may suspect your file is corrupted if you are experiencing and of the following: ![]() How do I know if my file might be corrupted? This guide will detail out how to determine if your FileMaker file is corrupted, what to next, and how to prevent it from corrupting again in the future. It’s part of software, and sometimes no matter how hard we try to prevent it, it still happens.
0 Comments
Leave a Reply. |