ChrisVanBuren

Corruption - Is Recovered File Safe to Use

Discussion created by ChrisVanBuren on Jan 14, 2012
Latest reply on Feb 8, 2012 by ChrisVanBuren

Hi All,


 

Thanks in advance for any help that can be offered. Here’s the situation:

 

 

-I have a perfectly good FileMaker file which is under constant development always hosted by FileMaker Server. I believe this file has never been crashed.

-I was going to use this file as the basis of a new template for myself. Because of this I tested this file with Recover.

-The file failed Recover even though the file works perfectly.

-My last good backup without the corruption is Nov 2, 2011. There has been many days of development since then.

-Recover says that I should NOT use the file going forward.

-Recover log report:

 

8496  Balanced out begin and end folder markers

 

 

-Clone fails recover with the same issue.

-Compacted copy fails recover with the same issue

-Deleting all scripts gives an error message “This script cannot be found or has been deleted” There is a folder called “Common” which also remains (cannot be deleted) so I believe the problem is either a phantom script inside Common or a problem with Common itself.

-The recovered file seems to work fine.

-The recovered file can be recovered itself with no problem.

-All scripts can be deleted from the recovered file (so problem appears to be fixed by recover).

 

 

 

 

FMDiff Check

Running check described at http://fmdiff.com/fm/filecorruption.html yields:

 

 

Test 1 - vs compacted copy

 

 

Errors (indicates some kind of damage)

 

No apparent errors detected.

Block 41 orphaned.

Warnings

 

First data block is not block 2.

No apparent errors detected.

 

 

 

 

 

 

 

 

 

Test 2 - vs recovered file

 

 

Errors (indicates some kind of damage)

 

No apparent errors detected.

Block 41 orphaned.

Warnings

 

File was recovered 1 times on Mac OS (Intel).

No apparent errors detected.

Overview

[–] Deleted

[~] Modified

[+] Added

Base Tables

 

1

Scripts

 

1

Graphics

 

1

 

Base Table ^

New: Cliverly.20120113.0 Recovered.fp7

Old: Cliverly.20120113.0.fp7

[+] 32798

Recovered Library

--

 

Table Occurrences ^

New: Cliverly.20120113.0 Recovered.fp7

Old: Cliverly.20120113.0.fp7

[+] 13631615

Recovered Library

--

Fields ^

New: Cliverly.20120113.0 Recovered.fp7

Old: Cliverly.20120113.0.fp7

[+] 1

Recovered Blob

--

[+] 2

From Table

--

Scripts ^

New: Cliverly.20120113.0 Recovered.fp7

Old: Cliverly.20120113.0.fp7

[+] 33011

--

--

Graphics ^

New: Cliverly.20120113.0 Recovered.fp7

Old: Cliverly.20120113.0.fp7

[~] 15

--

--

 

[4 bytes]

[4 bytes]

modificationId

45

44

 

 

 

Based on what Winfried Huslick (at http://fmdiff.com/fm/filecorruption.html) says I guess those are actually passes.

 

 

 

 

QUESTION

 

Can I just use the recovered file? The FM UI on recover says no but the log file says “Balanced out begin and end folder markers” which says there was a minor problem and recover fixed it for me. So my guess is that I the recovered file is safe to use. Love to have other opinions.

 

 

 

Lessons

 

-You cannot trust any FileMaker file to be free of corruption. You must check every FileMaker file for corruption after every x hours of development. The value of x depends on how careful you want to be.

 

-A simple check with Recover is a good idea but I full check with FMDiff would appear to be a better bet (http://fmdiff.com/fm/filecorruption.html). Again it depends on how careful you want to be.


 

Argh. I hate corruption but I let it bite me and I did know better. When’s the last time you checked your working perfectly files for corruption?

 

 

Cheers,

 

 

Chris Van Buren

---------------------------------------------------------

e: chris@zeropointdata.com

t: +44 (0)1291 689966

www.zeropointdata.com

 

Abbey Lodge, Tintern, CHEPSTOW, NP16 6SF, UK

---------------------------------------------------------

Outcomes