To the Mac, it just looks like one 6TB drive. I have my QX2 set up as a 6TB volume (4 X 2TB drives as RAID 5). There it was, safe and sound on my Desktop. This morning, I turned on my OWC QX2 for a weekly backup. So it appears that either the volume size is at issue (6TB vs 2TB), or there is something about the device itself (both devices used the same PCIe eSATA card, a FirmTek SeriTek 2ME4-E). Update! I cloned my Master volume to a 2TB backup drive- different and correct behavior (no “Initiating system restore.” nonsense). As it was, it turned a 10 minute quick update into a 5 hour backup. If this had been in place, I would never have proceeded with the clone. In the case of a full erase and copy, the user should be told explicitly that the volume will be erased, and this should be confirmed with a dialog eg “ The entire target volume Backup will be erased and the entire contents of the source volume Master will be copied to it. The fine-print at the bottom of the window should be eliminated it is long and confusing at best, and ambiguous as to what will actually happen. The user should know exactly what will happen, since the behavior could change unpredictably, depending on current system status (eg apps running with open files, or not). This non-deterministic behavior is confusing, and needs to be addressed in the user interface. So CCC thus chose to perform a file-level incremental clone, which is what I wanted all along. The difference? Today I had files open on the source volume (as I almost always do), so that CCC could not unmount it. Retesting today showed totally different behavior. At that point, I had no backup left, since it had just been wiped out. This caused software I had running (Dropbox) to immediately complain, which startled me, which is why I then clicked Stop. In my case, a particular detail contributed: CCC was able to unmount the source volume, and thus was able to wipe out the target volume in preparation for a block-level clone. I took it to mean “will be efficiently updated”, since that’s what had always happened for me before. The fine print at the bottom of the main window that states “What will happen” is contradictory it’s an either/or, so the user can’t know what will really happen. For me at least, that totally defeats the purpose of using CCC for backup.ĬCC does issue a "may delete files and folders" warning, which I understood/understand to mean files and folders that no longer exist on the source volume, not all files and folders. That means wiping out the target volume and recopying the entire source volume, or at least all 1.8TB of data on it. This saves considerable time, since only changed items are copied.īut with the 6TB volume, CCC chose to do a block-level clone this particular time (explanation below). In that case, CCC always does an incremental clone, exactly what I want. I was contacted by a very concerned Mike Bombich, author of Carbon Copy Cloner, and I believe I now understand what happened.Īll my past cloning for backup purposes has been from a 3TB volume(with 1.8TB of data) to a 2TB volume. The facts I stated have not changed, but there is an explanation. Update - My original post follows verbatim further below (excepting the title). SEND FEEDBACK Related: backup, Carbon Copy Cloner, cloning, display connectivity
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |