I updated my first RUTX11 to firmware 7.22. The first thing I always do is make a backup and compare it to the previous version to check for errors or settings drift. In the backup.XXX.tar.gz file created by 7.22, the entire /etc/config directory is missing. I didn’t see anything about this in the r…

Ok thank you. I am surprised this slipped by during testing. It’s somewhat concerning.

Also on a RUTX50, there are even more files and subdirectories of /etc missing, along with /etc/config. A few examples, when compared to a backup taken in 07.21.3 …. /etc/crontabs /etc/openvpn /etc/profiles /etc/profiles.d … and many more I hope someone has given the dev-testers a kick up the…

Greetings, @Mike , Thank you for your feedback, And thank you for sharing that there are more missing files and directories from the backup. I have forwarded this information for our R&D team as it may be useful for further investigation. I will post an update in this topic, once I have more info…

I also did a backup on a RUTX50 and compared the 7.22 version with a 7.21 version. The only difference I could find where the uhttpd cert files that moved from the /etc directory to the /etc/certificates directory. No missing directories. Before I run a backup I always run this command: api Post /…

[image] FW 7.22.0 - New Backup File JSON Question Issue With the newest FW changing the structure of the backup files to use the API endpoints for device configuration, I wanted to ask if it is possible to upload the new configuration.json file directly to…

That explained why I did not experience the problem. I do backups the “old-fashioned way”. I run an Ansible playbook using the /sbin/sysupgrade -b command. - name: Get backup file name ansible.builtin.shell: cmd: set -o pipefail && echo "${HOSTNAME}|$(/sbin/uci get system.system.device_fw_ver…

Hello everyone, I have an update regarding this matter. The change in the backup structure is intentional and reflects a transition to a universal backup system. Instead of multiple configuration directories and files, the configuration is now consolidated into a single file located at /tmp/config…

I am still skeptical of the benefit of this “universal” monolithic JSON file vs the filesystem-adjacent method used previously. The old system was very easy to store, modify, compress, compare, and validate. Now we have this huge mess of a JSON file which introduces novel ways to break the entire s…

Also the in 7.22 introduced integrity feature at /integrity/actions/validate is file based. I use it to monitor file changes in my day-to-day backups.

@rvo that’s an interesting API for sure, but it’s hash-based. I just played around with it. It detects changed files, but you can’t diff the changes or see what they were. I had built up some tooling that relied on having access to the actual config file data. The integrity API isn’t a substitute fo…

Backup function seems broken in 7.22 Firmware? config dir missing

Networking Solutions Issue

Mike July 17, 2026, 3:00pm 21

Have a peer at this conversation …