Skip to main content

Backup - Catalogs with fully managed images

Comments

10 comments

  • Paul Steunebrink
    I never take a backup facility for granted. No expectations or assumptions only. Backup and restore and review the whole process from begin to end. I learned it the hard way, a few times.

    As you noticed, only the catalog database file is backed up. For an entire backup, use backup software, sync software or manually copy the entire catalog folder.
    0
  • mli20
    Paul, I agree with you not to take anything for granted when it comes to backups. We need to know for certain.

    However, I have to feel sorry for the average user that there must be so much confusion as to what Catalogs in CO are really doing. Like, the Image Quality Professor says:



    "If you use Fully Managed Image Files then they will also be stored in this Catalog file".

    Well, it just isn't so, is it?

    Here's to hoping that Phase One pays attention.

    Cheers,
    Mogens
    0
  • sizzlingbadger
    So how do you restore a catalog that contains images from a catalog backup ?
    0
  • mli20
    Catalogs really don't see much use around here for obvious reasons. I use PhotoSupreme and is at present looking at Lightroom, fascinated by being able to use the X-Rite Colorchecker for creating my own customized Nikon camera profiles.

    I use Western Digital Smartware Pro, to monitor and backup selected files and folders automatically. It evens keeps versions of files, allowing me to go back a number of file generations. As a matter of course it also comprises restore functionality.

    Cheers,
    Mogens
    0
  • Paul Steunebrink
    mli20 wrote:
    ...
    Like, the Image Quality Professor says:



    "If you use Fully Managed Image Files then they will also be stored in this Catalog file".

    Well, it just isn't so, is it?

    To my understanding this is a correct statement. With fully managed files, the imported images are stored inside the catalog folder structure, in contrast to referenced images.
    0
  • mli20
    "Catalog file" and "catalog folder structure" are not one and the same, the first being a single file, the second presumably a number of files and folders.

    Image files in C1 are NOT kept within the catalog file, aka the SQLite database, the file with the extension .cocatalogdb.

    Cheers,
    Mogens
    0
  • Paul Steunebrink
    There can be confusion on the term catalog file. I suspected that already.

    On Mac, the catalog is presented as a single file, a.k.a. package. You can look into it with Finder and see all the files and folders. On Windows, you always see the entire folder structure. When users refer to the catalog in Finder, they mostly refer to the entire folder structure.

    One important piece in the catalog (folder structure) is the catalog database file, you already referred to. It is clear that the database file does not contain the image files, nor have I read such a statement in the blog you referred to.

    I think the misunderstanding is that you read the term catalog file for catalog database file. I hope it is now more clear.
    0
  • mli20
    So, for a Windows user to understand the workings of C1 he needs a knowledge of the filing system on Macs. That doesn't make sense in my world 😉

    Notwithstanding this, the real problem is that the user is lead to believe that his fully managed images are backed up together with the catalog (since they are said to be held within the catalog) when using the C1 backup function. As I have said already, they are not.

    This is what he'll see running C1 off a backed-up catalog with one fully managed image:

    http://mli20.smugmug.com/photos/i-JLJZjbv/0/S/i-JLJZjbv-S.jpg

    C1 cannot find the image, which supposedly is stored in the catalog.

    Cheers,
    Mogens
    0
  • sizzlingbadger
    I have been testing this.

    You have to backup the catalog package (Mac)/ folder (Win) while it is closed to get a useable backup if it contains images. You do not use the built-in catalog backup function as this only copies the sqlite database to a backup destination.

    To restore from the built-in sqlite database backup you have to create a new catalog in CO first. This creates a catalog package / folder structure. Then you can replace the sqlite database file in the package / folder with the one you had created from the built-in backup.

    If you are using all referenced files then thats pretty straightforward. I you have images in the catalog (folder / package) they will be stored in a folder called "Originals" and you will have to have a backup of that folder to be able to restore it.

    Which means you might as well copy the whole catalog structure as your backup solution instead of using the built-in backup function.

    Some work required by Phase One I think to make this more robust and simple.
    0
  • NN87501
    Back up feature does not work for me.. I choose back up to another HD and it does not but put to empty folders.
    Does anybody know where I can find more information on Back up option? I thought it would make a back up during a shoot so that I can have a copy/back up during a days shoot instead of manually having to copy the files to another disk. For me I click on the back up option and direct it to a separate Hard Drive but nothing happens. Just stores to empty folders.
    Thanks in advance for any help. Cannot find anything in the forums..
    MacBook Pro Retina. 10.8.5
    C-1 7.1.4
    Eric
    0

Please sign in to leave a comment.