The following two notification emails were sent out: The schedule reported that the database failed a consistency check. The file opened without any errors at that time.Ī few days later, FileMaker Server ran a weekly backup with verification enabled. ![]() Progressive backups had been turned on, so I replaced the database with a progressive backup from 11:44 am – right before the crash. I checked the Windows Server system and event logs to pinpoint the time of the server crash. Database may be damaged use the Recover command in FileMaker Pro 16. FileMaker Server 16.0.3 on FMS reported the following event:.Note that, because there are certain details of my client’s environment that I do not want to publicly disclose, I changed the FileMaker host name to “FMS” and the database file name to “FMDB”. (This particular solution consists of just one file.) It said the database was damaged and could not be opened.īelow is the full notification that was sent. I learned about the outage about an hour later, thanks to a 12:40 pm FileMaker Server email notification. My client’s server crashed on Tuesday, April 17th at 11:45 am. Error 242 Database could not be opened may be damaged What follows is an account of how the new Data Migration Tool made it possible for me to quickly address a database corruption issue for one of our clients. This is exactly what happened to me not too long ago. However, if you find yourself in a situation where you have to recover from a damaged file, you will suddenly develop a strong appreciation for the existence of this new tool. The second use case will probably not garner as much notice. Please see my colleague Matt Hintz’s post for a detailed examination of this use case. The first use case is likely to receive the most attention. Revert to a known clean clone by migrating data from a damaged production file.Deploy development changes by migrating production data into a development file.The Data Migration Tool has two primary use cases: has rolled out a new tool to make migrating data between copies of a database file much faster and easier. (Unfortunately there is no command to explicitly instruct the tool to run in record mode.)Īs part of the FileMaker 17 release, FileMaker Inc. Running the tool in record mode would give a better chance of correcting the damaged portion of the file, but even then there’s no guarantee, because it’s not an official feature of the tool. ![]() The engineer I spoke to explained that when the tool runs in block mode, if data is corrupted, it will most likely end up getting moved into the target file as is. My incorrect understanding was based on information provided during the testing period, but that had apparently changed by the time the 17 platform was released.ĭepending on several factors, the tool will run in either block mode (fast) or record mode (slow). After talking to a FileMaker engineer about the Data Migration Tool, I learned that using the tool to recover from a damaged file is not a supported use case like I had previously thought. 9/11/18 update: I need to recant the information that was provided in this blog post based on what I learned at this year’s DevCon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |