Ways to prevent corruption in FileMaker database
Reasons of corruption in FileMaker Pro:
- Since FileMaker is disk based application, so it just transfer the data as needed in main memory instead of loading the entire database. When it transfer data from main memory to hard disk and you unexpectedly quit the application then it is most likely that your FileMaker database becomes corrupt.
- Unexpected system shutdown due to power failure.
- Virus attack.
- Wrong updation of index file.
- Corruption in layout image.
How to prevent corruption in FileMaker Pro?
- Updated backup: You should maintain regular backup of your database. There are many advanced backup tools available that create multiple copies of database. Needless to say it is much simpler to recover your data from an updated backup instead of time consuming recovery process.
- Save a clone of your database. Clone is important because whenever you make any major changes in your database it is best to work on clone and later on import your data back to main database.
- Avoid unexpected shutdown or termination of application: As we have discussed above that one of the most common reason of FileMaker corruption is unexpected system shutdown or unexpected application termination so to avoid these situation it is recommended to use UPS (uninterrupted power supply).
- File size limit: FileMaker Pro earlier versions have some file size limit and if your file has exceed that limit then there are full chances of corruption. So to avoid corruption make sure your file size does not exceed limit.
- Run hard disk utility: If you have multiple corrupted files on your computer then it might be possible that your hard disk is corrupted. Run advanced utility program to check hard disk corruption.
- Routine maintenance: Routine maintenance of database is required to avoid corruption issue. One of the ways is to compress data to reclaim unused space and to optimize database.
- Run anti-virus software: Now last but not the least is avoid virus attack by running good anti-virus program on your system.
So if you take above precaution then there are minimal chances of FileMaker corruption. However if even after taking above precaution your database got damaged then you should opt for a third party FileMaker Recovery tool. Such tool effectively repair damaged database without making any changes in original database.