Once again I state very clearly: I’ve always had success using SD to create bootable backups, no matter which OS I have used, and no matter which Mac I have had. I hope that is clear by now.
I did read previously about some of the issues you mentioned. For the past 6 years or so, I’ve been using Samsung SSDs for my backups (plus other activities), so not sure how much that has played a factor with my success. But even before then, the Seagate HDs I had been using worked fine also.
I would think Apple will fix that issue regarding bootable backups, It sure would be extremely disappointing if they did not!
I also am interested in how people think and behave, Some of my favorites:
That’s amazing. Even Dave Nanian was reporting SD couldn’t make bootable backups in his Jan 31st 2021 blog. The work around was doing it the way that is now standard on CCC.
Dave’s comments in that blog are a good summary of the problems that led CCC to changing policy around that time.
Honestly do not remember anything about Big Sur and issues with SD. But even with that, obviously David (and maybe Apple?) fixed it. Again, never had any issues with bootable backups created by SD for any Mac OS I have used, and for any Mac I have owned.
The creation of the bootable backup is straight forward in SD. Nothing “weird” needs to be done.
Yes, the bootable clone situation has improved substantially since that period.
Indeed, there have been a few times where Apple has broken its own asr tool, in much the same way they’ve broken other things (hey, without stuff breaking, there’d be no need for updates)…and since it’s a forcing factor for OS copying, if it’s broken (as it is a bit in Golden Gate; we’ve reported the same issue as well…but it’s a BETA so you expect this kind of thing), that part doesn’t work.
But as I’ve said, and continue to say, the ability to boot is a nice-but-not-required for restoration. Your backup is good—made properly—whether it boots or not.
Yes indeed. Even in the olden days of integrated system volumes I preferred to restore by reinstalling a clean new system and migrating with Setup Assistant, rather than relying on a bootable clone. Fortunately I have never been in the situation where an immediately bootable external clone was needed. If I had a problem with my internal, my focus was always on sorting out the internal rather than booting from an external, which I have found a very tiresome process with all the re-authorisations and re-syncing etc my installs needed. I accept that some people need to boot from a clone, which of course is not possible if the internal is completely dead. If a business is dependant on immediate continuity I think a second computer is preferable.
I have not…but will download and give it a whirl. Probably won’t switch as I’m happy with CCC though, but I will take a look.
Would not ask you to switch, Neil: I’m glad you’ve found something you’re satisfied with.
The point was more that you probably haven’t looked in a while, so you might as well base your critiques on the current state of the product, rather than what you used before.
For a “casual” user like me, I appreciate it David that you have made the creation and stability of bootable clones a reality! Although there have only been a few times where I’ve needed to boot from one of them, I’m glad that is a viable option.
One other thing I’ve just discovered, and excuse me if I make a conjecture. I FINALLY realized that by changing the security on my external SSDs where the SD clones are on (specifically ignore permissions), I no longer get that “Authorize” nonsense any more. Could that also be the case as to why Golden Gate is not “allowing” such devices to show up in the Start Up Disk “area”? Again, just a conjecture.
I certainly don’t change security on the drives, no. And no, that’s not why; they’re not properly doing all the finalize steps in the Golden Gate asr.
I think for my external SSDs that ONLY contain SD backups, it should be fine. They never leave my place. If I do need to take one of them with me, then I’ll change the Security back.
But speaking of that “Authorize” business, is there any way I can do something to stop those annoying prompts? By the way, SD 3.x does not do that.
Arthur Kent
Click the lock in the lower left?
That is what I did, but then I had to change the Security to “None” (or whatever it said).
Perhaps I don’t understand what you’re seeing here, Arthur, and it’s a bad place to do support. Why don’t you send a screen shot of what you’re encountering to me at the support email instead of bothering these nice folks with this.
But I was just answering your question. I’ll take you up on your request though.