1. Welcome to the new MacRumors forums. See our announcement and read our FAQ

carbon copy cloner: doing full instead of incr. bkup each time?

Discussion in 'Mac Applications and Mac App Store' started by G0meZ, Nov 20, 2012.

  1. macrumors regular

    it seems to me that my ccc bkup is doing a full backup instead of incremental each time. eg. it copies all my apps every time.
    i've tried with two ext fw800 hdd, bkup up my 500gb internal drive... it keeps taking some 1.5-2hrs each time, day... what could that be? log file says nothing...

    (latest ccc version on osx.7.5 on mbp8.1)
  2. macrumors member

    Just delete and rebuild the task...
  3. macrumors regular

    nah, done that
  4. macrumors regular

    just checking the last log entry:
    after all, it seems to not do a full bkup: 18.8gb took 02:41hrs...but that can't be right on fw800, no?
    also, 18gb is way to much for an incremental bkup as far as i can tell...largest file copied is 17.2gb according to log...must be the frikking windows instance i suspect...maybe just exclude that volume then?
  5. macrumors 68040


    Yeah it can't track individual files in the virtual machine. Instead all CCC knows is that the VM has changed and needs to be completely backed up. If your boot drive and VM are on the same drive and your VM is running this can make the backup very slow.

    This is also a problem that occurs with large database files such as an Outlook PST.

    I would also set up a backup to run from your VM to another drive for any files you want to protect in Windows.
  6. macrumors regular

    i know, never have that monster running unless i absolutely have to.

    no need for that. have taken the win-dir out of the ccc list...
    but still, something's funny...ran a full ccc clone, took >2hrs (~350gb), rerunning same clone takes now already 1:44, comparing files forever and still copying ~600mb now :confused:
  7. macrumors newbie

    Drop us a line over at help.bombich.com (use the "Ask a question" menu item from CCC's Help menu). It sounds like there could be either an issue with communication to the destination disk, or perhaps some sort of competition for bandwidth.

  8. macrumors regular

    thank you mike, i'll do that

Share This Page