ADSM-L

Re: Replacing our onsite tapepool that is used for migration?

2004-07-09 11:33:02
Subject: Re: Replacing our onsite tapepool that is used for migration?
From: asr AT UFL DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 9 Jul 2004 11:32:48 -0400
==> In article <OF857AAFF9.8DACA76A-ON85256ECC.004143F9-85256ECC.0046096F AT 
humana DOT com>, David Browne <dbrowne AT HUMANA DOT COM> writes:


> We will be removing our onsite tapepool that is used for migration of our
> disk pool, replacing it with a large disk pool.

> Below is the size of the current tapepool.

> I was considering just adding DASD to our current diskpool, discontinue the
> migration process and letting the files expire through the normal backup and
> file expiration process. After time, move the remaining stranded data to the
> disk pool.

> Is there a recommended procedure to do this task or can someone suggest a
> better procedure?

DISK devclasses don't reclaim space all that well. You would do well to
consider using FILE devclasses instead, and then just pretend that it's a tape
library.


- Allen S. Rout

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