MikroTik has once AGAIN managed to break script compatibility by prohibiting something as common as spaces(!) in file names. I have zero understanding of this as it affects our current solutions for version control and backup which now must be modified and tested on all nodes before we can even consider upgrading to v7.15. Why ever repeat the exact same mistake as with the date format fiasco!?
This is yet another piece of evidence that one should try (even if it’s remotely possible) to avoid RoS scripting in production at all costs as Mikrotik might break compatibility without notice at any time.
Since this isn’t the first time (and probably not the last) that Mikrotik breaks script compatibility, I think it’s more than fair that Mikrotik includes a clear warning about this on the help page regarding scripting. Besides, spaces in file names have no significant effect that would justify this change otherwise we’d have seen a lot of complaints about this already.
Bottom line - one might wonder if R&D practices any QA sign-off at all. Sorry for my French, but this is completely bonkers!
Ref: http://forum.mikrotik.com/t/v7-15beta-broke-backup-file-naming/174404/1