Dude v4.0beta02 export dies

Having a problem doing backups on v4.0beta02

Trying to export the config before upgrading to v4.0beta03 however I:

Click export button
watch it display “Exporting”
watch it display “Downloading export file…”
Client rate sits at about 400~kbps for about 5-10 seconds then Dude disconnects and logs back in again without completing the file.

Anything I can disable in my maps or remove that’ll allow me to get the backup?
Alternatively any way to fire up a new dude server and copy devices across from one to the other?

Dude is running on a RouterOS machine so no chance of copying the folders before upgrading unfortunately.

Reduce your raw keep time and wait a few days for data to be averaged away. Delete log files.

Can you tell me how long it takes before it gives up? My export is about 500 MB, takes about 4 or 5 minutes but does complete.

Approx storage value reads only 44kb (there’s not much stored on this server, just used for basic monitoring but has about 200 devices setup).

Logs are at 22 and 300kb respectively, I expect the output size won’t be over 100Mb at the moment but it only goes for about 5 seconds while displaying “downloading” and then dude disconnects.

I am running w2k sp3. Maybe different setup?

Yeah lol, as above - running directly on RouterOS. No way to backup the files properly.
I guess I’m stuck now.

Wow that sucks :frowning:

I have EXACTLY the same symptoms with dude 4.0 beta1, beta2, beta3 on RouterOS even on clean database.
Tried fresh install on RouterOS 4.x and 5.0 running in Virtual machine in RouterOS KVM.

I cannot export immediately after installation (empty database) and with 1 dummy object added. When I push export - export file is prepared and I get disconnected during file download.
System has 512M of ram (492M free) and 512M of disk space (446M free so it is not a ram/hdd space problem.

Debug log shows that right after disconnect dude seems to be re-initialized:

12:30:39 store,debug adding system drive: primary-master (/dev/hda) 
12:30:39 store,debug dude1: disk setup finished successfully 
12:30:39 store,debug web-proxy1: disk setup finished successfully 
12:30:39 store,debug activating store for dude1 
12:30:39 store,debug dude1: activation finished successfully

Looks like attempt to export data just crashes dude instance.

Export is OK if I install dude on master host, not in VM.

Any comments from MiktoTik?

I am in the same situation. This really sucks because I have several years worth of data that is at risk of being lost now. Is there any possible way to copy the dude data manually? I was tempted to go back to 3 but I don’t want to loose the last 2 or 3 months of data.

Took the plunge and upgraded to v4.0beta3 but still have the same issue (2 seperate boxes running the Dude on top of RouterOS) >_<

I’m using Dude v4.0beta3 and have the same experience.

I am on the same ethernet segment, same logical subnet and click export. It says “Exporting…” in the lower left corner. Once it is done with that it briefly says “Downloading export file…” and then crashes.

Every once in a while it will actually work. I just got a 73MB file downloaded from a host on the same physical and logical network.

Arghhh.

Attempted to do a backup from v4.0beta3 tonight, backup completes, starts transferring to my machine and stops.
Dude disconnects and tries to reconnect, gives invalid username and password error.

Fearing the worst I try to connect with the default details and sure enough, blank config. :frowning:

I have the same problem ( bag ) , that is describe in the first post, but it still not solved :frowning:

Same problem here, get disconnect and cant get my backup-data. Really need solution.

Handful of people have the exact same claim. Could we get some update on this, Mikrotik?

+1 here with Dude 3.6 running on RB600 (ROS 3.30). I try to export data, 5 seconds later it disconnects.

sorted by deleting large files from the Files window and truncating the logs to a minimum.

No solution to this yet?

No solution, personally we ended up moving to hosting the service on a Windows box where we could backup the entire directory itself.

That said, so long as only keep a few router-os version on there and make sure we’re not keeping 100~s of MB worth of logfiles, the backup process is now quite quick and the export quite small, under 100MB for a network of over 2300 devices at present. Haven’t had it crash on the windows box yet.

i got a backup file downloaded with the web interface on dude running on routeros. its corrupt, but it gave me some file. i wonder if there is a workaround using website url to download backup.