ADSM-L

Antwort: disk pool problem tsm 4.2.1.9

2002-01-28 08:23:30
Subject: Antwort: disk pool problem tsm 4.2.1.9
From: Gerhard Wolkerstorfer <Gerhard.Wolkerstorfer AT T-SYSTEMS DOT AT>
Date: Mon, 28 Jan 2002 14:17:09 +0100
The only chance I see =>
Increase your diskpool.....
Because, if you have 3 Gb diskpool und there are 2 Nodes with (let's say) 1,8 Gb
Files, the first grabs 1,8 Gb, and there are only 1,2 Gb left und the second
Node doesn't have enough space in the pool and will go to the nextpool (your
tapepool)

Gerhard Wolkerstorfer





burak.demircan AT DAIMLERCHRYSLER DOT COM (Burak Demircan) am 28.01.2002 
13:24:40

Bitte antworten an ADSM-L AT VM.MARIST DOT EDU

An:   ADSM-L AT VM.MARIST DOT EDU
Kopie:     (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT)

Thema:    disk pool problem tsm 4.2.1.9



Hi,
I am using TSM 4.2.1.9 on AIX 4.3.3 with 3583 Library (3 Drives on it)

I have a disk pool about 3GB. All my schedules starts at 7pm but some
clients' files are over 1.8GB on a low bandwitdth. These clients
try to write next stg pool (to a tape pool) directly although their
destination pool is my disk pool. I came to a conclusion that due
to not enough space on disk pool during backup of many clients
some of them are trying to write tape pool even though tape drives are very
slow.

Do you have any idea to prevent clients to write my tape pools
directly (I use migration and at %60 the disk pool migrates to tape pool).

I want all clients to write to disk pool and migrate them according
to above condition whatever the size or bandwitdh of data.

Thank you in advance
Burak
<Prev in Thread] Current Thread [Next in Thread>
  • Antwort: disk pool problem tsm 4.2.1.9, Gerhard Wolkerstorfer <=