I've been working for the last 6 years in Rekordbox with an External HDD as the main host of my database, and all my more than 3000 archives are stored in the external drive, when I open Rekordbox it only open with the external drive connected, cause if not, the program reset to default "zero" local database. But I recently updated to 6.7.0 version, and Rekordbox just don't recognize my external drive and open in the default local database that is empty of course.
I've tried to move to my external database in my drive and just doesn't work, the program overwrite the "new" empty database on the old files, and just cannot recover them.
I've tried to rename the master.backup.db to master.db in the external drive in order the open the last database, but it doesn't work.
I've tried to recover vía C:\user\AppData\Roaming\pioneer\rekordbox where I know there're other master databse files, but of course it doesn't work cause is external.
There is another place that the old master database file could be stored in order to replace it by the empy new database? I'll eternally grateful to you.
Post is closed for comments.
As your database is on the external, the path is PIONEER\Master
rekordbox shouldn't ever remove the database, if anything it defaulted to the internal because there was a problem reading the drive or the path (drive letter) changed. Check under the Preferences > Advanced to see if the external drive is available to open the database.
The files are available in the external drive, as you can see in the picture attached. But, these files are the overwritted version without the last full master database library, as the files has the same name. When I re-open the rekordbox program it's opened loading the external database, but now empty.
As you can see in the imagen, the archives are modified from yesterday, 27-March-2023, but the last fulfilled version of my library is from 18-March-2023.
You opened / closed and it several times between 5:31 and 5:47, it overwrote the previous backups:
If you have a backup from prior to that, I'd suggest restoring that version.
