4 Replies Latest reply on Dec 20, 2010 12:23 PM by philmodjunk

    FileMaker Server database corruption? can't copy out database

    ChrisSheehy

      Title

      FileMaker Server database corruption? can't copy out database

      Your post

      We have a FileMaker Server v10.0.2.206 running on a Vista Business Edition PC with a database that 5 clients connect to on a daily basis. Last night the database became inaccessible so the server was rebooted. Once the server came back online the database was available. This morning the database was again inaccessible (showing CLOSED in Admin Console.) Upon trying to Open the database from Admin Console it would go to Verifying then back to Closed state. The database is around 250MB.

      We have a backup scheme that uses Volume Shadow Copy in place to copy out the database every night as long as the time stamp is different. Well when we checked the backups, there has not been a backup in 12 days. the only error in the backup log is this morning. The backup reported a CRC error when trying to copy out the file. When I try to manually copy the file out it bombs at around 75%. I can rename the file and all the other files on the server are fine.

      How can the database NOT get a different timestamp if it has been worked in daily for the last 12 days? I know the backup is working fine since there are other files in the scheme that have been picked up.

      The database file is fragmented into 6 pieces and I attempted a defrag but that failed as well.

      Is there hope for repairing this file or getting the data out of it? Is there anything we can do to prevent this from happening in the future?

      Any help greatly appreciated,

      Chris

       

       

       

        • 1. Re: FileMaker Server database corruption? can't copy out database

          Chris Sheeny:

          Thanks for posting!

          Was the Volume Shadow Copy backing up the live databases? If so, this could be the cause of your corruption. If you need to backup the databases with a third party method, we recommend scheduling a FileMaker Server back up and then using the third party method to back up the resulting back ups when it's finished. As a general rule, nothing besides FileMaker Server should be touching live databases.

          I, unfortunately, don't have any recommendations for getting the database out of there if the copy's failing. If you do find a way to move it somewhere else, or if you're willing to try some of these steps directly on the server, I highly recommend taking a look at Knowledge Base Answer #5421:

          http://help.filemaker.com/app/answers/detail/a_id/5421

          TSBear

          FileMaker, Inc.

          • 2. Re: FileMaker Server database corruption? can't copy out database
            ChrisSheehy

            TSBear,

            The recovery process was successful with a handful of errors (all of them are ERROR: Page xxxxx could not be loaded; invalid header or file error (4294967295).) We will test the recovered database tomorrow.

            We did have a third party app backing up the live database. I have enabled the built-in backup schedule and switched the third party app to backup the BACKUP directory.

            Thanks for the information and help. This will get us in the right direction.

             

            • 3. Re: FileMaker Server database corruption? can't copy out database
              ChrisSheehy

              The database appears to be okay. However, we are concerned about the errors generated in the recover.log file. Here is the error portion of the log file: Can we move forward with the database in this state? Will there be missing data?

              2010-12-17 18:55:56.531 -0500 OLDBook_Menu.fp7 0 *** Started recovery of 'OLDBook_Menu.fp7'
              2010-12-17 18:55:56.625 -0500 OLDBook_Menu.fp7 0 Scanning blocks and rebuilding file...
              2010-12-17 18:56:49.375 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45912 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:57:05.968 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45913 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:57:45.781 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45914 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:58:03.375 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45915 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:58:19.968 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45916 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:58:37.390 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45917 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:58:55.015 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45918 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:59:12.328 -0500 OLDBook_Menu.fp7 0 ERROR: Page 45919 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 18:59:52.890 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55562 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:00:56.828 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55563 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:01:29.531 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55564 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:01:29.687 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55565 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:02:26.171 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55566 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:02:58.640 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55567 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:04:04.750 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55568 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:04:05.406 -0500 OLDBook_Menu.fp7 0 ERROR: Page 55569 could not be loaded; invalid header or file error (4294967295)
              2010-12-17 19:04:08.968 -0500 OLDBook_Menu.fp7 0 Scan complete, found 56849 page(s) to process
              2010-12-17 19:05:06.281 -0500 OLDBook_Menu.fp7 0 Rebuild processed 56849 page(s), completing end of file
              2010-12-17 19:05:32.890 -0500 OLDBook_Menu.fp7 0 Completed copy or rebuild of file blocks

              • 4. Re: FileMaker Server database corruption? can't copy out database
                philmodjunk

                Best practice is to never use a recovered file, but to replace it with an undamaged back up. This is one of the main reasons for making and saving a large number of backup copies of your file. Recover works well for the most part, but you never know for sure if it fully and correctly fixed all the issues.

                If you can find an undamaged copy, you can save a clone of it, then import all the data from your recovered file, resetting serial number fields' next serial value settings as needed. This process can be scripted so that you can set this up to run unattended, importing data from all tables and updating all serial number fields, while you do other things.

                If you can't find such a copy, you'll have to decide whether to rebuild your file from scratch or use the file and hope everything is correct. (You might also investigate third party utilities such as FMDiff.)