backup,critical error creating backup file, ROS 6.42.1

RouterOS General
21

Thank you very much, /ip ssh regenerate-host-key solved my problem also on 6.42.1 RB493AH

22

Fixed it for my RB1100AHx2 as well. A shame for Mikrotik who suggested to NetInstall the device.

Thank you!

23

Note that this is the better advice because export is human readable and compatible between services (minor changes required) and backup is sometimes not, even between same models.

However, since export lacks certificates and users, perhaps both regular export and backup is the best solution for disaster recovery.

24

Well, it’s not compatible between devices of the same model as MAC addresses are exported as well.

25

Thanks so much.
This cleared the problem for my 751G-2HnD running 6.42.3.
Regenerating the host key without rebooting seemed to be enough for backup to run without an error message.

26

thanks

solved error :

error creating backup file: could not read all configuration files

on RB951G RouterOS 6.42.9

27

I’m running 6.43.4 with the same issue. I ran the suggested script and it worked great!
/ip ssh regenerate-host-key
/system reboot
Many thanks!!!

28

The same issue here after upgrade from RouterOS 6.43.1 to 6.43.7.
Advice from post #16 solved the issue. Kudos for that!

Can anyone explain the root cause of the problem?
It seams that the backup command is not able to read the SSH authentication keys (private + public key pair) to include them in the backup file.
And regenerating the SSH keys solves the problem.

– rpr.

29

I had the same issue after update from 6.42.9 to 6.42.12.
Regenerating ssh fixed it. Thanks guys !

30

Same here with latest 6.44.3 on x86 RouterOS.

Regenerating the SSH keys solved the issue (and reboot wasn’t necessary).

Thanks!

31

awesome, this also worked for me on a few RBs that were having this exact same issue (ros 6.45.x and 6.46.x ). I acutally didnt even need to reboot after doing the ssh key regen command.
thanks!

32

I have an RB1100AHx2 running 6.48.1 receiving the same error. This fixed it. I don’t understand why MikroTik hasn’t fixed it, it’s been around for years.

33

Antient bug…i resolved it with provided ssh regenerate command. ROS v6.49.2 on multiple boards.