Hello Zoltan,

Using STRIPES breaks the backup into "multiple chunks".
The STRIPES value that you specify will indicate how
many chunks are created at backup time.
If you still cannot get the backup speeds you need,
and you do not get useful suggestions from this list,
please open a PMR with IBM support. They can get the
TSM performance team involved and let you know how best
to tune your environment to get the best speeds possible.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 09/13/2011
12:48:12 PM:

>> From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 09/13/2011 01:02 PM
>> Subject: Re: Disk storage pool 100% utilized but NOT cached
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> Yes, that is kinda what I guessed.  I have the 4TB SQL backup still
>> running from Saturday.  It is only 50% done.
>>
>> There has got to be a better way to handle SQL backups of LARGE
databases.
>>  This is causing numerous headaches/problems with other backups by
>> pre-allocating the space or if going to tape, locking the tape drives
for
>> the duration.
>>
>> Del,  I know we discussed this and stripes (I have it configured for 3)

>> for improving the speed, but this goes back to my question about
breaking
>> up the SQL backup into multiple chunks, especially with this new issue
of
>> it locking 4TB of disk space to contain the backup, until it finishes.
I
>> can't have 1-backup detrimentally effecting everyone else and at the
speed
>> it is running, it will take almost a week to finish.
>>
>> Suggestions?
>>