Today I have a couple of links for all of you interested in backup:
First, the launch of the "official" EMC Backup and Recovery Systems Division blog, The Backup Window. There is lots of great content up already, and I am really liking some of the thinking about the future stuff that Stephen Manley is posting.
Second, Chad has a really great and thought provoking post about the future of backup for VMware enviornments. Really great, and really interesting. Although there is still a really big problem to tackle: data consistency within applications.
And to add to Chad's comments, I can think of a few other things I would like to see:
- Built in charge-back modeling. It is great to provide users with the ability to define their own backup and provision it, but it also has some dangers--like users that dont understand retaining everything forever entails some risks.
- Built in policy boundaries. There should be a setting that defines what the limits of a user-defined policy are. In other words, don't let people shoot themselves in the foot. vCD should have settings that limit frequency and retention for backups.
- What if modeling that shows resource impacts of changes to backup policy.
- Critical parts of the vCD structures in a multi-tenancy environment should be automatically "pinned" to the backups of that tenant so that those backups are portable and self-defining.
I am sure there are others--but it is great stuff to think about. Make no mistake, this is where backup is heading, in my opinion.
Comments