RE: [Veritas-bu] Hardware compression not working

2006-04-25 Thread Carlisle, D Renee
 
We believe that our issue does lie with the driver on each individual platform. 
 We think the IBM atdd driver will work for HP and seems to be supported by 
Veritas, but it is not supported for the Sun platform.  What I would like to 
know from anyone using Solaris 9 media servers with IBM LTO2 drives is what 
driver are you using?  You can find this by loading a tape in the drive and 
running the following:

Mt -f /dev/rmt/drive name rew
Mt -f /dev/rmt/drive name status

It should come back with something like IBM ULTRIUM-LTO2.  Also, what do you 
have in st.conf for IBM LTO 2 drives?  Thanks for your help.

 
 

Reneé Carlisle 
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-
The information contained in this message may be privileged,
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or any employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.

Thank you. Paychex, Inc.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread WEAVER, Simon
Title: Message



Although the spec is the same, do any of the netbackup
logs show why compression may not be running?


Regards
Simon Weaver3rd Line Technical SupportWindows
Domain Administrator 
EADS Astrium
Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3
5PU
Email:
[EMAIL PROTECTED]

  
  -Original Message-From: Carlisle, D
  Renee [mailto:[EMAIL PROTECTED] Sent: 17 April 2006
  20:22To: veritas-bu@mailman.eng.auburn.eduSubject:
  [Veritas-bu] Hardware compression not working
  
  Tape Library: IBM 3584
  partitioned into production and test environment
  Operating System: Solaris 9, Windows 2003, HP-UX 11i
  Netbackup: 5.1 mp3
  
  Just upgraded from STK L700E
  LTO-1 library to a IBM 3584 LTO-2 library
  All of a sudden tape
  compression is not working on any flavor media
  server, but only in production. Our test environment is compressing
  data at a hardware level just fine. Same OS, same NBU release, same Tape
  library, same tape drive drivers, same HBA cards, same firmware, same st.conf
  file on the Sun systems.
  Can anyone think of what we
  might be missing that would cause the production environment not to be using
  hardware compression while the test environment
  is?
  
  
  
  
  Reneé
  Carlisle Sr.
  Systems Administrator675 Basket
  RoadWebster, NY
  14580
  
  Jer
  29:11-13
  
  
  
  

  
  The information contained in this message may be
  privileged,confidential, and protected from disclosure. If the reader of
  thismessage is not the intended recipient, or any employee or
  agentresponsible for delivering this message to the intended
  recipient,you are hereby notified that any dissemination, distribution,
  orcopying of this communication is strictly prohibited. If you
  havereceived this communication in error, please notify us
  immediatelyby replying to the message and deleting it from your
  computer.Thank you. Paychex,
Inc.

This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England


RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Whelan, Patrick
Title: Message









What is the indication that it is not
compressing? Is it the same data as the test system?





Patrick Whelan 
NetBackup Specialist 
Architect  Engineering 
+44 20 7863 5243 

Of all the things I've lost, I miss my mind the most! - Unknown 



-Original
Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of WEAVER, Simon
Sent: 18 April 2006 10:04
To: 'Carlisle, D Renee';
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Hardware
compression not working





Although the spec is the same, do any of the
netbackup logs show why compression may not be running?















Regards

Simon Weaver
3rd
Line Technical Support
Windows Domain
Administrator 

EADS
Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: [EMAIL PROTECTED]



-Original Message-
From: Carlisle, D Renee
[mailto:[EMAIL PROTECTED] 
Sent: 17 April 2006 20:22
To:
veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Hardware
compression not working

Tape Library: IBM 3584
partitioned into production and test environment

Operating System: 
Solaris 9, Windows 2003, HP-UX 11i

Netbackup: 5.1 mp3



Just upgraded from STK
L700E LTO-1 library to a IBM 3584 LTO-2 library

All of a sudden tape
compression is not working on any flavor media server, but only in production.
Our test environment is compressing data at a hardware level just fine.  Same
OS, same NBU release, same Tape library, same tape drive drivers, same HBA
cards, same firmware, same st.conf file on the Sun systems.


Can anyone think of what we might be missing that would cause the production
environment not to be using hardware compression while the test environment is?















Reneé Carlisle 
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580




Jer
29:11-13














The information contained in this
message may be privileged,
confidential, and protected from
disclosure. If the reader of this
message is not the intended recipient,
or any employee or agent
responsible for delivering this message
to the intended recipient,
you are hereby notified that any
dissemination, distribution, or
copying of this communication is
strictly prohibited. If you have
received this communication in error,
please notify us immediately
by replying to the message and deleting
it from your computer.

Thank you. Paychex, Inc.







*
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also be subject to legal privilege.  If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies. 

Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.




This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England


RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Carlisle, D Renee
Title: Message



I checked all that and it looks good. Sg.conf is 
identical, major numbers and minor number convention on the HP looks the same 
(they don't exist on sun) no mention of compression or errors in 
bptm. Our issue is that if we don't figure this out by Friday, we will be 
out of tapes.




Reneé 
Carlisle Sr. 
Systems Administrator675 Basket 
RoadWebster, NY 
14580 

Jer 
29:11-13


585-216-0497 (w)585-472-2360 (c)




From: Whelan, Patrick 
[mailto:[EMAIL PROTECTED] Sent: Tuesday, April 18, 2006 10:04 
AMTo: Carlisle, D ReneeSubject: RE: [Veritas-bu] Hardware 
compression not working


I guess I would look at 
the bptm log files on the two systems and look for differences. Also look 
at /dev/rmt and see if the major/minor numbers agree between the systems. Are 
sg.conf files the same? And lastly, keep asking this group, someone may have a 
real answer. J

Regards,


Patrick 
Whelan 
NetBackup 
Specialist 
Architect  
Engineering +44 20 
7863 5243 
Of all the things I've lost, I miss my 
mind the most! - Unknown 
-Original 
Message-From: Carlisle, D 
Renee [mailto:[EMAIL PROTECTED] Sent: 18 April 2006 14:57To: Whelan, Patrick; 
veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Hardware 
compression not working

LTO 1 
tapes are filling up at about 100 gig of data and LTO 2 tapes are filling up at 
200 Gig of data. In our STK environment close to 200 gig on our LTO1 tapes 
in the STK environment. The data has not changed. The data between 
production and test is the same. Our performance in production is maxing 
35 mb/sec...which should be higher with compression.





Reneé Carlisle 
Sr. 
Systems Administrator675 Basket 
RoadWebster, NY 
14580 
Jer 
29:11-13


585-216-0497 
(w)585-472-2360 (c)







The information contained in this message may be privileged,
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or any employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.

Thank you. Paychex, Inc.



RE: RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread bob944
 Date: Tue, 18 Apr 2006 10:42:58 -0400
 From: Carlisle, D Renee [EMAIL PROTECTED]

 I checked all that and it looks good=2E  Sg=2Econf is 
 identical, major numb=
 ers and minor number convention on the HP looks the same 
 (they don't exist =
 on sun)  no mention of compression or errors in bptm=2E  Our 
 issue is that =
 if we don't figure this out by Friday, we will be out of 
 tapes=2E=0D=0A =0D=

What makes you believe that hardware compression is not working?
Testing how many copies of a repeatable data set go to a newly expired
tape before a second tape gets used, and repeating that (same tape, same
data, same client) with 1 1.5:1 or 2:1 difference would be a clear
indication.

Didn't you mention that you had changed to a new (partitioned) library
and drives, and were getting what you suspect is no h/w compression on
one side of the library?  I'd want to know the library's contribution to
your issue by testing.

AFAIK, hardware compression is solely controlled by a SCSI command which
sets the mode; the bits for which you see in the multiple-mode fields in
Solaris st.conf entries.  That's a driver function.  On Solaris, you can
look in messages on startup and see if the capability bits and modes you
expect are what are reported.  

I'd suggest proving the compression assertion first, then getting
support people for the drive/library/drivers involved.  


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Carlisle, D Renee
 
I answered the compression issue in a previous post, we definitely are not 
getting compression.  The reason I mentioned the library is that it does not 
seem to be at the hardware level since the tapes are obviously compressing on 
the test side of the world and we are using the same library.  IBM, Sun, and 
Veritas are all involved right now (even though it is across HP, Sun, and 
Windows), but everyone is scratching their heads.  Just trying to think outside 
the box now.

 
 

Reneé Carlisle 
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-Original Message-
From: bob944 [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 18, 2006 11:20 AM
To: veritas-bu@mailman.eng.auburn.edu
Cc: Carlisle, D Renee
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 Date: Tue, 18 Apr 2006 10:42:58 -0400
 From: Carlisle, D Renee [EMAIL PROTECTED]

What makes you believe that hardware compression is not working?

I'd suggest proving the compression assertion first, then getting support 
people for the drive/library/drivers involved.  


-
The information contained in this message may be privileged,
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or any employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.

Thank you. Paychex, Inc.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Jack Forester, Jr.
Some drives can have the compression turned on by a drive setting so 
that it uses compression, regardless.  Did any of your drive settings 
change?


I agree with a previous poster in that you should do some kind of a test 
to determine how much data is being written to a tape before it moves on 
to a new tape.


bob944 wrote:


Date: Tue, 18 Apr 2006 10:42:58 -0400
From: Carlisle, D Renee [EMAIL PROTECTED]
   



 

I checked all that and it looks good=2E  Sg=2Econf is 
identical, major numb=
ers and minor number convention on the HP looks the same 
(they don't exist =
on sun)  no mention of compression or errors in bptm=2E  Our 
issue is that =
if we don't figure this out by Friday, we will be out of 
tapes=2E=0D=0A =0D=
   



What makes you believe that hardware compression is not working?
Testing how many copies of a repeatable data set go to a newly expired
tape before a second tape gets used, and repeating that (same tape, same
data, same client) with 1 1.5:1 or 2:1 difference would be a clear
indication.

Didn't you mention that you had changed to a new (partitioned) library
and drives, and were getting what you suspect is no h/w compression on
one side of the library?  I'd want to know the library's contribution to
your issue by testing.

AFAIK, hardware compression is solely controlled by a SCSI command which
sets the mode; the bits for which you see in the multiple-mode fields in
Solaris st.conf entries.  That's a driver function.  On Solaris, you can
look in messages on startup and see if the capability bits and modes you
expect are what are reported.  


I'd suggest proving the compression assertion first, then getting
support people for the drive/library/drivers involved.  



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 




--
Jack L. Forester, Jr.
UNIX Systems Administrator, Stf
Lockheed Martin Information Technology
(304) 625-3946

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Mark Pinder
One other thing to keep in mind is that once a tape is written to with 
compression off, the drive will default to compression off when that tape is 
loaded. It will require a format of a tape (I.E. !! at BOT with a cbn device 
driver) to clear this condition and allow the tape to use compression. All of 
the tapes that have been formatted with the SW and Compression off will 
forever write in an uncompressed mode regardless of the device driver used. 
The drive does this on it's own by sensing/reading the tape. 

I agree that you should do some formal and systematic testing. A couple of ways 
to do this are 1) Create a text file that repeats some data pattern and make it 
large. Then count the number of times that file can be written to tape. 
Alternatively, 2) dd from /dev/zero to the tape device file and see how much 
data you can get on a tape or write anything more than the capacity of the 
tape's worth of '0's.  For both of these tests you should use a fresh tape and 
use a compression enabled driver. 


Mark Pinder : 
Systems Engineer:
Spectra Logic : 





___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread william . d . brown
You can get good test programs and test data file generation from the HP 
web site.

http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50460locale=en_US

Look for 'hptapeperf' and 'hpcreatedata' - the latter can produce specific 
compressibility levels of the data.

That will at least allow you to do definitive and repeatable tests.  I'd 
guess if you set the tape chunk size smaller than the volume of test data, 
you can just see from the logs how many chunks NBU writes, to see if it is 
compressing the data.  Maybe - I'm not sure when it decides to start a new 
chunk if it is allowing for hardware compression.  HP LTT is also a good 
tool for querying the drive status pages.

Definitely worth doing your tests with known brand-new media, as someone 
suggested, once written uncompressed always so written unless reformatted.

William D L Brown


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Jeff Lightner
Didn't respond earlier because I thought your post regarding Sun only.   On HP 
the device's minor specifies settings of the drive's device entries - it will 
have several.   You need to make sure your minor numbers are for the Best 
density which would include compression.

Also as noted by another poster I have seen on HP-UX that when I wrote to a 
drive using its non-compressed device entry that subsequent writes to that 
device where I couldn't specify the density made it continue to write in a 
non-compressed mode.   This was for a backup I was doing from the boot prompt 
(don't remember how exactly I did that).   By booting up the OS then doing a 
short write to the device file that had compression enabled then going back 
down to the boot prompt I was able to make it write compression.

Not sure how familiar with HP-UX you are.  It has a command called lssf for 
listing special files.   For tape devices it will show you detail.

Example chosen at random from my HP-UX master server:
lssf /dev/rmt/c9t3d5BEST
stape card instance 9 SCSI target 3 SCSI LUN 5 att best density available at 
address 0/6/1/0/4/0.98.54.255.1.3.5 /dev/rmt/c9t3d5BEST

Shows it is the best density available so I know it has compression.   You 
might want to try running lssf on the devices you have configured in HP-UX to 
insure they have this.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlisle, D Renee
Sent: Tuesday, April 18, 2006 12:16 PM
To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 
I answered the compression issue in a previous post, we definitely are not 
getting compression.  The reason I mentioned the library is that it does not 
seem to be at the hardware level since the tapes are obviously compressing on 
the test side of the world and we are using the same library.  IBM, Sun, and 
Veritas are all involved right now (even though it is across HP, Sun, and 
Windows), but everyone is scratching their heads.  Just trying to think outside 
the box now.

 
 

Reneé Carlisle 
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-Original Message-
From: bob944 [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 18, 2006 11:20 AM
To: veritas-bu@mailman.eng.auburn.edu
Cc: Carlisle, D Renee
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 Date: Tue, 18 Apr 2006 10:42:58 -0400
 From: Carlisle, D Renee [EMAIL PROTECTED]

What makes you believe that hardware compression is not working?

I'd suggest proving the compression assertion first, then getting support 
people for the drive/library/drivers involved.  


-
The information contained in this message may be privileged,
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or any employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.

Thank you. Paychex, Inc.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


RE: RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Cornely, David

Not sure if this is the issue for you but our experience with tape drives and 
HP might help.
We're using AIT-3 and what we've had to do from the beginning is configure them 
to emulate AIT-1 drives.  This is done from our library, not on the host.

It's necessary because HP only produces drivers for the AIT-1 model -- I guess 
they just haven't felt like keeping up the drivers as new models come out.  At 
any rate, this might be something to consider in your case.  I don't have the 
beginning of the thread so I don't know what type/model tape drive you're using 
but you might want to check to make sure they have driver support for this 
model.  Or you could look into emulating older models of the same tape drive 
and see what happens.

-Dave

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlisle, D Renee
Sent: Tuesday, April 18, 2006 12:32
To: Jeff Lightner; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

We are using BEST on HP, we have done numerous testing with new tapes and 
consistent data and compression has not been working since we switched over to 
the IBM library. 


 
 

Reneé Carlisle 
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-Original Message-
From: Jeff Lightner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 18, 2006 2:42 PM
To: Carlisle, D Renee; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

Didn't respond earlier because I thought your post regarding Sun only.   On HP 
the device's minor specifies settings of the drive's device entries - it will 
have several.   You need to make sure your minor numbers are for the Best 
density which would include compression.

Also as noted by another poster I have seen on HP-UX that when I wrote to a 
drive using its non-compressed device entry that subsequent writes to that 
device where I couldn't specify the density made it continue to write in a 
non-compressed mode.   This was for a backup I was doing from the boot prompt 
(don't remember how exactly I did that).   By booting up the OS then doing a 
short write to the device file that had compression enabled then going back 
down to the boot prompt I was able to make it write compression.

Not sure how familiar with HP-UX you are.  It has a command called lssf for 
listing special files.   For tape devices it will show you detail.

Example chosen at random from my HP-UX master server:
lssf /dev/rmt/c9t3d5BEST
stape card instance 9 SCSI target 3 SCSI LUN 5 att best density available at 
address 0/6/1/0/4/0.98.54.255.1.3.5 /dev/rmt/c9t3d5BEST

Shows it is the best density available so I know it has compression.   You 
might want to try running lssf on the devices you have configured in HP-UX to 
insure they have this.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlisle, D Renee
Sent: Tuesday, April 18, 2006 12:16 PM
To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 
I answered the compression issue in a previous post, we definitely are not 
getting compression.  The reason I mentioned the library is that it does not 
seem to be at the hardware level since the tapes are obviously compressing on 
the test side of the world and we are using the same library.  IBM, Sun, and 
Veritas are all involved right now (even though it is across HP, Sun, and 
Windows), but everyone is scratching their heads.  Just trying to think outside 
the box now.

 
 

Reneé Carlisle
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-Original Message-
From: bob944 [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 18, 2006 11:20 AM
To: veritas-bu@mailman.eng.auburn.edu
Cc: Carlisle, D Renee
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 Date: Tue, 18 Apr 2006 10:42:58 -0400
 From: Carlisle, D Renee [EMAIL PROTECTED]

What makes you believe that hardware compression is not working?

I'd suggest proving the compression assertion first, then getting support 
people for the drive/library/drivers involved.  


-
The information contained in this message may be privileged, confidential, and 
protected from disclosure. If the reader of this message is not the intended 
recipient, or any employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly prohibited. If you 
have received this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you. Paychex, Inc.


___
Veritas-bu

RE: RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread Mansell, Richard
Renee

I left my HP-UX life behind a couple of years ago but have you installed the 
LTO drivers for HP-UX from IBM? We used to have a 3584 connected to various 
HP-UX servers and I remember having to install something from IBM.

Here is a link that may help:-

http://www-1.ibm.com/support/docview.wss?uid=ssg1S4000102

Have you seen this Red book from IBM about connecting drives to UNIX systems?

http://www.redbooks.ibm.com/abstracts/SG246502.html?Open




Don't know if you have access to HP's ITRC but here is a thread from there:-



Jun 3, 2005 07:10:21 GMT  

Hi,
Could anyone help me to configure ibm 3584 tape library for rp2470 ? 
With thanks  regards
Sid  
 
Leif Halvarsson   Jun 3, 2005 07:55:00 GMT  3 pts   

Hi,
IBM LTO drives need a special driver (ATDD) which can be downloaded from IBM 
but, perhaps you should check this thread before:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=620564 


Thanks for ur reply. I already downloaded the binaries and installed but it 
didn't work.
Sid 


Leif Halvarsson   Jun 3, 2005 13:10:28 GMT  3 pts   

I downloaded the drivers from following site
ftp://ftp.software.ibm.com/storage/devdrvr/HPUX/11i_PCI/
and installed the drivers. Then I changed kernel parameters for acdd to be 
loaded automatically. And it fixed the issue.

 
 

 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlisle, D Renee
Sent: Wednesday, 19 April 2006 7:32 am
To: Jeff Lightner; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

We are using BEST on HP, we have done numerous testing with new tapes and 
consistent data and compression has not been working since we switched over to 
the IBM library. 


 
 

Reneé Carlisle
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-Original Message-
From: Jeff Lightner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 18, 2006 2:42 PM
To: Carlisle, D Renee; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

Didn't respond earlier because I thought your post regarding Sun only.   On HP 
the device's minor specifies settings of the drive's device entries - it will 
have several.   You need to make sure your minor numbers are for the Best 
density which would include compression.

Also as noted by another poster I have seen on HP-UX that when I wrote to a 
drive using its non-compressed device entry that subsequent writes to that 
device where I couldn't specify the density made it continue to write in a 
non-compressed mode.   This was for a backup I was doing from the boot prompt 
(don't remember how exactly I did that).   By booting up the OS then doing a 
short write to the device file that had compression enabled then going back 
down to the boot prompt I was able to make it write compression.

Not sure how familiar with HP-UX you are.  It has a command called lssf for 
listing special files.   For tape devices it will show you detail.

Example chosen at random from my HP-UX master server:
lssf /dev/rmt/c9t3d5BEST
stape card instance 9 SCSI target 3 SCSI LUN 5 att best density available at 
address 0/6/1/0/4/0.98.54.255.1.3.5 /dev/rmt/c9t3d5BEST

Shows it is the best density available so I know it has compression.   You 
might want to try running lssf on the devices you have configured in HP-UX to 
insure they have this.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlisle, D Renee
Sent: Tuesday, April 18, 2006 12:16 PM
To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 
I answered the compression issue in a previous post, we definitely are not 
getting compression.  The reason I mentioned the library is that it does not 
seem to be at the hardware level since the tapes are obviously compressing on 
the test side of the world and we are using the same library.  IBM, Sun, and 
Veritas are all involved right now (even though it is across HP, Sun, and 
Windows), but everyone is scratching their heads.  Just trying to think outside 
the box now.

 
 

Reneé Carlisle
Sr. Systems Administrator
675 Basket Road
Webster, NY 14580 

Jer 29:11-13

 

 

585-216-0497 (w)
585-472-2360 (c)

 

-Original Message-
From: bob944 [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 18, 2006 11:20 AM
To: veritas-bu@mailman.eng.auburn.edu
Cc: Carlisle, D Renee
Subject: RE: RE: [Veritas-bu] Hardware compression not working

 Date: Tue, 18 Apr 2006 10:42:58 -0400

RE: [Veritas-bu] Hardware compression not working

2006-04-18 Thread bob944
 Tape Library: IBM 3584 partitioned into production and test 
 environment
 
 Operating System:  Solaris 9, Windows 2003, HP-UX 11i
 
 Netbackup: 5.1 mp3
 
 Just upgraded from STK L700E LTO-1 library to a IBM 3584 LTO-2 library
 
 All of a sudden tape compression is not working on any flavor 
 media server,=
  but only in production. Our test environment is compressing 
 data at a hard=
 ware level just fine.  Same OS, same NBU release, same Tape 
 library, same t=
 ape drive drivers, same HBA cards, same firmware, same 
 st.conf file on the =
 Sun systems.

Have you consulted the NetBackup Hardware Compatibility List?  Both the
5.1 and 6.0 lists show Library partitioning is supported for
TotalStorage 3582 and 3583 models, but the 3584 models say All models
supported. --- ALMS is supported with the exception of drive sharing.
No mention of library partitioning.

Un-partitioning the library for a test should show if this is germane.

 color:blue;font-weight:bold'Although the spec is the
 same, do any of the netbackup logs show why compression
 may not be running?/span/font/i

AFAIK, NetBackup knows/does absolutely nothing about compression--it
uses the drive/driver that you configured.  If you configured
/dev/rmt/0bn, you gave it an uncompressed drive[r entry point], if
/dev/rmt/0cbn, a compressed one (assuming the name matches the maj/min
numbers, of course).  You know that already.  The point is, NetBackup
sends the driver a write command, a buffer address and a count and gets
back a good/bad status from the driver at the end of the operation.
What the hardware actually put on tape is up to the hardware and the
mode to which its driver set it.

In case you carried over your old media to one of the new environments,
you know that LTO-1 media in an LTO-2 drive is written to at LTO-1
density.

Update from digest #5102:
 I answered the compression issue in a previous post.

Apologies.  You did, but words are sprinkled throughout pages of
impenetrable HTML crap.  I would still recommend a) setting up a simple,
repeatable test as suggested and b) proving that the partitioning of the
library is not a factor.  Now, I'd add c) involve or eliminate NetBackup
by using dd, rmt, fdump or other utilities to see if they exhibit the
same behaviors you see on your test/prod sides.

You have completely ripped out the old lib/drive configuration (dev,
fibre, st, sg, NBU) and rebuilt it with the new hardware, correct?


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu