No module should depend on backup by design. That said this could be a bug in dependency handling. Perhaps even an edge case that has been around a while. The dependency being added is what seems to be causing this but may not be the root issue. Backup should simply install first and it isn’t. This is likely a bug in framework. The only dependency in backup is filestore. I haven’t looked at that but perhaps filestore needed an update so backup was pushed back behind sipsettings. I honestly haven’t looked at the dependency code in like 10 years. This requires someone to sit, break it, and fix it repeatedly to debug what is falling in it’s face. This is why I also mentioned needing a solid reproduction path so it can be repeatedly and consistently put in this state to find and test a fix.