Confirming data disaster using SuperDuper under Leopard - marmaladewanker

Well, it was really a combination of errors on my part.

First, I backed up my 10.4 system using SuperSuper. All went well. Then I upgraded to 10.5. I launched my SuperDuper application (again) to backup my new (updated) system and made sure I had the application check with the server for "Updates." There were none. SuperDuper said it was up to date.

So, I presumed SuperDuper was compatible with Leopard. I started copying over my old system on my external FireWire hard drive assuming everything was OK. I was wrong.

SuperDuper should have "failed-safe" and made sure to tell me that it wasn't compatible with Leopard.

I *assumed* that no message from the developer (upon the application connecting to their Web site) meant that SuperDuper was compatible with Leopard.

My backup was then hosed and I frantically contacted the developer. He told me not to use SuperDuper. That's when I searched the Web and found out about CCC's compatiblity with Leopard.

There are many other gory details, but that is the gist. Imagine how much grief *thousands* of users could have been saved, if SuperDuper had just made a phony build that was automatically triggered when it checked for updates. It would simply present a splash screen that said, "Since SuperDuper is not compatible with Leopard at this time, please utilize another backup strategy." It wouldn't be just good customer service, it might have also saved their business.

Reply to This | Parent

Tuesday, January 08 2008 @ 06:48 PM PST