How do you make backup mikrotik device configurations and compare versions?

Have a look at https://unimus.net/

Have a look at https://unimus.net/

No thanks. Only interested in local solutions.

If you want to export configuration in the human redable form then use CLI

/export file=putthenamehere

You can then compare versions when you transfer it locally.

If you want to export configuration in the human redable form then use CLI

/export file=putthenamehere

You can then compare versions when you transfer it locally.

you propose to do it manually for 500 devices ?
export file - will kill your hdd !

Have you mentioned number 500 anywhere or should I be a fairy to know it? But there is no other way if you want to compare running configuration to previous/original/standard one.

It was just an idea for you ... you can also make a script on some Linux server which connects to your devices vith ssh, executes script which exports configuration, downloads it and then saves and compares locally.

Have a look at https://unimus.net/

No thanks. Only interested in local solutions.

Unimus is not a cloud software, you run it locally on your servers.

Have a look at https://unimus.net/

No thanks. Only interested in local solutions.

Unimus is not a cloud software, you run it locally on your servers.

Unless you stick it in the cloud But yes, @op - best solution for an automated backup and change management.

Unimus is not a cloud software, you run it locally on your servers.

Unless you stick it in the cloud.

Touché

Hi folks,
what I usually do is creating the backup configuration files, downloading them to my local machine. Once this is done I'll strip the very first line containing the time stamp (this makes the files ready for the diff process in GIT, otherwise they will always change). Then I rename them so that they contain the identity (FQDN) of the MT device in your network (to make them unique) and commit them to a local GIT repository. Once this is done for the whole network (I usually use a text file with all FQDN of my MT devices) the commit is tagged and pushed to a private GIT repository.

Restore Configuration
Restoring MT configuration is done the opposite way using a version tag or commit ID. Remember to use a kind of restore text file so that units are initiated in the right order.
The whole process can be automated using a SSH key and the ssh agent. So the user has to enter the passphrase for the SSH key just once.

Collaboration
What about sharing the code in a Github repository? We could then further develop the solution so that it will be more robust and usable for more MT users?

Summary

1. Download using SCP
2. Strip the timestamp
3. Continue with the rest of the network using a text file containing all the FQDN
4. Commit to local GIT repository
5. Create a tag
6. Push the changes to a remote GIT repository

I use rancid http://www.shrubbery.net/rancid/ for config backup. At a previous employer they use it to backup 10s of thousands devices with great success.