I'm curious why my ON1 database backup for about 16,000 images is: 917 MBytes. I know from reading articles that it doesn't contain my actual images.
When I look at the sum of my sidecar .on1 files, and the few .onphoto files, they together amount to 177 MBytes. I would expect catalog info and the few albums I have to only contain filespec pointers. All of those should be small. Presets that only pertain to settings would also be small.
I went hunting for sizeable contributors to the 840 MBytes difference.
Under c:\programdata\on1\extras 2023\ there is a mix of files which I did import (didn't know their size initially) and some surprising additional files. It seems that the imported extras for Occudrone skies and Sunsets and other skies account for 263 MB on disk. I didn't import Textures 165 MB, Borders 203 MB, nor Backgrounds 291.2 MB. Those together are close to the difference. The don't appear within the ON1 app under Manage Extras.
To me, standard ON1 elements aren't pertinent to my instance / database. They'd get re-installed at another PC when ON1 program would be re-installed. Having a lot more included in the database extends the time to close down running ON1, and of course extends the time and disk space consumed for backups.. I have an open support case on this.
Are other users seeing a lot of baggage in their ON1 backups?
Please sign in to leave a comment.