When I ran nsru, I would also separately copy the /opt/var/lib directory, which contains the historical data for Chrony, Unbound, and VnStat. I would also separately copy /jffs/addons/YazDHCP.d which contains the data for YazDHCP. So when I reinstalled any of those scripts, or changed the USB drive, or needed to do a nuclear reset of the router to install a recent f/w version from an old version, I could restore that dir, and my old data for those scripts would be restored. Same for the YazDHCP dir. Copying that folder made my DHCP assignments so much easier, even when I went from my AC86U to my new AX86U. But I never figured out where connmon data was stored (oh, yea, I do that also). I also never figured out where each of the scripts stored their settings so I could easily restore them, although I now think some might be stored in /opt/share. I also now think the settings for BackupMon are in /jffs/addons. So as of now, I envision the new user file would contain 4 lines: /opt/var/lib, /opt/share, /jffs/addons/YazDHCP.d, and /jffs/addons/BackupMon. Hard coding those locations would be a problem if any of those script writers decided to change any of their locations, but I figured I'd deal with that if and when that happens. But maybe there is a better way to deal with this, like maybe a common API for all amtm scripts that would identify its storage locations so BackupMon could query them and use that data. But that is obviously outside my wheelhouse. For now, just having the ability to add sub-dirs to the backup list that BackupMon uses would be a help.