What will backup in the cloud look like? Chuck Hollis wrote a post a few weeks ago on the subject.
I have been thinking about the issues that he raised ever since. Mostly because there was something about the piece that didn't quite satisfy me. There was something missing. Something that I couldn't put my finger on at first.
So I asked a more fundamental question: why do we backup like we do today?
And the only good answer I could come up with was: because that is the way we have always done it.
And I really don't like that answer.
In and of itself it is almost never a good answer. It may be that we have always done it that way, and there are good reasons for doing it that way. But if we are just doing it because we have always done it, and there is no other reason, that isn't good enough.
Not when the process is so badly broken.
Make no mistake: backup today is broken. Badly broken. It involves too many pieces. Too many components of the infrastructure. Has too many dependencies. Takes too much administrative effort. Takes too long. And it doesn't do a very good job of leveraging new technologies.
All because we take a host-centric view of backup.