Home → Problems →

How do I know when CCC is finished cloning?

Admin Functions

• Remove

doug

29 Jul, 2012 03:16 AM

I am running the scheduled early morning cloning once manually. For a while, a progress window was open, but it has since closed. The CCC log seems to still be adding entries, but just once in a long while, like shown here:

7/29 11:46:47 Preparing...
07/29 11:46:47 Authenticating...
07/29 11:46:47 "Macintosh HD" has ownership enabled.
07/29 11:46:47 "CCC Clone" has ownership enabled.
07/29 11:46:47 [INFO] Volume mounted: "/"
07/29 11:46:47 [INFO] Volume mounted: "/Volumes/Recovery HD"
07/29 11:46:47 [INFO] Volume mounted: "/Volumes/Hao"
07/29 11:46:47 [INFO] Volume mounted: "/Volumes/Tao Two"
07/29 11:46:47 [INFO] Volume mounted: "/Volumes/CCC Clone"
07/29 11:46:48 Spotlight state on destination: On
07/29 11:46:48 Initiating synchronization engine...
07/29 11:46:48 DEBUG: [sender] Running the x86_64 executable (10001)
07/29 11:46:48 DEBUG: [dfcc: sender] Effective UID is 0 for // (10001)
07/29 11:46:48 [sender] Fileflags mask for //: 0 (10001)
07/29 11:46:48 DEBUG: [dfcc: sender] Setting effective UID back to 0 for source (10001)
07/29 11:46:48 DEBUG: [receiver] Running the x86_64 executable (10001)
07/29 11:46:48 DEBUG: [dfcc: receiver] Effective UID is 0 for /Volumes/CCC Clone (10001)
07/29 11:46:48 [receiver] Fileflags mask for /Volumes/CCC Clone: 0 (10001)
07/29 11:46:48 DEBUG: Max xattr size for the destination filesystem is 131072 bytes (10001)
07/29 11:46:48 DEBUG: [dfcc: receiver] Setting effective UID back to 0 for dest (10001)
07/29 11:46:49 Cloning...
07/29 12:10:15 rsync: recv_generator: mknod "/Volumes/CCC Clone/Users/admin/Library/Application Support/iPhone Simulator/5.0/Library/Application Support/Ubiquity/ubiquity.socket" failed: No such file or directory (2) (10001)

Did it finish? Usually it indicated how long it took.

Thanks,

doug

1. Support Staff 2 Posted by Mike Bombich on 29 Jul, 2012 03:25 AM

   

   Hi Doug:

   Are you sure the window is closed, and not just obscured by another window or in a different "space"? The task is still running. It looks like your tasks take about 75 minutes, so this one has some time left in it. In the CCC log, you'll see a line like this when the task has finished:

   07/29 04:44:47 iMac to CCC: Time elapsed: 01:14:42. Data copied: 29.61 GB

   Mike

   Admin Functions

   • Echo
   • Remove

2. 3 Posted by doug on 29 Jul, 2012 04:13 AM

   

   Hi, Mike.

   I think the task that took 75 minutes ending at 4:44 this morning was unusually long because I (stupidly) updated to Mountain Lion yesterday. So there was more to backup than usual.

   Anyway, yes, I am sure the window was closed. I "brought all to front" and it's not there.

   Did you see the huge time gap between "Cloning..." and the next message?

   Anyway, it seems it finally did finish. I just checked the log again and see this line at the end of the log now:

   07/29 12:33:43 iMac to CCC: Time elapsed: 00:46:56. Data copied: 873.26 MB

   That was about 45 minutes ago.

   Usually I don't run CCC manually like that, but I wonder why the log wasn't showing all along.

   I guess I should just check the log and wait for the end message and assume it's running and not depend on the window?

   Thanks,

   doug

   On Jul 29, 2012, at 12:25 PM, Mike Bombich <[email blocked]> wrote:

   > **** PLEASE REPLY ABOVE THIS LINE ****
   > **** Any part of your response that is below this line will be discarded ****

   Admin Functions

   • Split
   • Remove

3. Support Staff 4 Posted by Mike Bombich on 29 Jul, 2012 04:22 AM

   

   Did you see the huge time gap between "Cloning..." and the next message?

   That's normal (24 minutes in this case). CCC doesn't log progress indication, so you should expect to see a gap between "Cloning" and "Hiding files that should be hidden".

   I guess I should just check the log and wait for the end message and assume it's running and not depend on the window?

   You can certainly rely on the content of the log, but I'd be really surprised if the window closed without any indication in the log. It has a panel attached to it, so technically it can't close until the panel is dismissed, which won't happen until the task is aborted or finishes. I suspect the window was either lost offscreen or stuck in another space. If you changed screen resolution or made some other display configuration change, that could explain the disappearance of the window.

   Mike

   Admin Functions

   • Echo
   • Remove

4. 5 Posted by doug on 29 Jul, 2012 04:46 AM

   

   Mike,

   I didn't change anything regarding the screen during that time.

   Just out of curiosity, what keyword might I check for the panel closing? I tried window, panel and close but didn't see anything. This is not important, so no need to rush an answer.

   Thanks, as always,

   doug

   On Jul 29, 2012, at 1:22 PM, "Mike Bombich" <[email blocked]> wrote:

   > **** PLEASE REPLY ABOVE THIS LINE ****
   > **** Any part of your response that is below this line will be discarded ****

   Admin Functions

   • Split
   • Remove

5. Support Staff 6 Posted by Mike Bombich on 29 Jul, 2012 04:51 AM

   

   There's nothing logged specific to the window being closed. If I saw "User clicked the Stop button", I'd know that the task had been aborted and that the window would probably be dismissed. Even then, though, that isn't a given. Error messages could keep the window open, the defer panel could keep it open, etc. I haven't had a lot of problems with the task window itself in the past, so I don't have a lot of debug information sent to the log about it.

   Mike

   Admin Functions

   • Echo
   • Remove

6. Mike Bombich closed this discussion on 15 Sep, 2012 04:03 AM.

Comments are currently closed for this discussion. You can start a new one.