unmount after backup not desired

mma's Avatar

mma

02 Aug, 2012 09:20 PM

After a backup I see the volume that contains the backup disappear from my desktop. I have not ready anything in the 'Settings' of the scheduled task (when I click 'run') that mentions unmounting of a volume.
What is the default strategy? I can imagine safety considerations requiring an unmount of the destination volume if the volume was originally not mounted and CCC took care of mounting the volume prior to backup, but what behavior can I expect for volumes that are already mounted and then put into a backup task as backup destination?
I get the impression that these, too, are unmounted. Is my observation correct, and if so, how can I prevent this?

  1. Support Staff 2 Posted by Mike Bombich on 02 Aug, 2012 09:49 PM

    Mike Bombich's Avatar

    Hi Ard:

    There are three scenarios in which CCC will unmount a volume:

    1. You specified a disk image file as the destination. In this case, CCC will mount the disk image at the beginning of the task and unmount it at the end.
    2. You have specifically requested that the destination volume is unmounted in the "Before & After" tab of the Scheduled tasks window.
    3. CCC mounted a network volume as the root user (only applicable Lion+). When this occurs, you actually don't see the network volume on your own Desktop, which is why CCC specifically ejects these mounts.

    Looking at your past logs, I can see both #1 and #3 occurring. If you want to avoid having CCC unmount a disk image volume, mount the volume, then select the mounted volume as the destination. When you select the mounted volume as the destination, CCC assumes that this is a volume you want to keep mounted, so it won't unmount it at the end of a backup task.

    Mike

  2. 3 Posted by mma on 03 Aug, 2012 07:35 AM

    mma's Avatar

    > When you select the mounted volume as the destination, CCC assumes that this is a volume you want to keep mounted, so it won't unmount it at the end of a backup task.

    Clear. Is there any chance a mounted volume is a destination and thus remains mounted, one time is not mounted, CCC changes the nature of the destination to #1 or #3, mounts it, does task, unmounts it and in the future, even when the image is mounted at the start of the task, CCC will unmount it when finished?

    I ask because Im hunting down The Great Unmounter Monster. It is one of four I can think of: glass fibre modem nightly interrupt, NAS on the other end of the interweb, Synk or CCC...
    Now CCC has been switched off for a day or 2, I haven't experienced unmounts (yet). Yes, I'm familiar with coincidence 8-)

  3. 4 Posted by mma on 03 Aug, 2012 08:08 AM

    mma's Avatar

    > 1. You specified a disk image file as the destination. In this case, CCC will mount the disk image at the beginning of the task and unmount it at the end.

    Hmm, I read this phrase again a few times. CCC might, but that is ambiguishly stated above, always eject the destination IF it is a disk image, regardless of wether at the beginning of the task it was mounted or not.
    When the disk image file was not mounted at the beginning of task execution, things are clear: the image will be unmounted.
    What happens if the DISK IMAGE (implies eject) was mounted at the start of task execution?

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

  4. 5 Posted by mma on 03 Aug, 2012 09:03 AM

    mma's Avatar

    >> 1. You specified a disk image file as the destination. In this case, CCC will mount the disk image at the beginning of the task and unmount it at the end.
    >
    > Hmm, I read this phrase again a few times. CCC might, but that is ambiguishly stated above, always eject the destination IF it is a disk image, regardless of wether
    whether of course.
    > at the beginning of the task it was mounted or not.
    > When the disk image file was not mounted at the beginning of task execution, things are clear: the image will be unmounted.
    > What happens if the DISK IMAGE (implies eject) was mounted at the start of task execution?

    I worded that ambiguously too. I mean 'was already mounted [by the system, the user or another app] at the start of task execution'.

  5. Support Staff 6 Posted by Mike Bombich on 03 Aug, 2012 07:06 PM

    Mike Bombich's Avatar

    Hi Ard:

    Hmm, I read this phrase again a few times. CCC might, but that is ambiguishly stated above, always eject the destination IF it is a disk image, regardless of wether at the beginning of the task it was mounted or not.

    It isn't a matter of whether the disk image is mounted when the task starts, it's a matter of whether the disk image was mounted when you created the task. But more importantly, it's a matter of whether you chose "Existing disk image" (or "New disk image") from CCC's Destination menu vs. selecting a mounted volume. If you specifically selected a disk image file as the destination, CCC assumes the responsibility of mounting and unmounting the disk image file (whether it was mounted or not when the task starts). If you select a mounted volume as the destination, CCC only assumes the responsibility of mounting that volume (if necessary), not unmounting it.

    So if CCC is unmounting the disk image, delete that scheduled task, then reconfigure CCC, choosing the mounted disk image volume as the destination. Create a new scheduled task and you should be all set.

    Mike

  6. 7 Posted by mma on 03 Aug, 2012 07:15 PM

    mma's Avatar

    > So if CCC is unmounting the disk image, delete that scheduled task, then reconfigure CCC, choosing the mounted disk image volume as the destination. Create a new scheduled task and you should be all set.

    Right. I think with that we will have the problem solved. See: the first time indeed I asked CCC to create a disk image and put the whole source onto it. Then I presumed that once the image was mounted, it would stay mounted. Not so apparently. Luckily the solution is easy once you know what is going on. You have it all well thought out and documented.
    Thanks for the clear answer.

    Cheers,
    Ard

  7. Mike Bombich closed this discussion on 20 Sep, 2012 05:01 AM.

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