I’m exporting my existing dude database and trying to import it into a CHR.
I’m copying the file over as backup.tgz
/dude import-db backup-file=backup.tgz
It imports, then seems to bail out at 99% and my dude client gets an ‘Error: Connect failed: 10061:No connection could be made becaus…’
/dude print either gives a blank status, or:
enabled: yes
data-directory: dude2
status: applying settings: enabling: reading db object #176
Checked with v4.0b3 and v6.34rcXX backups both are imported without issues on CHR dude server.
Try generating backup on original dude server again, possibly this on is corrupted.
I’ve done this 3 times now. Full export of the tgz backup, then import-db the file. Same thing.
Please try importing it one last time in v6.34rc45 and if it fails then generate supout file after this attempt and sent it to support@mikrotik.com we will check why db does not want to load.
ok, dude 4b3 on Windows. Export file backup-2016.01.27.tgz
copy to files on 6.34rc45
on 6.34rc45
/dude set enable=no
remove dude directory
/dude set enable=yes
/dude import-db backup-file=backup-2016.01.27.tgz
status: importing: 45% complete
status:importing database object …
/dude print now shows either blank status, or ‘applying settings …’
dude client gets 10061 error
support file sent
just for fun, I stopped the dude on the windows box and vacuumed the database (sqlite3.exe dude.db “VACUUM;”)
this shrank the db file from 111MB to 90MB.
relaunched the dude, exported, transferred, imported, same results.
I’ve tried 6.34, 6.34.1, and 6.35rc4.
Now, it’s starting to import, but getting hung up on
status: applying settings: enabling: reading db object #174
or
status: applying settings: enabling: reading db object #175
CPU 100%.
At least it stays ‘connected’ to the import-db run now, but never seems to complete.
FYI, fresh export file just moments before, and importing using ‘/dude import-db backup-file=bu.tgz’
Same problem here, got to 99 % then it perpetually prints applying settings: enabling: reading db object. The number will change and sometimes cycle back to an old one but thats about it.
Edit:
The dude is running underneath though, if you torch the interface you can see traffic going to your devices. You just can’t connect to the dude.
Went 24 hours at 100% CPU on 6.35rc4, trying again on 6.35rc5…not hopeful because it’s already sitting on “status: applying settings: enabling: reading db object #174”
yeah, about 20 minutes in, same thing…
I’ve done this, no response…
This is about the only thing holding me up…
Im importing a dude database from v4b3 to the latest release candidate. it failed the first two times @ 99% with “action timed out” on the third attempt it worked.
I’m about 6x in and haven’t gotten one to complete yet.
@krisjanis, any ideas here?
Some of backup files that you guys sent in are still with DEV for checking, unfortunately no news yet.
thanks.
Any progress in fixing this problem ? We migrated from the old Dude to 6.34.3 and we can’t import the data.
You have migrated too early. Just stay with 4b3 for some time more…
Found a workaround… Startet up my old Dude server… Just selected all items on my MAP and CTRL+C
Switched to my New Dude server and opened the map and CTRL+V.
Does not copy every setting and such but beter then making the whole thing from scratch… 
But i cant even upload files to the new server.. so something is seriously wrong with the software… 