Roger

Just a thought. What about the MAXNUMMP parameter on the node. Setting
it to zero. My initial thoughts were that it would be counter productive
for restores, in that, you would not be able to mount a tape for a
restore operation. However,  a help UPD NODE, shows the following

A value of zero specifies that a node cannot acquire any mount point for
a client data
store operation. The MAXNUMMP value is not evaluated or enforced during
client data read operations such as restore, retrieve, and HSM recall.

Leigh

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Roger Deschner
Sent: 05 June 2006 16:50
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Files stuck in disk stgpool

I'm looking for a strategy to attack a strange problem of stuck files
and failing migration.

In one heirarchy, I have a file size limit of 10g for the disk storage
pool, and also a limit of 10g for the tape pool it migrates to. The idea
is to prevent a client backup session from ever mounting a tape
directly, which is very inefficient.

We are using client compression.

There exists a client somewhere, who has a 9.99gb file that is of a type
that is already compressed (a jpeg photo, or a zip file, for instance).
The server compares its 9.99gb size to the 10gb limit, and says "OK,
back it up", and it comes down the wire into the disk storage pool.
However, when it arrives, it has grown by being recompressed, so that
now it is larger than 10gb.

Now it's stuck in the disk stgpool, and cannot be migrated to tape.
Migration processes repeatedly fail and are restarted. Things grind to a
halt.

This has now happened twice. My only fix is to temporarily raise the
tape pool's limit to get the stuck file migrated. However, this could
allow a client backup session to mount a tape.

Anybody got any better ideas?

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu