Search for content in message boards

Corrupted data migrating backwards into backup files?

Corrupted data migrating backwards into backup files?

Posted: 7 Feb 2013 8:25PM GMT
Classification: Query
This is a weird set of circumstances, and I am hoping there is some help here on this.

For the record, I am on Windows 8, running FTM 2012 (newest updated version).

Last night while my laptop three up a "blue screen of death" while I was working on a census citation for an individual in my file. I had other programs open so I am not convinced it was FTM that caused this, but who knows.

After rebooting, and doing a few other things, I go back into FTM. I'm working on the same individual, but I notice that the place location has changed on its own. Instead of being "Boone, Indiana, USA" it is now "Marlborough, Middlesex, Massachusetts, USA". And this is for all of the place locations on his record -- not just that one fact. If I go into the place locations and go to Marlborough, he does not show up in that list. But, also Boone does not show up under Indiana. While I do not have many people in Boone, Indiana, there should have been a few entries there.

I had a similiar case of data corruption in December (this time with locales in Wisconsin). At that time I restored from a backup and all was fine. So, I decided to restore from the backup from the morning. Set that to run and went to bed (it takes too long to process since my tree is synced to the online tree and it was late). When I got up int he morning to go to work I checked in on the program. It was done, and I looked in on my person. The location was still messed up!

This is weird. The backup from the morning should have had the correct place name. I know this, becuase it was there before the crash. Also, I had synced online files before the backup that morning -- and if you look at my online tree the place location is correct there.

I am currently trying to restore from the backup file one older than I had done -- to see if the problem remains. If it does, what are my options? While I know the data in my online tree is good I am afraid that in syncing the "wrong" place data will be kept. I also do not want to just download the family file from onine -- the online file does not have all the Notes and research notes on people. (Or at least not that I can see).

Is the place name part of the software itself? It occured to me that I might have to reinstall FTM in order to clear up this faulty place location.

Does anyone have any ideas?

Re: Corrupted data migrating backwards into backup files?

Posted: 7 Feb 2013 10:50PM GMT
Classification: Query
Have you done a resolve place names on the affected records?

FTM (the program) has an internal Place Name Authority of about 3.5 million places. This has nothing to do with Bing maps but is used when you resolve place names and the new places hierarchy functionality

Have you compacted your file?


I once lost an FTM file once because of a power glitch that so severely corrupted the file I could not fix it. I had good back ups.

I then purchased a Uninterruptible Power Supply (UPS) to protect my computer and modem


I would suggest that you focus on getting your FTM data correct before you contemplate syncing


John D

Re: Corrupted data migrating backwards into backup files?

Posted: 7 Feb 2013 11:16PM GMT
Classification: Query
Out of order to your points, but:

1. I always compact after doing a full backup. And I try to do a full backup daily. Having been through too many database rebuilds from data loss I am a bit paranoid that way.

2. I have way too many places that FTM will not recognize (old locations no longer around), and so I do place name resolves as I find them as it were. (My database is 29K people). Syncing is part of my "backup systems" as it were, since I know that I have at least a chance at partial data recovery from a fully synced file online.

3. Both places were resolved. I was worried since Boone was not showing up as an option under the place hierarchy at all (places will show up as greyed out in the hierarchy if they exist and you do not use them). However .... (see 4 below)

4. I went into the "corrupted" file and changed the location to Boone County. At first it did not recognize it and I resolved it. Now it shows up properly in the place name hierarchy. It might not have been corrupted so much as confused, although how FTM lost a place name and overwrote it I do not understand at all.

Looks like I can manually change all the places for that couple back to what they should have been -- I just hope it was only that county that got messed up. I really have too many people to check everyone.


Then later on I should look into if I have some bad sectors on this disk (that caused said blue screen of death).

Re: Corrupted data migrating backwards into backup files?

Posted: 7 Feb 2013 11:28PM GMT
Classification: Query
I agree that compacting your file may fix the place issues.

I had one a few weeks ago - my grandmother was born in Massachusetts, but the baptismal record was showing up as "Louisiana." It took a couple of compacts, but eventually FTM realized that Boston, Suffolk County HAD to be in Massachusetts rather than in Louisiana.

Re: Corrupted data migrating backwards into backup files?

Posted: 7 Feb 2013 11:38PM GMT
Classification: Query
I think what may have happened is that your file "lost" some of the internal pointers which are part of FTM's relational database.

You seemed to have confirmed this when you report you can manually correct them (reset the pointers).

After you have done this, I would again suggest compacting as one of the main (unpublished) things compacting does, is forces the database to be re-indexed and this resets the internal data pointers. Bit like strightening bent street signs so they point down the right street :-)

The database used in FTM 2008 and above is relational not flat field like it was in FTM 16 and earlier and seems to be far more robust, but things can still go wrong.

I would also be investigationg why your computer crashed in the first place and of course have good backups

John D

Re: Corrupted data migrating backwards into backup files?

Posted: 8 Feb 2013 1:04AM GMT
Classification: Query
John D said: -

I would also be investigationg why your computer crashed in the first place and of course have good backups

That is a VERY good point that John has mentioned. Usually a Blue Screen of Death is HARDWARE related. NOT software.

Jon C


Re: Corrupted data migrating backwards into backup files?

Posted: 8 Feb 2013 10:31AM GMT
Classification: Query
The only times I have gotten the dreaded blue screen on this laptop (3 or 4 I think) FTM has been open and running. Granted, I use that program A LOT, but it makes me think there is a bad file sector somewhere and FTM is intersecting or accessing that sector. This weekend I plan on doing some "repair" work to see if that helps.

Elizabeth

Re: Corrupted data migrating backwards into backup files?

Posted: 8 Feb 2013 2:10PM GMT
Classification: Query
Elizabeth -

Note that you can also get the BSOD from something as simple as an outdated monitor driver. I was having a series of those and solved it by checking for and downloading the latest driver. Check the screen when this happens for an error code or more info. Google BSOD to get a list of the error codes and more info on causes.

Virginia
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | New Privacy | New Terms and Conditions