My previous post Is a Copy a Backup? was written after I got to thinking about a backup services catalog. What is a backup services catalog? Basically it is two things.
First, it is an admission that we have a lot more choices in terms of what technologies to use to provision backup services than ever before. 10 years ago, the backup technologies was really backup technology: tape. It was pretty easy to design a such a catalog, because you really only had one choice: tape. And it didn't really matter how rich, thin, or beautiful you were, you still only had one choice: tape.
Second, it is a recognition than different applications have different levels of importance to the business, and that given we have an array of technology choices with which to backup them up and recover them, we should probably choose different technologies for the different applications. Let me put that a different way: your SAP/Oracle application which runs AP, AR, and inventory is probably way more important than a miscellaneous SQL server some user threw up for ad hoc reporting, or an edge web server that is one of a few dozen others just like it.
So if you have different tiers of applications, shouldn't you have different tiers of backup and recovery? You bet you should.