MikroTik

Hello.

We have RB2011L with ROS 6.42.1 saying "echo: backup,critical error creating backup file: could not read all configuration files" to terminal upon creating a backup file.

How do we fix this?

Send supout to the support. Come back to us with their answer.

Send supout to the support. Come back to us with their answer.

It is said that "limited support service might be provided by e-mail for 30 days after the purchase". It's more than 30 days after the purchase. Where should I send the supout?

Support@mikrotik.com. Mikrotik receives all error reports. Does not matter if the period is over or not.

This message started appearing after upgrading to 6.42rc56 and support returned me with the following response:

Hello,

Your configuration has details which can't include in backup file. More about it you can find there:
https://wiki.mikrotik.com/wiki/Manual:C ... tem_Backup
If you have further problems then contact with us.

I couldn't identify which "detail" is causing this message !!!

.. so you should contact them again as they suggested.

I have the same problem on the same router RB2011L, v.6.42.1

Hello together,

the same issue happens to both of my KVM-based virtualised x86 installations after upgrading from 6.38.5 to the actual MikroTik RouterOS 6.42.2

best regards
Marc

Solution is Netinstall...

I couldn't identify which "detail" is causing this message !!!

You may want to investigate removing line by line from the configuration and see when backup will succeed.

I think it's good coding practice to generate detailed diagnostics output when software is not happy about some parameters built in earlier version of the same software.

In the end, Mikrotik support suggested us to export config using "/export".

And after update to 6.42.2 "backup,critical error creating backup file" error disappeared.

I am getting the same error here after upgrading a couple of old v5.26 installations to v6.42.1. Some of them do not have it but others do.

Netinstall is not a good solution, it is a disaster if you have quite a few remote installations.

PS: Sending the supout.rif

Same happens here on couple of 951G and one 2011L.

Is there any better solution than netinstall from MikroTik?

Thanks!

i updated about 200 devices (mipsbe, powerpc, tile, x86, mmips) to 6.42.1 and about 30% has problem with backup:
10:44:06 echo: backup,critical error creating backup file: could not read all configuration files

i test one device with this error (RB1000) and enable all packages, update firmware, upgrade to 6.42.2, 6.42.3, chek installation and no help with this error.
i browse support.rif in my mikrotik account and no problem visible.

Good day,

no problem on 6.41.x, problem begin with 6.42.2.
Affected devices are 1100AHx2 and 751G-2HnD, CCR without issue.

Pavel

i did backup with error "backup,critical error creating backup file" and restore box with this "error" backup.
config is without change and error dissapears...
tested only on few devices, some ok, some not

btw i tested in lab upgrade from old ros (4.10(netinstall)->5.26->6.40.8->6.42.1) with same config on same device and resultis:
2 times error backup
4 times no error
its magic, some updates ok, some updates not


today look for some solution about error "ssh,error Corrupt host's key, regenerating it! Reboot required!" on other boxes: and works
binary backup is now without error. tested on about 10 devices

ssh regenerate key works for me.
tested on 50+ problematic boxes.

Code: Select all

/ip ssh regenerate-host-key
/system reboot

and works
binary backup is now without error. tested on about 10 devices

Works for me as well. Thanks a lot!

Code: Select all

/ip ssh regenerate-host-key
/system reboot

and works
binary backup is now without error. tested on about 10 devices

Works fine. Thanks

Well discovered! Works here as well. This should be posted with upgrade notes as too!

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

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

Thank you!

In the end, Mikrotik support suggested us to export config using "/export".

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.

In the end, Mikrotik support suggested us to export config using "/export".

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.

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

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.

thanks

solved error :

error creating backup file: could not read all configuration files

on RB951G RouterOS 6.42.9

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!!!!

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.

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

Same here with latest 6.44.3 on x86 RouterOS.

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

Thanks!

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!

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.

Code: Select all

/ip ssh regenerate-host-key
/system reboot

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