Hello Michael, lets divide the answer in a general and specific part. - X3 and X7 operate of different HW. The Units like PLC have the dependicies on the expected HW (the bootproject reply with the generated code on the x3 or x7 HW). Changing the based HW need to modify the target the code will be build for in the ctrlX-PLCEng. project. - Maybe the rest of the apps shown in your screen shot does not have the dependicies. - Instead of trying to get the "older" app versions placed to a newer LTS-image (assume 2.6LTS) it would be better to store the bakcup without the app-versions and focus on the apps-data. - Moving older-app version to newer image base may bring conflicts in the RT-part where Automationcore interacts with Motion/Ecat/PLC. these 4 Apps are supposed to interact in the same versions at least.
Now to the issue of not being able to store the backup-data. The OP state is fitting. The failure message indicates that one the copy process of (at least ) one the app-state of the acitive config can not be done. Most likely because app-functionality is blocking the copy procedure because of still open file operations by the app itself. The Solution app tries to create the backup but is blocked because the needed operations are blocked by ... I guess the InfluxDB app. We suppose file operations (saving continuously data) are ongoing and disturbing. That lag of flexibility is fixed by IDB-V-0304. Remember to Disable the InfluxDB app even working under 2.6 LTS. A meantime workaround is feasible by Disabling the InfluxDB under System/apps before running the Backup. Please consider to skip the apps itself and restore just the app-related data on the new system.
Please return with some feedback.
Bye
... View more
