Skip to main content

Catalog size

Comments

5 comments

  • John Friend
    Top Commenter

    I sounds like you have things configured so that the Capture One catalog backups are going to the same directory that your catalog is in and thus the two are getting mixed together.  And, you have no process by which you trim old catalog backups so they just keep accumulating over time and by now you have 57 backups (each of which is a snapshot of your whole catalog).

    Here's my suggestion.

    Go to Edit/Preferences.  In the "General" tab, near the bottom, find the "Catalog Backup" section.  The find the "Location" section.  Write down where it is currently set (you will need this later).  Click the "..." to set the Location.  Pick a directory that is NOT the same directory as your catalog is located.  I put catalog backups in a specific top level folder named "Capture One Backups", but you can pick any location you want as long as it is completely separate from where your catalog is stored. 

    Then, you can go to the original backup location, find the backups and move them to your new backup location.  You will have to make very sure that you know what a backup is and what your catalog is so you aren't moving part of the actual, live catalog.

    Then, develop some workflow that trims the backups folder in some regular time frame.  I have a script that runs nightly and automatically that trims the backups to keep only the last 10 backups or 10 days worth of backups whichever is more.  It's amazes me that neither Lightroom or Capture One have code to allow you to set how many backups you want to retain so they automatically trim old backups for you.  It's such a required part of any regular use of the product, but a sorely missing feature.  I developed automated scripts for doing this for both Lightroom and Capture One for myself.

    0
  • Hank

    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
  • John Friend
    Top Commenter

    I don't know what you mean by "in the package". 

    On Windows, a Capture One catalog consists of a xxxx.cocatalogdb file and then several sub-directories that contain more files and more sub-directories.  Everything is just files in the file system.  I have backups of only the xxxx.cocatalogdb file in that same directory that appear to correspond to when I did upgrades (so probably when the catalog database file was upgraded to a newer format).  Those have names like xxxx.cocatalogdb.backup and xxxx.cocatalogdb.backup 1, where xxxx is the name of my catalog.  My regular catalog backups from daily backups are kept elsewhere.  One can presumably delete those once you've been running for awhile without incident on a new version.  Plus, as long as you have regular backups of your catalog, you're covered that way from an upgrade too.

     

    Here's a screenshot of my top level catalog directory:

    0
  • Hank

    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
  • John Friend
    Top Commenter

    Hank

    Yeah, that's pretty sloppy by Capture One to leave all that junk around, even worse if the junk is inside a package that many users won't even know about.  Good on you to do the import to a new catalog to clean things up safely.

    0

Please sign in to leave a comment.