Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Verify and Repair of database fails... what next?

Comments

4 comments

  • Eric Valk
    I'm also an ex Aperture user. I made the transition a few years ago, however.

    Database errors are now less common the formerly, but still nasty when they happen.

    Since all your images are inside the catalog, you have two choices
    • Re import from Aperture

    • Open a support ticket and ask the support team to help recover the catalog


    What I reccomend in the future is

    • Store your images outside catalog, and configure Time Machine to back them up.

    • Configure Capture One to back up every time you close the catalog, or daily.

    • Configure Capture One to back up images on import (on an external drive)


    Then, if something goes wrong, you will have something to work from.
    0
  • Permanently deleted user
    Thanks for the advice. I ended up extracting the old images (not the ones imported from Aperture - I'll deal with that later - but the ones from my camera) and just starting a new catalog. I lost about an hour of work, but lesson learned... kind of disappointing, I have to admit; I always had the "vault" backup system for Aperture in case something like this happened, but it never happened. I always thought of Capture One Pro as a more premiere product than Aperture, and yet here we are, years after I last touched Aperture, and it's such a seemingly basic problem to encounter... and the repair mechanism seemed to fail so badly.

    Do you think that Time Machine backups are sufficient? In theory I could just recover the catalog file from a Time Machine backup. I poked around the backup part of Capture One and I didn't see an easy way to have it be scheduled or automated, but maybe once you make a backup then there are more screens that appear...
    0
  • Eric Valk
    [quote="Reign of Crows" wrote:
    ......
    Do you think that Time Machine backups are sufficient? In theory I could just recover the catalog file from a Time Machine backup. I poked around the backup part of Capture One and I didn't see an easy way to have it be scheduled or automated, but maybe once you make a backup then there are more screens that appear...


    I do not think that Time Machine backups are sufficient. Time Machine is an incredibly handy backup service to handle the “where was that file that I was using last week†situations. But Time Machines file and link structure can be corrupted and then you are done. Time Machine also purges very old interim backups, and this can leave you hanging.

    Don’t get me wrong - I use Time Machine and like it, but I do not rely on it as my only backup.

    In Capture One General preferences there is a setting where to backup the catalog, and I think it is there you indicate when to back up the catalog. I selected “every time I close the catalogâ€, and a location on an attached backup drive (not my Time Machine drive).

    On the C1 import menu there is a sub menu that allows you to back up image files on import. I see this as just what is needed. One mechanism archives the files on import, another backup the organization and editing details. And then Time Machine backs up both image files and the database.

    And don’t store images in the catalog. It’s fine when it’s working, but a disaster when it doesn’t.
    0
  • Jerry C
    It is most comforting to have a good backup plan that defends against catastrophic failure.

    I back up my catalog every time I make changes I would not want to lose. Since Capture One 8, I have only had to deal with 3 corrupted database events. When that happened, I found that only thing you have to do is replace the corrupted cocatalogdb file with the last backup. The data in other files in the same cocatalog package with the corrupted database were never the problem. Restoring from backup is supposed to be a selection from within Capture One. If it works as advertised, you would not have to manually copy the database file into the catalog package.

    It is also wise to keep your raw files outside of the catalog as referenced files and a copy of the raw files in an off line portable drive along with a copy of the cocatalog. There are a number of apps, like ChronoSync, that will expeditiously sync changes/additions to your off line catalog and referenced files. Not only is this a complete backup, you can plug it into any other computer with Capture One and run it from the off line drive or keep it in your safe deposit box. Better, rotate the copy in the vault with another copy and keep both updated frequently.

    Jerry
    0

Post is closed for comments.