Andriy.Okhrimets wrote:But catalog files are relatively small(it is actually small database), so I have no problem keeping them forever.
harald_walker wrote:I have multiple catalogs and within each catalog the SQLite database file is between 100 and 250 MB. Catalog are all on the local SSD disk and space is limited there. Each GB counts. I was able to regain several gigabytes of disk space by cleaning up old CaptureOne backups. For incremental backups I have my time machine backups.
If C1 would keep 1 or two copies, that would be more than enough and is basically just for disaster recovery like Aarons problem.
Paul Lindqvist wrote:harald_walker wrote:I have multiple catalogs and within each catalog the SQLite database file is between 100 and 250 MB. Catalog are all on the local SSD disk and space is limited there. Each GB counts. I was able to regain several gigabytes of disk space by cleaning up old CaptureOne backups. For incremental backups I have my time machine backups.
If C1 would keep 1 or two copies, that would be more than enough and is basically just for disaster recovery like Aarons problem.
You don't have to have the back up on your local SSD, just set it to be stored somewhere else. As for backing up the DB files, there a plenty of software that can manages that and do it well.
harald_walker wrote:Paul Lindqvist wrote:harald_walker wrote:I have multiple catalogs and within each catalog the SQLite database file is between 100 and 250 MB. Catalog are all on the local SSD disk and space is limited there. Each GB counts. I was able to regain several gigabytes of disk space by cleaning up old CaptureOne backups. For incremental backups I have my time machine backups.
If C1 would keep 1 or two copies, that would be more than enough and is basically just for disaster recovery like Aarons problem.
You don't have to have the back up on your local SSD, just set it to be stored somewhere else. As for backing up the DB files, there a plenty of software that can manages that and do it well.
Please read again what I first wrote, it also makes the same backup within the catalog file on the SSD. I know that I can change the backup location in preferences to an external disk.
Paul Lindqvist wrote:Im not sure i understand, are you saying that it backups the database on two locations, one always in the catalog folder and one in the location you specified in the preference panel ?
I just tested this and i have no backup databases in the original catalog folder, just get them in the location i specified.
harald_walker wrote:Paul Lindqvist wrote:Im not sure i understand, are you saying that it backups the database on two locations, one always in the catalog folder and one in the location you specified in the preference panel ?
I just tested this and i have no backup databases in the original catalog folder, just get them in the location i specified.
Yes, exactly that. Here is a screenshot.
I guess this is another bug then.
CaptureMann wrote:Poor Aaron just wants a solution to his problem - not a bunch comments about why he did or did not back up his catalog.
Shame on all you perfect people for trying to malign him instead of helping him with his problem.
BerndInBerlin wrote:Have posted this for another person who had the same problems:
I managed to "recover" a destroyed catalogue by simply creating a new one and importing the old damaged one.
Dear Phase One - with all due respect for the great work on this software. Maybe it is time to make a public announcement that Capture One 9 is at present NOT working reliably with Canon files.
A pretty serious issue that would affect one or two photographer out there.
HansB wrote:Rebuilding is also possible from command line. I don't have a broken catalog to test it, but maybe somebody wants to try it on a copy of a broken one? It's command line, so cd into the catalog file.
- Code: Select all
cd <YOUR>.cocatalog
mv <YOUR>.cocatalogdb <YOUR>.cocatalogdb.yourbak
echo .dump | sqlite3 <YOUR>.cocatalogdb.yourbak | sqlite3 <YOUR>.cocatalogdb
Another option might be to query VACUUM; on the catalog database.
Not sure if this works, but maybe it helps creating a solution.
Regards,
Hans
Andriy.Okhrimets wrote:It makes automatic backups of catalog file weekly. So in case of corruption you may revert.
Catalog files are always a single point of failure in any DAM, so back it up or sync to other drive to prevent cases such you are describing. I've got similar case with Lightroom and it cost me 2 weeks of work restore to correct state.
Return to Capture One 9.x Software
Users browsing this forum: No registered users and 9 guests