Need help restoring database
So this morning, all heck broke loose, I can't open my primary Catalog (67k images). It sees the database but can't verify and cannot repair.
I use the catalog in "reference" mode on a Mac. I backup-upon-exit regularly, so how do I restore? Do I just copy over my "bad" database file, replacing with a back up from a few days back? I'd like to know before I take a stab at it. I saw a post somewhere that I may then need to re-associate or reconnect the images to the database. Which is fine (if it works).
Any links, pointers, welcome....
Regards,
Pete
I use the catalog in "reference" mode on a Mac. I backup-upon-exit regularly, so how do I restore? Do I just copy over my "bad" database file, replacing with a back up from a few days back? I'd like to know before I take a stab at it. I saw a post somewhere that I may then need to re-associate or reconnect the images to the database. Which is fine (if it works).
Any links, pointers, welcome....
Regards,
Pete
0
-
Hi Pete,
Sorry for your misfortune. Yes, the restore operation works as you mentioned: copy a backup database over the original and start CO8 again. The database backup feature of CO8 only backs up the database (the most important part).0 -
Thanks, I was away for a few days but got it to work. I had also opened a ticket, the answer to which mimicked your response with one addition for Mac folks. Here's the story in a nutshell
1) Close Capture One
2) Find the corrupt production catalog in Finder
3) Right click on it, choose "Show package content"
4) You will see a file called "yourcatalogname.cocatalogdb"
5) Rename this to ""yourcatalogname.corrupt" (you can delete it later when all is back up and running)
6a) You will also find files called "yourcatalogname.cocatalogdb.backup" in the same package. Find the one with the highest number behind it as it is the newest (check also creation date) and rename the newest one to "yourcatalogname.cocatalogdb" (Basically remove .backup plus the number)
or
6b) copy the latest backup database from your "catalog backup" location set in General preferences.
In my case, I have C1 set to backup daily so I simply copied the backup database (in the 6b location) from the day prior to the issue occurring and pasted it into the production catalog package.
Restarted C1 and it's fine.
Regards,
Peter G.0 -
Thanks for your feedback and great you are back on track again! 0
投稿コメントは受け付けていません。
コメント
3件のコメント