View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020721 | MMW 5 | Install/Config | public | 2024-03-14 20:52 | 2024-03-21 18:52 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | feature | Reproducibility | always |
Status | feedback | Resolution | open | ||
Product Version | 5.1 | ||||
Target Version | 5.1.1 | Fixed in Version | 5.1 | ||
Summary | 0020721: Improved data/settings migration facility | ||||
Description | When users upgrade from earlier versions of MediaMonkey for Windows: a) Although there is a facility to import the DB/settings from older installations on the PC, it's not always obvious which settings the user should be importing. b) When users migrate from one PC to another, although it's possible to Backup the DB, other aspects of the installation aren't backed up (mediamonkey.ini, persistent.json, registry settings, scripts), which makes it complicated to replicate the setup from the previous PC c) When users migrate from one PC to another and restore the DB, users must manually remap the drive and/or find moved/missing files To alleviate all of these issues, the following improvements are suggested (based on discussions with Ludek/LL): 1) Modify the first-run settings import dialog as suggested at ~c74593 : Do you want to use the database and settings from an existing installation of MediaMonkey? Version found - Last updated ( ) MediaMonkey 4 - 2019-02-05 ( ) MediaMonkey 5 - 2023-12-24 (o) MediaMonkey 2024 - 2024-02-29 [Import selected] [Select Folder] [Cancel] 2) Modify the backup functionality to also allow settings to be backed up. e.g. This will create a backup of the current database... Backup [x] Database [ ] Settings [ ] Addons Do you want to proceed? 3) If users do a clean install and recover data from an existing database (at step 1) above), and MediaMonkey detects that the new drive letters/paths do not match previous drive letters/paths then facilitate fixing this automatically. e.g.: a) Media Properties MediaMonkey has detected that your database points to drives that do not exist on this PC. Would you like to remap the drive(s)? . . . . . . . . Type . . . Serial . . . . . . Label . . . Location Old . . . . . Fixed . . . 76B7-6923 . Music . . . D:\ [ ] Suggested: Fixed . . . 58D9-6579 . Music . . . F:\ Old . . . . . Fixed . . . 76B7-6923 . Music . . . D:\ [ ] Suggested: Fixed . . . 58D9-6579 . Music . . . F:\ [OK] [Cancel] b) Then automatically select all tracks with broken links and show a dialog along the following lines: Locate moved/missing files x files in the database cannot be found in their expected locations. Search the selected locations: | ||||
Additional Information | Note: items 1) and 2) can be implemented without any new strings. | ||||
Tags | No tags attached. | ||||
Fixed in build | 3007 | ||||
|
2) a) Settings should include items included in ini, persistent.json and registry. However care needs to be taken with settings that can be PC/install specific, including Path settings, Monitor settings, IP (network), and Windows version settings as users may restore the backup on a different system. Also consider the ability to backup and restore between Windows and MAC. One option would be that import verifies settings on import to make sure they're valid on the importing install (and skip settings that aren't). b) Addons, one option would be a system where Addons installed would be used on the new install to download and install from Addons site. Some apps use this. It should have a system where Addon developers can include Addon settings/files in backup to be restored after Addons have been installed on new PC. c) Backups should work between regular and portable installs either direction. 3) We may want to consider users that migrate system and merge files from multiple drives onto the same drive (for example, old system C and D drive are now both on M drive on new system). |
|
NOTE 2): in 0016176 it was already suggested to ZIP DB Files to conserve HDD spaceas some users have 2GB+ library file and plain ZIP compress it to 1/10 of full MM5.DB size. |
|
2) The restore/backup facility has been enhanced to include Settings and Addons (optionally) in build 3007 |