Is the new dude able to pull backups or export the configs from mikrotiks that it can log into?
No.
Well not to pull but u can send from some device in network to mikrotik device that Dude is installed or some external ftp server
Create Scheduler in mikrotik device
Something like that
/system backup save name=test
/tool fetch address=(Dude Ip) src-path=test.backup mode=ftp user=(dude usr.) password=(dude pass.) dst-path=test.backup upload=yes
same goes for config
if u want to export lets say wireless access-list and sent it to Dude server
/interface wireless access-list export file=test
/tool fetch address=(Dude Ip) src-path=test.rcs mode=ftp user=(dude usr.) password=(dude pass.) dst-path=test.rcs upload=yes
Also add interval about 3 days or more
We have some ideas for automatic backup system for monitored ROS devices, but it will be some time before anything like that is actually implemented in The Dude.
That would be great not only to have the encrypted backups but the clear text exports from monitored devices in the dude also.
We have begun using Oxidize. It pulls the backups, its free, and gives us revisions.
It would be a really nice feature that if a device was added to the dude it automatically pulls a backup.
So we’re about a year and a half later. Any news/progress on this?
This is the primary feature we want for deploying The Dude and for increasing our dependency on M’tik routers for clients.
Thanks.
Looks like there is no development of dude again…
should be ashamed of
You know that how? Was it announced or is there gits/svns to follow?
It’s a shame. Maybe time to really look elsewhere? It’s a [potentially] pretty good product, not just for Mikrotiks, though of course the integration is a big plus. I liked it for all sorts of snmp devices/monitoring and was stoked it was making a comeback. Just hard to commit to it (again) if dev is going to always be a stop/start rollercoaster.
I looked at oxidize. I so despise Ruby it’s a non-starter. Every Ruby project I’ve ever tried deploying was either a disaster from the start or worked great, then less great then eventually got to the point where it needed to be nuked and redone. Usually because upgrades/updates.
I suppose my lack of knowledge of Ruby/Rails doesn’t help but really I shouldn’t have to be a dev to administer software. I don’t know much about writing C, C++, Perl or Pascal but I manage to admin Windows and Linux machines pretty well.
Unimus is interesting, even though it IS paid (thanks Hammy). The dev is pretty responsive and he’s including [starting to anyway] mechanisms for pushing commands/scripts to devices which is making it somewhat of a change-mgmt platform with some interesting possibilities. This would have been helpful to us, for example, in the 6.42.1 patch rush as we updated some users from 6.40 branch and got bitten by the removal of the master/slave ports (some routers automagically added a bridge and added the ports to it, most did NOT.) Pushing a fix script to all at once would have been quite welcomed. It’s also not m’tik specific so we can use it for our other gear (Ruckus, Cisco and some UniFi and older pfSense.) I asked dev if he could add Ruckus Unleashed any time soon and he asked if I had access to some lab units for him. A couple days later it’s released in beta. Pretty good in my book.
The backups it does for m’tiks are basically full export text backups and they are compared and only kept when there’s a change which I like (because my routers may not change configs for many many months or more and frankly, who needs to keep 12-24 months of backups around in hopes they’ll have the last 1 or 2 iterations like we do now)
On the roadmap [supposedly soon] is ftp/scp file push/pull which should make it possible to do things like pulling blob backups from 'tiks and combined w/ the scripting pulling exp comps (which are useful to us for migration/upgrade across router models.) I’m expecting to be able to push these backups to a server share which will then get rolled in with our regular backups rotation which would actually be a huge win for us.
All in it’s an interesting platform and for us worth the little bit of scratch. Mikrotik should take note.
Frankly if this guy can command $4.50 a year per seat, m’tik could have pushed a similar price model and put a dedicated dev on it. Hell even for $2/yr per seat, at m’tik’s volume that should produce at least ONE full time dev’s salary and kept everyone happy and under the Mikrotik umbrella.
Oh well.
I know that because I read the changelogs. And because I use the dude for years…
A link might have been helpful since none of the changelogs I found mention stopping development.
I did find a forum thread where Normis says that the dude is stable and so I suppose that implies there’s no further dev but nothing stating that. So again a link to the info you know would be handy.
In any case, it’s a shame if they pigeonhole this platform again. A lot of potential with a lot of missed opportunity imho.
There is no such statement I can point at. Just like the history repeats… We already saw a development gap of dude and it happens again. There are many requests and bug reports that lies untouched for a long time. Don’t expect that mikrotik will confirm the actual state.
I have bugs open against The Dude and the last reply I had said this:
“We have stored all your provided information, and will take a look at it when the active Dude development will renew!”
Dude certainly isn’t stable.
Just wanted to say thanks for the kind words 
and you are not ashamed at the sight of this?
I don’t see Ubiquiti’s UNMS being overly successful at backing up my Foundry, Cisco or IgniteNet switches, my Mikrotik routers, my Calix DSLAMs, etc.
Ubiquiti ADD will kick in eventually and the product will die.
bla bla bla … the question was asked the vendor! but not about this https://unimus.net/ semi-finished product!
The question was asked of whom? Please be specific.
Semi-finished in what way? Hopefully, everything I use is semi-finished. Not being semi-finished means they’ve stopped improving the product.