![carbon copy cloner network drive carbon copy cloner network drive](http://cdn.differencebetween.net/wp-content/uploads/2021/05/Difference-Between-Carbon-Copy-Cloner-and-Time-Machine.jpeg)
![carbon copy cloner network drive carbon copy cloner network drive](https://www.podfeet.com/blog/wp-content/uploads/2019/11/Carbon-Copy-Cloner.png)
CARBON COPY CLONER NETWORK DRIVE MAC OS
I have a relatively laissez-faire attitude to software updates, because my experience through using the Mac OS since 1998 - from OS 8.5 through OS 9 and 9.1 to OS X, is that everything generally works whatever you do, and that we haven't generally experienced big problems with security - up until recent years. There's a big difference in the way many Mac users think about software to those from the Windows background I think, it's rooted in history and the roots are deep. I guess that kind of error will occur on number of occasions wouldn't it? While cloning, stuff is still happening on the source disk if it is currently running the OS, isn't it?Īlthough I have CCC4 (4.1.20), I actually use version 3.5.7 most of the time since it still works for Mavericks and does the job well, and I prefer it's interface. I would still expect the clone to work properly. Was it an actual clone failure, or just that it wouldn't verify? If it was a verification error then I'm sure the clone would've worked except that one (or two) files might have been different, not a big deal perhaps.