Related

Basecamp Alldata.gdb and Alldata.bak files Overwritten, database gone?

5931737

When launching BaseCamp v4.7.5, an error stating something about a list file popped up and I clicked "Attempt to Repair." I didn't write down exactly what the error said, and I cannot reproduce it.

BaseCamp booted up normally, however my entire database is gone. No waypoints, tracks, or routes from 8+ years of adventuring are present. 

The AppData\roaming\Garmin\BaseCamp\Database\4.7 directory shows AllData.gdb and AllData.bak as 2KB files.

My assumption is that BaseCamp overwrote the existing database files and simply deleted the old ones.

Is there any way to get the previous database back? I do not have a manual backup besides the little data on my GPS because I blindly trusted that Garmin would have redundancy for this and would not just overwrite all previous data without saving the corrupted file separately. 

  • 0

    Any data file should be backed up, regardless of whether it's BaseCamp, Word, Excel etc ... if you have some sort of routine back up set you may find it there. However BaseCamp also can work with numerous  AllData.gdb files, it may simply be that you've set it to look at the wrong one. Do a search for AllData.gdb files and see if you have any others. Point BaseCamp at any you find and see if your data is there.

  • 0

      is right.  Don't rely on the software to backup your data.  It is common for software to contain a routine that tries to repair a corrupted database, but if it is irreparable, a new one is created.  IMHO, Garmin went the extra mile in Basecamp by providing backup and restore functions.  I truly hope your situation is simply a case of Basecamp looking at the wrong .gbd file.  Please consider creating a backup routine for all data on your PC because it is all susceptible to loss.

  • 0

    Ive just had the same problem, Basecamp has crashed and ive lost the AllData.gdb file.  This isnt good enough ive got a a long day ahead to rebuild the database.  
    Basecamp needs a pretty thorough rebuild.

  • 0 in reply to Kearly

    Basecamp version 4.7.5 was released on March 27, 2023 and I think this release surprised a lot of people because Basecamp was thought to be already of out development.  I will be a big surprise if that produce another version of Basecamp.  AFAIK, the current route creation tool produced by Garmin is a phone app named Tread.  I know absolutely nothing about it, but I can not see myself ever trying to create multi-hundred mile routes along secondary roads, to share with a other riders, using an app on my phone.

  • 0 in reply to Kearly

    BaseCamp crashing or even being uninstalled doesn't delete your database. Something else must have happened. I assume you've done a search for AllData.* on your PC?  That should find AllData.gdb and AllData.bak

    If it doesn't whatever happened isn't caused by BaseCamp, but in future ensure you back up AllData.gdb yourself just like you should do for any data on your PC.

  • 0

    Hi all, just an update. I've used Recuva and several other means to look for previous versions of AllData files, but they are well and truly gone. 

    I was under the mistaken impression that Garmin saved discrete .gpx files for each waypoint and track, since that's how my own file structure works when I make routes manually to import into Basecamp. Unfortunately it doesn't, so when it overwrote the files, they were all gone. 

    I have a small amount of data on the actual device archives, so I'm able to reconstruct some of what I lost but not all of it. I wish there was one more confirmation beyond "some data loss may occur" before Garmin absolutely nukes the database and wipes everything. 

    Live and learn, I guess! Appreciate the input from everyone, and now I know what to back up.

  • 0 in reply to 5931737

    Did you look at AV activity, perhaps its quarantine location?  I don't see any reason for a AV product to quarantine the AllData files but I would appreciate checking everything and everywhere we can think of in the hopes of identifying what happened.