Modular NetBackup Client Architecture
This idea is to prevent a NetBackup Master server upgrade from being a requirement in order to support a new client type. For example, it is very painful to have to upgrade all NetBackup masters to a new code revision (testing, Q/A, change procedures, outages, etc.) to support a new client type like Windows Server 2008 R2 or SQL Server 2008. If the NetBackup code was possibly more modular, a new client could possibly be created that would still function without a NetBackup master upgrade. This is not an apples to apples comparison obviously, but the idea is similar to how one can run Outlook 2007 with an Exchange 2000 server and have almost all functionality still of the Outlook 2007 client, but without some of the advantages of Exchange 2003/2007/2010 on the back end.
Comments
New types of data to be
New types of data to be backed up require code changes not only on the client but on the master/media servers as well.
Would you like to reply?
Login or Register to post your comment.