Yes, you are correct. The Mikrotik Wiki has some information about this: http://wiki.mikrotik.com/wiki/Manual:Co ... escriptionThe only case in which decryption works after a restore is when the backup was done in exactly the same hardware ( as far as I could test )
Does anyone know why ?
Thanks for any help.
The restoration procedure assumes the cofiguration is restored on the same router, where the backup file was originally created, so it will create partially broken configuration if the hardware has been changed.
Again, the Mikrotik Wiki is a good resource, it covers this as well: http://wiki.mikrotik.com/wiki/Manual:Co ... figurationThanks for your answer, but my question was another: Why an export done from / fails when it is imported ( it hangs forever ) ?
Note that it is impossible to import the whole router configuration using this feature. It can only be used to import a part of configuration (for example, firewall rules) in order to spare you some typing.
Agreed, maybe I should whip something upWhen you have many routers in your network and you try to minimize incident response time as a consequence of a hardware failure, having to manually retype router configuration is not an acceptable manteinance procedure.
That's the problem I am trying to solve:The only case in which decryption works after a restore is when the backup was done in exactly the same hardware ( as far as I could test )
Yes, currently it is correct.So the conclusion is that, in an environment where you have many routers, you must provide your manteinance staff not only with the backups files but also with the cerificate/key pairs.