See previous comment about centralized DB... Retarded that each client keeps its own job results... poor!
I'm not quite certain as to how having a centralized Database is a point of failure in CommVault's design. To the best of my knowledge, the majority of NetBackup's data resides in 3 central databases, all retained on the Master Server (or a seperate EMM server, if you so wish to deploy one):
- NetbackupDB - central database
- EMMDB - "MediaManager" equivalent which controls all media (tld(*), media server registration, maybe vaulting?)
- Catalog - similar to Index Cache, but not quite.
So if anything, I don't see how this is a bad point. What I will point out however, is the database design is quite different.
So let's go off on a tangent here and look at DR restores for example.
With NetBackup, due to legacy decisions, primary ID's within catalogs/databases are based against master/media server names, not IDs. What this means is that in Netbackup land you are tied to the one server name, from install, for life.
- Want to perform a Catalog recovery and the original media server doesn't exist or is no longer named what it was? Have to manually edit catalog files (TECH48819).
- Want to rename the Master server? Not supported unless you contact SYMC Professional Services for "catalog manipulation services".
With CommVault this is all un-necessary .. names are simply that, names. You are not tied to your server names, and are free to migrate your servers, and your CommServe around as you need to which can happen every once in a while in an organisation (merger/de-mergers, acquisitions, organisational changes to your network, etc.)
To be honest, if you're going to compare CommVault against NetBackup then you need to be looking at something more tangible.
(Just my 2 cents..)