I wonder if anyone else is seeing this? I couldn’t see any mention of it in recent posts, since 2.53 was released.
I backup my Nucleus One via two recurring backups:
- external SSD, daily, max 99 backups
- Dropbox, every 4 days, max 6 backups
Recently, Dropbox informed me I had run out of space. Checking the Roon backups, I find I now have 10, rather than the “max 6” specified in the backup schedule.
Looking more closely, I see that the Roon backup shows two sets of entries under clean/restore, for the Dropbox backups. One set has 6 entries, under a particular “identification”, i.e. the long hexedecimal string. The second set had 4 entries, under a different hex string ident.
When I checked the daily backups to external SSD, I saw the same: one set of backups with one hex id, with what looked like 99 backups, then a second set under a different hex ID.
There is only one Roon server here, and one external SSD, and one Dropbox account. But two sets of backups in each location.
Obviously, since the “max” setting is per backup ident, not per backup location, that explained why I had 10 backups filling up Dropbox, despite setting a max of 6.
The second set of backups (in both locations) appears to have been created for the backup on July 10th.
I note that 2.53 was released on July 8/9, so it’s likely that I installed it around July 10, which may indicate something.
Anyone else seeing a fresh set of backups starting around the date they installed 2.53?
It’s obviously not a huge issue, but does rather mess up the “max” setting per backup.
I don’t know what the backup hex “ident” signifies, but it seems that it changed when I installed 2.53?
