Veritas-bu

Re: [Veritas-bu] Off Topic: Firmware and driver versions?

2010-05-12 09:59:01
Subject: Re: [Veritas-bu] Off Topic: Firmware and driver versions?
From: "Marianne Van Den Berg" <mvdberg AT stortech.co DOT za>
To: "Lightner, Jeff" <jlightner AT water DOT com>, <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Wed, 12 May 2010 15:58:44 +0200

Thanks Jeff

 

Hoping to get as many responses as possible.

 

We were asked by a customer in a (fairly) large environment to provide recommended firmware and driver info. I am merely prepared to give what is in the Compatibility List. There are separate teams for everything – SAN, O/S (separate Windows and Unix team), Backup. Backup team has VERY limited access to servers (sudo access to NBU commands only on Solaris servers, local admin on Windows). Which team should be responsible for gathering and implementing firmware/driver updates?

 

The installation is about 2 years old and no updates have been done since the original installation. NetBackup has been patched several times.  

 

From: Lightner, Jeff [mailto:jlightner AT water DOT com]
Sent: 12 May 2010 02:03 PM
To: Marianne Van Den Berg; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Off Topic: Firmware and driver versions?

 

I don’t see that at all – the switches and HBAs are SAN/Network technology that deal with the transport of data and aren’t directly addressed by NetBackup per se.  NetBackup compatibility should have to do with what OS they’ll run on and what storage medium they’ll work on – it should be up to the HBA and storage vendors to determine what will get data between the two of them.

 

In any scenario where you have multiple vendors involved you’re apt to find something in your overall solution that isn’t on everyone’s compatibility list.   There’s been many a complicated environment I’ve worked on where one piece or another wasn’t “supported” but worked just fine and had to be there.   If you hold back on constituent applications or hardware waiting for it to be in the matrix you’re apt to find that by the time it is something else has gone EOL so no longer is.

 


From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Marianne Van Den Berg
Sent: Wednesday, May 12, 2010 7:54 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Off Topic: Firmware and driver versions?

 

Another Off Topic question:

 

In a big SSO environment with mixed O/S media servers attached to tape and disk (via different HBA’s) – who dictates what driver/firmware versions should be used on tape drives, hba’s, switches?

 

The NBU hardware compatibility list is very basic and list ‘tested’ versions for tape drives, not recommended.

As far as switches and HBA’s are concerned, the compatibility guide says: “Consult the hardware vendor's web site for up-to-date firmware and driver updates.”

 

My viewpoint is that the tape vendor should supply all these compatibilities. I’d like to know how it’s done in your environment and who initiates the whole process…

 

Regards

 

Marianne

 

Proud partner. Susan G. Komen for the Cure.

 

Please consider our environment before printing this e-mail or attachments.

----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu