SuperDuper is the wildly acclaimed program that makes a recovery painless because it makes creating a fully bootable backup painless. Its incredibly clear, friendly interface is understandable and easy to use, and SuperDuper! a built-in scheduler that makes it trivial to back up automatically. SuperDuper’s interface confirms all your actions in simple, clear language to ensure that the end result is exactly what you intended.
- Download Link
- Supported Operation Systems
- Features
- Screenshots
- Whats new?
- macOS 10.10 or later 64-bit
- Your hard drive starts making that horrible clicking noise that signals an imminent meltdown
- A momentary lapse of coordination causes your MacBook Pro to take a dirt nap
- SuperDuper the system suddenly fails to boot
- Your most important day-to-day application isn’t working with the system update you just applied
- The new driver you just updated is causing your Macintosh to crash
- That lousy software you just tried didn’t come with an uninstaller and scattered files all over your drive
- You need to restore a SuperDuper stable copy of your system, but don’t want to lose what you’ve been working on
- You need to test new versions of the operating system with production data you can’t afford to lose
- Details are in the Revision History, but to highlight a few things: Backup on Connect no longer runs over and over if you use Erase, then copy on Big Sur.
- This had to do with some very low-level changes to some Big Sur APIs that messed with our code that detected whether we were already running a copy for that volume.
- The bug was useful for testing a zillion back-to-back Erase, then copies, though, so there’s that. Yeah! We meant to do that! Sure!
- Erase, then a copy was using asr to copy Catalina, which was unintentional. It now does the same thing v3.3.1 did.
- Send to Shirt Pocket was failing for users in all versions of SuperDuper due to a locally cached response of a value that had been updated on our server.
- This turned out to be rather interesting, and frustrating because we don’t have a way of “fixing” old copies…although they will “fix themselves” over time…anyway, it won’t happen anymore in v3.5 B2 and later.
