ADSM-L

Re: [ADSM-L] 3592 drives no compression

2009-10-29 09:40:51
Subject: Re: [ADSM-L] 3592 drives no compression
From: Wanda Prather <wanda.prather AT JASI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 29 Oct 2009 09:38:14 -0400
Try this:

q actlog begindate=today-2 search=compress

You can see very quickly if any of your client systems are doing
compression.

On Thu, Oct 29, 2009 at 3:33 AM, Lars-Erik Öhman <larsa.ohman AT carnegie DOT 
se>wrote:

> No change at all with a new tape deviceclass. I did set the compression to
> the drive too.
>
> When I start the backup and do have some data on the tape, it reports that
> the estimated capacity is 921 Gb, but after a while it´s 100% full and it´s
> only 366Gb of data.
>
> /Larsa
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Robert Clark
> Sent: den 28 oktober 2009 00:12
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] 3592 drives no compression
>
> Did you get a batch of short tapes?
>
> [RC]
>
> On Oct 26, 2009, at 7:59 AM, Lars-Erik Öhman wrote:
>
> > "Backup Archive Client Backup Summary" reports that all clients
> > have 0 in "Percent Compressed".
> >
> > I´ll try and create a new deviceclass for tapes, and see if that
> > could change anything.
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of Richard Sims
> > Sent: den 26 oktober 2009 15:26
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] 3592 drives no compression
> >
> > On Oct 26, 2009, at 9:42 AM, Lars-Erik Öhman wrote:
> >
> >> It´s generation 1 drives, and the driver is the latest from IBM
> >> (September 2009).
> >>
> >> I check in device manager and the driver version is 6.2.0.1
> >> (3592J1A), and it even say in "Tape drive parameters" that
> >> Compression capable is TRUE, and Compression enabled TRUE.
> >
> > Okay - that helps narrow it down.
> > You indicate that the client options do not specify that the client
> > should be doing compression.  Do some 'dsmc query options' to assure
> > that.
> > Another thing to check is whether the REGister Node that was used for
> > these clients specified COMPression=Yes - or check the session summary
> > report from recent backups, for compression indications.
> >
> > Beyond that, the cause is obscure.  I would pursue by defining a
> > temporary storage pool and mgmt class (for tape isolation) performing
> > a backup on a very large, ordinary-content file, look at the backup
> > statistics, then perform a Select on it in the Backups table to look
> > for comparable size there, to see if there is any compression in the
> > path to TSM.  Outside of TSM, you might take a drive from TSM, mount a
> > spare 3592 tape via your OS and have a program write ordinary data to
> > it until EOT was reached, where it would report its progress, and you
> > could then assess compression.
> >
> >     Richard Sims
> >
> >
> > This communication is from a Carnegie company within the Carnegie
> > Group.
> >
> > The information contained in it, including any attachment or
> > enclosure, is intended only for the person or entity to which it is
> > addressed and may contain confidential and/or privileged material.
> > Any unauthorised use, review, retransmissions, dissemination,
> > copying or other use of, or taking of any action in reliance upon,
> > this information by persons or entities other than the intended
> > recipient is prohibited. If you received this in error, please
> > contact the sender and delete or shred the material immediately.
> > Thank you.
> >
> > Opinions, conclusions and other information expressed in this
> > message are not given or endorsed by my firm or employer unless
> > otherwise indicated by an authorised representative independent of
> > this message.
>
> Robert Clark
> Robert_Clark AT mac DOT com
> 503-681-0899 or 503-816-6488
> YIM:Robert_Storage_Engineer
> Twitter:rclark
>
>
> This communication is from a Carnegie company within the Carnegie Group.
>
> The information contained in it, including any attachment or enclosure, is
> intended only for the person or entity to which it is addressed and may
> contain confidential and/or privileged material. Any unauthorised use,
> review, retransmissions, dissemination, copying or other use of, or taking
> of any action in reliance upon, this information by persons or entities
> other than the intended recipient is prohibited. If you received this in
> error, please contact the sender and delete or shred the material
> immediately. Thank you.
>
> Opinions, conclusions and other information expressed in this message are
> not given or endorsed by my firm or employer unless otherwise indicated by
> an authorised representative independent of this message.
>

<Prev in Thread] Current Thread [Next in Thread>