Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Cloning via Carbon Copy Cloner *does not* disable journaling' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Cloning via Carbon Copy Cloner *does not* disable journaling
Authored by: bombich on Sep 20, '06 09:40:52AM

A few comments from the author of CCC (me):

1) Journaling does not prevent drive corruption, rather it prevents inconsistencies in the filesystem. Issues with users being unable to login is more likely to be caused by database corruption (e.g. incomplete transactions) in your LDAP database than a filesystem inconsistency.

2) Cloning Mac OS X Server is not supported by CCC (view the system requirements). I have never recommended using CCC for MOSXS. While it will work in many cases, there are specific issues with cloning open databases that I have never addressed, nor desired to address. If you are cloning or backing up Mac OS X Server, I recommend using tools that are designed for dealing with Mac OS X Server.

3) There is no code in CCC that disables journaling. I just performed the following test:

a) Format the target volume with four partitions, each formatted as "HFS+ (Journaled)"
b) Restore a disk image of a standard installation of Mac OS 10.4.7 to the first partition --> Journaling still enabled on all four partitions
c) Use CCC to clone the boot partition to the second partition --> Journaling still enabled on all four partitions
d) Rebooted from cloned partition --> Journaling still enabled on all four partitions

I think something else is going on here, and it is not related to CCC.

---
Mike Bombich | Bombich Software | http://www.bombich.com



[ Reply to This | # ]