Hi,
I'm sure this happened in a previous version.
Restoring a RB database backup defaults the music library to the C drive.
The restoration is always to the internal drive which is the default location; it does not restore to any other path. Once you have restored, you can then move it off to another drive.
Post is closed for comments.
PS: All my trax are on the M drive and auto relocate doesn't find all the files, despite there being no difference in the filename
I recently experienced the same. The filepath of the restored DB was C:\ instead of E:\.
With manual relocation it wasn't an issue. Just select all missing files and reloacte the first one and answer 'yes' to the question if rekordbox should use the location to find the other files.
In the auto relocation it some sort of scanned my iTunes DB which I didn't used to import tracks into rekordbox. I cancelled the transaction as I wasn't sure what rekordbox was doing.
I have experienced this in every version of RB6. RB5 works properly to restore to the proper location. I reported it to support and worked with them a few weeks ago to identify the issue. I have been looking for a new beta release and hoping this gets addressed. I use the Library Backup/Restore to maintain 2 systems without the dropbox cloud feature. The work around has been to run Auto Relocate after a restore to correct the file missing errors.
@Pulse
I'm 99.9% sure, that when I've restored a database in the past, the correct patch to my music files was correct, i.e. M\Tunes.
I'm also 99.9% sure that this issue did exist in a very older version and was fixed.
Cheers
Pulse,
The Restore Library function is restoring the database to the proper location and matches that of the Backup. For me this is E: drive on Windows 10. The problem is with the track locations. The Restore sets the track files location to C: on all tracks. My systems both have all the tracks on E:. I worked with one of the developers about 6 weeks ago and sent him all the information, screen shots, etc. to detail this issue. This issue does not exist in RB5. It started with the first version of RB6.
RB 6.2.0 does not fix this issue, just tested it with both system on 6.2.
FYI, I just tested a beta for a November release provided by support. The Restore Library issue of missing tracks on disk other than C: has been resolved. Look for it to be released in a few weeks.