Catalog size
My master catalog is 30 GB larger than it should be! Looking in the package file there are 57 "backup files" in the package. What are these for? Why were they created?
I imported the catalog into a new catalog and the size of the package was reduced by 30 GB.
the original was about 34GB and after import into a new catalog the new catalog package was 4GB with no "backup files in the package.
Is there an official way to deal with this? ie. reducing the size of a catalog?
-
the backups are in the Capture One Catalog package, so not specifically in the same folder as the catalog.
The reason I found this is I am moving data to a new computer and was investigating the catalog size.
I have specified an external drives for the backup. These "internal backups" have been collecting there for many years since the catalog was created. I was thinking it might have to do with the process of upgrading the catalog to a new version of Capture one. However that would be quite annoying, due to the size of the catalog packing increasing.
0 -
For the MacOS version these directories are kept in a special file called a package. I can open the package and see the contents, however this is not a normal thing for a user to do. The package contains resources used by the application, and generally is accessed only by the application processes.
I have the same directory structure as you show, since I have kept the same master catalog since 2015... there is at last count 59 backup database copies in the directory adding up to 30GB, This is very strange behavior for any program! There is no mention in the documentation about having to delete these files (or that they even exist), Thankfully, importing the master catalog into a new catalog did not copy the backups.
0
Post is closed for comments.
Comments
2 comments