Based on the backup history on my USB drive where the last backup that I can read was on the 4th March this year, I would consider it likely that it was the release on the 27th March that is the likely culprit:
If not that release, it may have been the next release:
Which of the two was the cause would depend upon the date that I applied the updates which could easily have been delayed a couple of weeks at that time since I was rarely in the house.
Great info! That would also explain why my Scheduled backups in the 6 mos after March could not be found when I checked in Find Backups last month (I had Scheduled backups set up for weekly, 26 max).
Now Find Backups can see the backup created by Force Backup Now (either 2025 Nov 7 19:21:59 or Nov 7 19:14:59) and Scheduled Backups (2025 Nov 8 03:00:00)
We were able to reproduce your problem internally.
The likely issue that’s the cause of the problem is that when writing a backup to the root of the disk - file “roonbackup_root_” is not created which is also a part of backup .
That’s why you can’t see the backup made to a root of the disk.
The “Backup now” option eliminates this problem by simply restricting and not letting you to write a backup to the Root of the disk.
We have open an internal ticket for investigation and will keep you posted on a progress.
Thank you for the update. I’m glad you were able to reproduce the issue and hope it is easy to fix.
I don’t know if this makes any difference, but I do see a file named " roon_backup_root" that was created in the root of the disk, outside of the RoonBackups folder, along with the database backup that was also created outside of the RoonBackups folder (see the folder and file dated 11/7/2025). Of course, being outside the RoonBackups folder, Find Backups cannot see this.
Now I’m questioning if I remember this correctly. Did I actually check Find Backups, or did I just see that Scheduled Backups reported a successful backup?
I suspect this affects many more users who do not realize it. It would be a real kick in the pants to need to restore a backup only to find their backups can’t be found.
Until this is fixed, I guess I’ll be using Backup Now much more often and not relying on Scheduled Backups (I still have automatic backups scheduled using a workaround, but I’m not going to rely on it like I have before).
Thanks for performing that test, we have added this info to the investigation ticket. The ticket has been submitted for developer review, meaning that this may take some time to be reviewed.
There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.
Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.