-Tumbleweed666
Sorry, I misspoke. Your method is what I meant - two, serialized backups. A Local TM, then that Local TM further backed up to Carbonite/Crashplan.
Nope, that's
not my method ! As you describe it above , both backups use the
exact same, single backup mechanism = TM. So if there is a TM issue (and they exist, I have experienced one), then you are screwed because you have
a single point of failure = TM.
My method is (1) backup using TM, (2) Backup using another,
entirely separate mechanism, preferably offsite, and
nothing at all to do with TM. Think about it, suppose unknown to you there is a bug which means all your TM's are now corrupt. Getting the offsite copy isnt going to help you!
FWIW I use
three backup mechanisms, all different - TM running all the time, online backups, and clones of my main HD. I thought I was paranoid but then someone described to me their
four different methods, LOL
Oh, I nearly forget, one other cardinal rule of backups, once in a while,
test. Select a file at random and restore it. I've known systems run for months or longer with backups that weren't working at all! You dont want the time to discover that, to be when you just had a disk crash

Ideally, you'd like to discover it before then
