Finished testing restore function of recent core 166 release.
Did a backup of 165 using suggested console cmd "cd / && backupctrl include", and restored to a fresh install of released core 166
All items I checked worked great except that the Log summary files did not get restored. ( eg: /var/log/logwatch/2022-03-30 could not be opened ).
Looking into the ipf backup file there was no /logwatch subfolder within the /var/log/ folder. So it appears the problem might be with the
"cd / && backupctrl include"
If the WebUI of 166 uses this same backupctrl, then this could be the bug and not the actual restore. I will test later doing a WebUI backup of this restored 166 and restore onto again a fress 166 install
All in all, you guys have done a great job at nailing this one down and was well worth the rushed release.
See below for details of what I tested and worked ok.
As far as I can see, those summaries are not supposed to be a part of the backup.
I don't know what the rationale is for that, and I would suggest adding them.
@Peter: Would you please take care of this?
If the backup 'excludes' logs, then I would agree.
But it's a historic log like any other log.
It's not a show stopper, as I've noticed this across previous cores. It's one of those 'Now you see it; now you don't.' type of logs after doing a 'logs included' restore.
Again, not a show stopper by any means.
Apologies for my tardy reply on this one.